@functional-systems/lambdadb-mcp 0.1.5 → 0.1.6-dev.20

package/CHANGELOG.md

@@ -2,6 +2,14 @@
 
 ## Unreleased
 
+- Pin the LambdaDB SDK to 0.10.0. Expand Query/Fetch/List and rerank limits to
+  1000 on supporting servers, retaining facet and collection-list limits of 100.
+  Vector dimensions now require integers from 64 to 4096 and similarity accepts
+  only cosine/euclidean; invalid requests and existing out-of-contract collection
+  metadata fail SDK validation. Update vector fixtures and native source guidance.
+
+- Synchronize the 0.1.5 release history and start the 0.1.6 development line.
+
 ## [0.1.5] - 2026-10-25
 
 - Pin MCP SDK 1.32.2, raise the Zod minimum to 4.6.7, and refresh the affected

package/README.md

@@ -14,18 +14,16 @@ MCP server for LambdaDB using the official TypeScript MCP SDK and the official L
 Package: `@functional-systems/lambdadb-mcp`. Executable: `lambdadb-mcp`.
 Requires Node.js >=22.14.0; CI tests the minimum and current Node 22/24 LTS.
 
-As verified on 2026-10-25 (KST), npm `latest` resolves to `0.1.4`. This checkout
-prepares `0.1.5`; it is not yet published. The `dev` channel advances separately.
-Use an exact published version for reproducibility or the stable channel for
-initial setup. See [release status and policy](RELEASING.md).
-
-[MCP 0.1.4](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.4) is published
-with LambdaDB SDK `0.8.1`, native embedding and native reranking terminology, and
-MCP SDK `1.31.0`. The MCP SDK update includes a 10 MiB stdio receive-buffer limit
-and revised schema-validation error formatting. Existing tool names, wire fields
-and read-only defaults remain unchanged.
-Existing installations need an MCP release containing these changes; upgrading
-the SDK separately does not update them.
+As verified on 2026-10-25 (KST), npm `latest` resolves to `0.1.5`; `dev` advances
+separately. Use an exact published version for reproducibility or the stable
+channel for initial setup. See [release status and policy](RELEASING.md).
+
+[MCP 0.1.5](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.5) is published
+with LambdaDB SDK `0.8.1`, MCP SDK `1.32.2`, patched dependencies and Kiro/Claude
+query-schema compatibility. This checkout starts the next `0.1.6-dev.1` source
+base; check npm for the current published dev version. Existing direct MCP
+installations need the new MCP version and an agent restart. CLI 0.1.5 still pins
+MCP 0.1.4 and needs a subsequent CLI release with an updated pin.
 
 This checkout pins MCP SDK `1.32.2` and requires Zod `^4.6.7`, with patched
 transitive dependencies in the lockfile. It replaces the query tool's top-level
@@ -39,7 +37,7 @@ those features to this stdio-only server. See the
 ```sh
 npx --yes @functional-systems/lambdadb-mcp
 # Pin the stable release:
-npx --yes @functional-systems/lambdadb-mcp@0.1.4
+npx --yes @functional-systems/lambdadb-mcp@0.1.5
 # Or install globally:
 npm install -g @functional-systems/lambdadb-mcp
 lambdadb-mcp
@@ -114,8 +112,8 @@ Optional write tools:
 
 ## API contract and tool inputs
 
-The LambdaDB SDK is pinned to `@functional-systems/lambdadb@0.8.1`, checked against
-the published package and [v0.8.1 release](https://github.com/lambdadb/lambdadb-typescript-client/releases/tag/v0.8.1).
+The LambdaDB SDK is pinned to `@functional-systems/lambdadb@0.10.0`, checked against
+the published package and [v0.10.0 changelog](https://github.com/lambdadb/lambdadb-typescript-client/blob/v0.10.0/CHANGELOG.md).
 This dependency update applies to builds containing this change. Publishing the SDK
 alone does not update previously published or installed MCP packages.
 
@@ -126,11 +124,13 @@ alone does not update previously published or installed MCP packages.
   Omitting `ref` reads from `main`. `consistentRead: true` is supported only by
   Query/Fetch with an omitted ref or a direct Branch ref. List has no `consistentRead`.
 - Query may omit `query` for match-all and accepts `facets` for keyword bucket counts
-  across all matches. Document `size` is 1–100, or 0 when at least one facet is supplied.
+  across all matches. Document `size` is 1–1000, or 0 when at least one facet is supplied.
   Up to five facet fields (including dotted paths) are allowed. Each field's options
   accept only `size`: an integer from 1–100, omitted, or `null`. Omitted/null bucket
   size uses the server default of 10; MCP forwards it unchanged. Empty `facets: {}`
   is accepted except with `size: 0`. Facet results survive inline and `docsUrl` responses.
+- Fetch accepts up to 1000 IDs; List accepts `size` from 1–1000 (server default 100).
+  These expanded read and rerank limits require a supporting server deployment.
 - List also accepts `filter`, `fields`, `includeVectors`, and `partitionFilter`.
   The SDK selects the extended POST endpoint when needed and preserves pagination tokens.
 - Upsert/Delete accept an optional `branch`; omitting it writes to `main`.
@@ -208,7 +208,7 @@ Bayesian requires exactly two signals. Boolean subqueries may combine clauses
 within a signal, but explicit boosts (even `1`) on either signal or its Boolean
 descendants and nested rank-fusion queries are unsupported. Do not supply fusion
 weights. Without rerank, top-level `candidateSize` is required and must satisfy
-`1 <= size <= candidateSize <= 100`; omitted `size` retains the server default of
+`1 <= size <= candidateSize <= 1000`; omitted `size` retains the server default of
 10. The budget is per signal, independent of final output size and `knn.k`.
 
 With rerank, omit top-level `candidateSize` and use `rerank.candidateSize`:
@@ -272,7 +272,7 @@ With write tools enabled, call `lambdadb_create_collection` with:
 
 Then call `lambdadb_upsert_docs` with
 `{"collectionName":"native-articles","docs":[{"id":"one","body":"Restore a saved version."}]}`.
-The source must be a text field; omit the generated vector from documents.
+The source may be an unindexed stored string path; omit the generated vector from documents.
 Use `knn.queryText` instead of `queryVector` for this field, including in either
 Bayesian example above. For example, call `lambdadb_query_collection` with:
 
@@ -285,6 +285,9 @@ Bayesian example above. For example, call `lambdadb_query_collection` with:
 ```
 
 Native embedding dimensions and similarity are optional and belong inside `embedding`.
+Supplied vector dimensions must be integers from 64 to 4096; similarity supports
+only `cosine` or `euclidean`. Model-specific native maxima remain server-validated.
+Existing collections with out-of-contract vector metadata fail SDK response validation.
 MCP does not infer a flag, provider, model or native embedding dimensions/similarity default.
 The SDK rejects `managedEmbedding: false` with `embedding`, and native embedding
 with top-level dimensions/similarity. Caller-provided vectors continue to use
@@ -327,7 +330,7 @@ ordered from lowest to highest relevance (2 KiB each, 8 KiB total UTF-8).
 Omitted/null criteria uses defaults; text, order, nulls and omission are preserved.
 
 Final `size`, vector-leg `knn.k`, and merged `rerank.candidateSize` are separate.
-Require `1 <= size <= candidateSize <= 100`; omitted/null candidateSize defaults
+Require `1 <= size <= candidateSize <= 1000`; omitted/null candidateSize defaults
 on the server to `max(50, size)`, with final size defaulting to 10. MCP never
 increases `k`. Reranking requires a scoring retrieval query, forbids `sort`,
 match-all and filter-only Boolean requests, and preserves ref/consistentRead

package/RELEASING.md

@@ -1,27 +1,33 @@
 # Releasing LambdaDB MCP
 
-## Prepared stable candidate: 0.1.5 (2026-10-25 KST)
-
-The `release/0.1.5` branch promotes reviewed develop commit
-`bf4536f5a8256a4193e8dcea86f1ecedc626294d`, including
-[Kiro schema PR #25](https://github.com/lambdadb/lambdadb-mcp/pull/25) and
-[dependency PR #26](https://github.com/lambdadb/lambdadb-mcp/pull/26), into main.
-Candidate-only changes are package/lock versions and release documentation;
-application source, tests, dependencies and CI match that reviewed source.
-See the [candidate validation record](docs/validation/2026-10-25-0.1.5.md).
-
-As checked on 2026-10-25 (KST), `latest` remains 0.1.4 and no `v0.1.5` tag
-exists. Candidate validation does not publish a package. After review, merge into
-main while preserving ancestry, then obtain explicit authorization before
-creating the annotated `v0.1.5` tag and publishing its non-prerelease GitHub
-Release. The release workflow must test and publish its exact artifact; verify
-registry identity, integrity, provenance and clean-consumer behavior afterward.
-
-The LambdaDB CLI still pins MCP 0.1.4. Stable CLI users receive this fix only
-after a separate CLI pin update and release. After MCP publication, synchronize
-main back into develop with the next dev base through a PR.
-
-## Current stable release: 0.1.4 (2026-10-07 KST)
+## Current stable release: 0.1.5 (2026-10-25 KST)
+
+[v0.1.5](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.5) tags main
+commit `1ae40dcbebea734e34ddde024e0991c8bf3fda64`, which merged
+[release PR #27](https://github.com/lambdadb/lambdadb-mcp/pull/27) with preserved
+ancestry. The user explicitly authorized the annotated tag, non-prerelease
+GitHub Release and npm latest publication. The
+[release workflow](https://github.com/lambdadb/lambdadb-mcp/actions/runs/40169478215)
+passed Node.js 22.14.0 / 22 / 24 validation and published its exact tested artifact
+with OIDC and provenance. Registry snapshot: `latest=0.1.5`, `dev=0.1.5-dev.18`.
+
+The downloaded 15-file stable artifact matched the tagged source and registry
+integrity, passed 37 installed-package tests, and had zero consumer audit
+findings. `npm audit signatures` reported no invalid or missing signatures;
+provenance repository, workflow, tag, commit and artifact digest matched.
+Actual Kiro V2/Sonnet called the published MCP directly against a synthetic
+backend without a resolver substitution. A separate actual development-service
+check verified authentication and collection-list access only. No writes or
+search readiness are claimed. See the
+[validation record](docs/validation/2026-10-25-0.1.5.md). Do not repeat publication
+or move the immutable tag.
+
+`release/sync-0.1.5` brings this main history back into develop with the next
+`0.1.6-dev.1` source base. Merge with preserved ancestry. Eligible develop merges
+can publish dev versions while latest stays on 0.1.5. CLI 0.1.5 still pins MCP
+0.1.4; its separate pin update/release is required for stable CLI users.
+
+## Previous stable release: 0.1.4 (2026-10-07 KST)
 
 [v0.1.4](https://github.com/lambdadb/lambdadb-mcp/releases/tag/v0.1.4) tags main
 commit `f84038962bbdc6f5375b873727d0cf54d843c7b2`, which merged

package/dist/tools/read.js

@@ -17,7 +17,7 @@ const rerankSchema = z.strictObject({
     queryText: z.string().min(1).describe("Required nonblank query text, at most 8 KiB UTF-8, including for raw vector queries."),
     fields: z.array(z.string().min(1)).min(1).max(8).meta({ uniqueItems: true })
         .describe("Unique stored scalar text paths in model input order; separate from returned fields projection."),
-    candidateSize: z.number().int().min(1).max(100).nullable().optional()
+    candidateSize: z.number().int().min(1).max(1000).nullable().optional()
         .describe("Merged candidate cap, at least final size. Omitted/null defaults to max(50, size); never changes knn.k."),
     onFailure: z.enum(["error", "returnOriginal"]).nullable().optional()
         .describe("Omitted/null defaults to error. returnOriginal covers only eligible provider failures."),
@@ -75,10 +75,10 @@ export function registerReadTools(server, config) {
         },
         inputSchema: z.strictObject({
             collectionName: nameSchema,
-            size: z.number().int().min(0).max(100).optional()
-                .describe("Documents to return (1–100), or 0 with nonempty facets."),
+            size: z.number().int().min(0).max(1000).optional()
+                .describe("Documents to return (1–1000), or 0 with nonempty facets."),
             // Preserve SDK/server validation and error classification for free-form queries.
-            candidateSize: z.number().int().optional().describe("Bayesian without rerank requires 1 <= size <= candidateSize <= 100 (size defaults to 10 on the server). With rerank, omit this field and use rerank.candidateSize, whose default is unchanged. Unsupported for other queries; server validates these combinations."),
+            candidateSize: z.number().int().optional().describe("Bayesian without rerank requires 1 <= size <= candidateSize <= 1000 (size defaults to 10 on the server). With rerank, omit this field and use rerank.candidateSize, whose default is unchanged. Unsupported for other queries; server validates these combinations."),
             query: z.record(z.string(), z.any()).optional().describe("Free-form query; omit for match-all. Top-level bayesian is an array of exactly two subqueries, with no explicit boosts on either subquery or its Boolean descendants. Nested rank fusion and fusion weights are unsupported. Server validates the query contract."),
             facets: facetsSchema.optional(),
             rerank: rerankSchema,
@@ -138,7 +138,7 @@ export function registerReadTools(server, config) {
         },
         inputSchema: z.strictObject({
             collectionName: nameSchema,
-            size: z.number().int().min(1).max(100).optional(),
+            size: z.number().int().min(1).max(1000).optional(),
             pageToken: z.string().optional(),
             ref: readRefSchema.optional(),
             filter: z.record(z.string(), z.any()).optional(),
@@ -173,7 +173,7 @@ export function registerReadTools(server, config) {
         },
         inputSchema: z.strictObject({
             collectionName: nameSchema,
-            ids: z.array(z.string().min(1)).min(1).max(100),
+            ids: z.array(z.string().min(1)).min(1).max(1000),
             ref: readRefSchema.optional(),
             consistentRead: z.boolean().optional().describe("true requires a direct branch ref or omitted ref (main)."),
             includeVectors: z.boolean().optional(),

package/dist/tools/write.js

@@ -12,7 +12,7 @@ export function registerWriteTools(server, config) {
         },
         inputSchema: z.strictObject({
             collectionName: nameSchema,
-            indexConfigs: z.record(z.string(), z.any()).refine((value) => Object.keys(value).length > 0, "indexConfigs must contain at least one field.").describe("Field configurations validated by the SDK/server. Native embedding vectors: {type: 'vector', embedding: {provider, model, sourceField, dimensions?, similarity?}}; declare sourceField as text. Native embedding dimensions/similarity belong inside embedding, never at the field top level. Do not combine embedding with managedEmbedding: false. Legacy true is preserved; no provider/model or native embedding defaults are inferred. Caller-provided vectors retain top-level dimensions/similarity."),
+            indexConfigs: z.record(z.string(), z.any()).refine((value) => Object.keys(value).length > 0, "indexConfigs must contain at least one field.").describe("Field configurations validated by the SDK/server. Native embedding vectors: {type: 'vector', embedding: {provider, model, sourceField, dimensions?, similarity?}}; sourceField may be an unindexed stored string path. Native embedding dimensions/similarity belong inside embedding, never at the field top level. Do not combine embedding with managedEmbedding: false. Legacy true is preserved; no provider/model or native embedding defaults are inferred. Caller-provided vectors retain top-level dimensions/similarity. Supplied dimensions must be integers from 64 to 4096; similarity supports only cosine or euclidean. Model-specific native dimension maxima are server-validated."),
             description: z.string().max(255).optional(),
             tags: z.record(z.string().regex(/^[A-Za-z0-9_.-]{1,63}$/), z.string().min(1).max(127).regex(/^[^:#,]+$/))
                 .refine((value) => Object.keys(value).length <= 5, "At most five tags are allowed.")

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-mcp",
-  "version": "0.1.5",
+  "version": "0.1.6-dev.20",
   "private": false,
   "description": "MCP server for LambdaDB data plane",
   "type": "module",
@@ -24,7 +24,7 @@
     "test:package": "node scripts/test-package.mjs"
   },
   "dependencies": {
-    "@functional-systems/lambdadb": "0.8.1",
+    "@functional-systems/lambdadb": "0.10.0",
     "@modelcontextprotocol/sdk": "1.32.2",
     "zod": "^4.6.7"
   },
@@ -62,5 +62,5 @@
     "access": "public",
     "registry": "https://registry.npmjs.org"
   },
-  "gitHead": "1ae40dcbebea734e34ddde024e0991c8bf3fda64"
+  "gitHead": "3d73730f700f785062ba59832a1e506857992dbd"
 }