@aborruso/ckan-mcp-server 0.4.13 → 0.4.14

package/CLAUDE.md

@@ -41,7 +41,7 @@ The server exposes MCP tools for:
 # Build project (uses esbuild - fast and lightweight)
 npm run build
 
-# Run test suite (179 tests - unit + integration)
+# Run test suite (191 tests - unit + integration)
 npm test
 
 # Watch mode for tests during development
@@ -73,7 +73,7 @@ npm run deploy            # Deploy to Cloudflare Workers
 The project uses **esbuild** for compilation and **vitest** for testing:
 
 - **Build**: Ultra-fast builds (milliseconds instead of minutes)
-- **Tests**: 179 tests (unit + integration) with 100% success rate
+- **Tests**: 191 tests (unit + integration) with 100% success rate
 - **Coverage**: ~39% overall (utils: 98%, tools: 15-20%) - available via vitest with v8 coverage engine
 
 The `build:tsc` script is available as a fallback but can cause memory issues in some environments (particularly WSL). Always use `npm run build` which uses esbuild.
@@ -88,12 +88,12 @@ The project has a comprehensive test suite using **Vitest**:
 tests/
 ├── unit/
 │   ├── formatting.test.ts    # Utility functions (19 tests)
-│   ├── http.test.ts           # HTTP client (6 tests)
+│   ├── http.test.ts           # HTTP client (11 tests)
 │   └── uri.test.ts            # URI parsing (11 tests)
 ├── integration/
-│   ├── package.test.ts        # Package tools (29 tests)
+│   ├── package.test.ts        # Package tools (31 tests)
 │   ├── organization.test.ts   # Organization tools (6 tests)
-│   ├── datastore.test.ts      # DataStore tools (17 tests)
+│   ├── datastore.test.ts      # DataStore tools (19 tests)
 │   ├── resources.test.ts      # MCP Resources (11 tests)
 │   └── status.test.ts         # Status tools (2 tests)
 └── fixtures/
@@ -101,7 +101,7 @@ tests/
     └── errors/                # Error scenario mocks
 ```
 
-**Test Coverage**: 179 tests total (85 unit + 94 integration)
+**Test Coverage**: 191 tests total (117 unit + 74 integration)
 
 When making changes:
 1. Run tests before committing: `npm test`
@@ -341,7 +341,7 @@ To test with Claude Desktop, add the MCP configuration to the config file.
 - Direct data access for datasets, resources, organizations
 
 **v0.2.0 (2026-01-08)**: Comprehensive test suite
-- 179 tests (unit + integration)
+- 191 tests (unit + integration)
 - ~39% code coverage (utils well-tested, tools improving)
 
 **v0.1.0 (2026-01-08)**: Modular refactoring

package/LOG.md

@@ -1,5 +1,19 @@
 # LOG
 
+## 2026-01-22
+
+### Date Query Auto-Conversion (v0.4.14)
+
+- **Feature**: Auto-convert NOW-based date math for `modified` and `issued` fields
+- **Problem**: CKAN Solr supports `NOW-XDAYS` syntax only on `metadata_modified` and `metadata_created` fields
+- **Solution**: New `convertDateMathForUnsupportedFields()` automatically converts queries like `modified:[NOW-30DAYS TO NOW]` to ISO dates `modified:[2025-12-23T... TO 2026-01-22T...]`
+- **Supported fields**: `modified`, `issued` (auto-converted) | `metadata_modified`, `metadata_created` (native NOW support)
+- **Supported units**: DAYS, MONTHS, YEARS (singular and plural forms)
+- **Tests**: +10 unit tests (201 total, all passing)
+- **Documentation**: Updated tool description with NOW syntax limitations and examples
+- **Files**: `src/utils/search.ts`, `src/tools/package.ts`, `tests/unit/search.test.ts`
+- **No breaking changes**: Backward compatible - existing queries work unchanged
+
 ## 2026-01-19
 
 ### Search Parser Escaping

package/PRD.md

@@ -214,7 +214,7 @@ An MCP server that exposes tools to interact with CKAN API v3, enabling AI agent
 - `wrangler@^4.58.0` - Cloudflare Workers CLI
 
 **Test Framework**:
-- `vitest@^4.0.16` - Test runner (190 tests, 100% passing)
+- `vitest@^4.0.16` - Test runner (191 tests, 100% passing)
 
 ### 4.2 Architecture Diagram
 
@@ -825,7 +825,7 @@ ckan_package_search({
 ### 10.3 Testing & Quality
 
 ✅ **Current State**:
-- 190 unit and integration tests (100% passing)
+- 191 unit and integration tests (100% passing)
 - vitest test runner
 - Coverage for all 13 tools
 - Fixtures for offline testing
@@ -860,7 +860,7 @@ ckan_package_search({
 - **Memory Usage**: < 50MB runtime (Node.js), Workers limits apply
 - **Response Time**: < 30s (CKAN API timeout), < 10s (Workers)
 - **Cold Start**: < 60ms (Cloudflare Workers)
-- **Test Coverage**: 190 tests (100% passing)
+- **Test Coverage**: 191 tests (100% passing)
 
 ### 11.2 Distribution Metrics
 

package/README.md

@@ -17,7 +17,7 @@ MCP (Model Context Protocol) server for interacting with CKAN-based open data po
 - ⚡ Pagination and faceting support
 - 📄 MCP Resource Templates for direct data access
 - 🧭 Guided MCP prompts for common workflows
-- 🧪 Test suite with 186 tests (100% passing)
+- 🧪 Test suite with 191 tests (100% passing)
 
 ---
 
@@ -45,7 +45,7 @@ npm install
 # Build with esbuild (fast, ~4ms)
 npm run build
 
-# Run tests (186 tests)
+# Run tests (191 tests)
 npm test
 ```
 
@@ -117,22 +117,29 @@ Then add to `claude_desktop_config.json`:
 }
 ```
 
-#### Option 2: Local Installation (Optional)
+#### Option 2: Local Project Installation (Optional)
 
-If you installed locally (see Installation), use this config:
+If you want to install the server in a specific project:
+
+```bash
+cd your-project
+npm install @aborruso/ckan-mcp-server
+```
+
+Then add to `claude_desktop_config.json`:
 
 ```json
 {
   "mcpServers": {
     "ckan": {
-      "command": "node",
-      "args": ["/absolute/path/to/project/node_modules/@username/ckan-mcp-server/dist/index.js"]
+      "command": "npx",
+      "args": ["@aborruso/ckan-mcp-server"]
     }
   }
 }
 ```
 
-Replace `/absolute/path/to/project` with your actual project path.
+**Note**: `npx` will use the locally installed package in `node_modules`. Make sure to install the package first.
 
 #### Option 3: From Source
 
@@ -559,7 +566,7 @@ ckan-mcp-server/
 │   └── transport/
 │       ├── stdio.ts        # Stdio transport
 │       └── http.ts         # HTTP transport
-├── tests/                  # Test suite (184 tests)
+├── tests/                  # Test suite (191 tests)
 ├── dist/                   # Compiled files (generated)
 ├── package.json
 └── README.md

package/dist/index.js

@@ -168,6 +168,31 @@ function isFieldedQuery(query) {
 function escapeSolrQuery(query) {
   return query.replace(SOLR_SPECIAL_CHARS, "\\$&");
 }
+function convertDateMathForUnsupportedFields(query) {
+  const now = /* @__PURE__ */ new Date();
+  const nowIso = now.toISOString();
+  const pattern = /\b(?!metadata_)(modified|issued):\[NOW-(\d+)(DAYS?|MONTHS?|YEARS?)\s+TO\s+NOW\]/gi;
+  return query.replace(pattern, (match, field, amount, unit) => {
+    const amountNum = parseInt(amount, 10);
+    const startDate = new Date(now);
+    const normalizedUnit = unit.toLowerCase().replace(/s$/, "");
+    switch (normalizedUnit) {
+      case "day":
+        startDate.setDate(startDate.getDate() - amountNum);
+        break;
+      case "month":
+        startDate.setMonth(startDate.getMonth() - amountNum);
+        break;
+      case "year":
+        startDate.setFullYear(startDate.getFullYear() - amountNum);
+        break;
+      default:
+        return match;
+    }
+    const startIso = startDate.toISOString();
+    return `${field}:[${startIso} TO ${nowIso}]`;
+  });
+}
 function resolveSearchQuery(serverUrl, query, parserOverride) {
   const portalSearchConfig = getPortalSearchConfig(serverUrl);
   const portalForce = portalSearchConfig.force_text_field ?? false;
@@ -180,7 +205,8 @@ function resolveSearchQuery(serverUrl, query, parserOverride) {
     const trimmedQuery = query.trim();
     forceTextField = trimmedQuery !== DEFAULT_SEARCH_QUERY && !isFieldedQuery(trimmedQuery);
   }
-  const effectiveQuery = forceTextField ? `text:(${escapeSolrQuery(query)})` : query;
+  let effectiveQuery = forceTextField ? `text:(${escapeSolrQuery(query)})` : query;
+  effectiveQuery = convertDateMathForUnsupportedFields(effectiveQuery);
   return { effectiveQuery, forcedTextField: forceTextField };
 }
 
@@ -333,6 +359,9 @@ Query Syntax (parameter q):
     - NOW/DAY, NOW/MONTH (round down)
     - Combined: "metadata_modified:[NOW-2MONTHS TO NOW]"
     - Example: "metadata_created:[NOW-1YEAR TO *]"
+    - IMPORTANT: NOW syntax works on metadata_modified and metadata_created fields
+    - For 'modified' and 'issued' fields, NOW syntax is auto-converted to ISO dates
+    - Manual ISO dates always work: "modified:[2026-01-15T00:00:00Z TO *]"
 
   Field existence:
     - Exists: "field:*" or "field:[* TO *]"
@@ -351,6 +380,7 @@ Examples:
   - Proximity: { q: "notes:"open data"~3" }
   - Date range: { q: "metadata_modified:[2024-01-01T00:00:00Z TO 2024-12-31T23:59:59Z]" }
   - Date math: { q: "metadata_modified:[NOW-6MONTHS TO *]" }
+  - Date math (auto-converted): { q: "modified:[NOW-30DAYS TO NOW]" }
   - Field exists: { q: "organization:* AND num_resources:[1 TO *]" }
   - Boosting: { q: "title:climate^2 OR notes:climate" }
   - Filter org: { fq: "organization:regione-siciliana" }