@functional-systems/lambdadb-cli 0.1.6-dev.21 → 0.1.6-dev.22

package/CHANGELOG.md

@@ -4,6 +4,9 @@
 
 ### Maintenance
 
+- Pin MCP 0.1.5 for Kiro/Claude-compatible query schemas and patched MCP
+  dependencies; preserve credential forwarding and explicit write-tool opt-in.
+
 - Synchronize the 0.1.5 release history and start the 0.1.6 development line.
 - Update the Homebrew formula to verified stable 0.1.5 and run the installed
   init contracts alongside the existing CLI contracts.

package/README.md

@@ -225,11 +225,13 @@ atomic replacement per file, not a transaction across files: a disk/permission
 failure can leave a partial installation; inspect the displayed paths and rerun.
 
 Agent settings launch `npx -y @functional-systems/lambdadb-cli@<installed-version> mcp`,
-which runs the existing `@functional-systems/lambdadb-mcp@0.1.4` stdio package.
+which runs the existing `@functional-systems/lambdadb-mcp@0.1.5` stdio package.
 No npx cache path is saved. The exact CLI version must be published before an
 agent can fetch it; a source checkout/unpublished tarball alone does not provide
 that registry version. Node/npm and `npx` must be on the agent's PATH; first launch
 may download both packages and requires npm registry access.
+After upgrading the CLI, rerun init for the same agents and scope to refresh
+their exact CLI version pin, then restart/reload the agent with the key available.
 
 The `mcp` bridge reads the selected key from the agent environment at startup and
 maps CLI endpoint/project/key to MCP's `LAMBDADB_BASE_URL`,

package/dist/mcp.d.ts

@@ -1,4 +1,4 @@
 import type { Config } from './config.js';
-export declare const mcpPackage = "@functional-systems/lambdadb-mcp@0.1.4";
+export declare const mcpPackage = "@functional-systems/lambdadb-mcp@0.1.5";
 export declare function mcpEnvironment(config: Config, writeTools: boolean): NodeJS.ProcessEnv;
 export declare function serveMcp(config: Config, writeTools: boolean): Promise<number>;

package/dist/mcp.js

@@ -1,7 +1,7 @@
 import { spawn } from 'node:child_process';
 import { InputError } from './errors.js';
 // Stable stdio package; this CLI only adapts credentials and process lifecycle.
-export const mcpPackage = '@functional-systems/lambdadb-mcp@0.1.4';
+export const mcpPackage = '@functional-systems/lambdadb-mcp@0.1.5';
 export function mcpEnvironment(config, writeTools) {
     return {
         ...process.env,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@functional-systems/lambdadb-cli",
-  "version": "0.1.6-dev.21",
+  "version": "0.1.6-dev.22",
   "private": false,
   "description": "Project-scoped LambdaDB command-line tools",
   "type": "module",
@@ -55,5 +55,5 @@
     "url": "https://github.com/lambdadb/lambdadb-cli/issues"
   },
   "license": "Apache-2.0",
-  "gitHead": "1fad1dbf656f6e511a69eb8244f6d2e05586573f"
+  "gitHead": "5f3a7ac87912b9ffb08324e7ee91b1e68694c61a"
 }

package/src/mcp.ts

@@ -3,7 +3,7 @@ import type { Config } from './config.js';
 import { InputError } from './errors.js';
 
 // Stable stdio package; this CLI only adapts credentials and process lifecycle.
-export const mcpPackage = '@functional-systems/lambdadb-mcp@0.1.4';
+export const mcpPackage = '@functional-systems/lambdadb-mcp@0.1.5';
 
 export function mcpEnvironment(config: Config, writeTools: boolean): NodeJS.ProcessEnv {
   return {