@engramx/mcp 0.16.0-rc.14 → 0.16.0-rc.15

package/README.md

@@ -10,7 +10,7 @@ EngramX speaks MCP from two places, and installing the wrong one is the most com
 |---|---|---|
 | Where it runs | On-chain, at the engram's `/mcp` HTTPS endpoint | On the machine the agent runs on, spawned over stdin/stdout |
 | Credential | OAuth 2.1 bearer token, installed once (an agent connected by sign-in) | The Ed25519 key for this engram, on disk (a paired agent) |
-| Install | Nothing to install — point the MCP client at the URL | `npx @engramx/mcp@0.16.0-rc.14` |
+| Install | Nothing to install — point the MCP client at the URL | `npx @engramx/mcp@0.16.0-rc.15` |
 | Tools | 10 | 19 |
 | Has money tools | No — payment vouchers are signed with a client-held key, which a canister cannot hold ⟨corrected 2026-09-30: no voucher is signed; paying is a ledger approval plus a call made as the buyer's own key, which a canister cannot make on the agent's behalf⟩ | Yes |
 | Docs | [engramx.ai/docs](https://engramx.ai/docs) | this file |
@@ -19,7 +19,7 @@ EngramX speaks MCP from two places, and installing the wrong one is the most com
 package can print the config for it without starting a server:
 
 ```bash
-npx @engramx/mcp@0.16.0-rc.14 connect --canister xxxxx-xxxxx-xxxxx-xxxxx-xxx
+npx @engramx/mcp@0.16.0-rc.15 connect --canister xxxxx-xxxxx-xxxxx-xxxxx-xxx
 ```
 
 That prints the engram's remote MCP URL plus per-client setup for 14 supported MCP clients (11
@@ -44,12 +44,12 @@ tools, the profile/session helpers, or a client-held key you control.
 ## Prerequisites
 
 - Node.js >= 22.12 (inherited from `@engramx/client`, which this package depends on)
-- An engram your agent is paired with (the key for this engram, from `npx @engramx/client@0.16.0-rc.14 pair`)
+- An engram your agent is paired with (the key for this engram, from `npx @engramx/client@0.16.0-rc.15 pair`)
 
 ## Quick Start
 
 ```bash
-ENGRAM_CANISTER_ID=xxxxx-xxxxx-xxxxx-xxxxx-xxx npx @engramx/mcp@0.16.0-rc.14
+ENGRAM_CANISTER_ID=xxxxx-xxxxx-xxxxx-xxxxx-xxx npx @engramx/mcp@0.16.0-rc.15
 ```
 
 ## Configuration
@@ -69,7 +69,7 @@ Add to your Claude Desktop config (`~/Library/Application Support/Claude/claude_
   "mcpServers": {
     "engramx": {
       "command": "npx",
-      "args": ["@engramx/mcp@0.16.0-rc.14"],
+      "args": ["@engramx/mcp@0.16.0-rc.15"],
       "env": {
         "ENGRAM_CANISTER_ID": "xxxxx-xxxxx-xxxxx-xxxxx-xxx",
         "ENGRAM_SESSION_KEY_PATH": "/Users/you/.engramx/session.key"
@@ -88,7 +88,7 @@ Add to `.cursor/mcp.json` in your project root:
   "mcpServers": {
     "engramx": {
       "command": "npx",
-      "args": ["@engramx/mcp@0.16.0-rc.14"],
+      "args": ["@engramx/mcp@0.16.0-rc.15"],
       "env": {
         "ENGRAM_CANISTER_ID": "xxxxx-xxxxx-xxxxx-xxxxx-xxx",
         "ENGRAM_SESSION_KEY_PATH": "/Users/you/.engramx/session.key"
@@ -106,7 +106,7 @@ from mcp.client.stdio import stdio_client
 
 server = StdioServerParameters(
     command="npx",
-    args=["@engramx/mcp@0.16.0-rc.14"],
+    args=["@engramx/mcp@0.16.0-rc.15"],
     env={
         "ENGRAM_CANISTER_ID": "xxxxx-xxxxx-xxxxx-xxxxx-xxx",
         "ENGRAM_SESSION_KEY_PATH": "/path/to/session.key",
@@ -125,7 +125,7 @@ Any MCP-compatible client can spawn the server over stdio:
 ```bash
 ENGRAM_CANISTER_ID=xxxxx-xxxxx-xxxxx-xxxxx-xxx \
 ENGRAM_SESSION_KEY_PATH=/path/to/session.key \
-npx @engramx/mcp@0.16.0-rc.14
+npx @engramx/mcp@0.16.0-rc.15
 ```
 
 The server communicates over stdin/stdout using the MCP protocol. Set environment variables for authentication.
@@ -215,7 +215,7 @@ what else the credential carries.
 2. Generate an agent invite in the engram dashboard
 3. Pair your agent:
    ```bash
-   npx @engramx/client@0.16.0-rc.14 pair <invite-code> --engram <canister-id>
+   npx @engramx/client@0.16.0-rc.15 pair <invite-code> --engram <canister-id>
    ```
    ⟨2026-10-03⟩ Every pairing command in this README names the package and the version it ships
    with. Before, it called the globally installed `engramx` command, which runs whatever version is
@@ -231,7 +231,7 @@ Point the published server at a local replica:
 ```bash
 ENGRAM_CANISTER_ID=<local-canister-id> \
 ENGRAM_HOST=http://localhost:4943 \
-npx @engramx/mcp@0.16.0-rc.14
+npx @engramx/mcp@0.16.0-rc.15
 ```
 
 ⟨2026-09-30: this section began with building the server from a clone of its source, and the
@@ -241,7 +241,7 @@ came out; the published package is all you need to run or test the server.⟩
 Inspect with the MCP Inspector:
 
 ```bash
-npx @modelcontextprotocol/inspector -- npx @engramx/mcp@0.16.0-rc.14
+npx @modelcontextprotocol/inspector -- npx @engramx/mcp@0.16.0-rc.15
 ```
 
 ## Troubleshooting
@@ -250,7 +250,7 @@ npx @modelcontextprotocol/inspector -- npx @engramx/mcp@0.16.0-rc.14
 The server exits with a clear error. Set the environment variable to your engram canister ID.
 
 **The key for this engram was not found**
-Generate one with `npx @engramx/client@0.16.0-rc.14 pair`. The default path is `~/.engramx/session.key`. Override with `ENGRAM_SESSION_KEY_PATH`.
+Generate one with `npx @engramx/client@0.16.0-rc.15 pair`. The default path is `~/.engramx/session.key`. Override with `ENGRAM_SESSION_KEY_PATH`.
 
 **Canister unreachable**
 Check that `ENGRAM_HOST` is correct (default: `https://ic0.app` for mainnet). For local development, use `http://localhost:4943`. Verify network connectivity.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@engramx/mcp",
-  "version": "0.16.0-rc.14",
+  "version": "0.16.0-rc.15",
   "description": "MCP server for EngramX — persistent, decentralized agent memory",
   "license": "Apache-2.0",
   "author": "EngramX <developer@engramx.ai>",
@@ -16,7 +16,7 @@
     "access": "public"
   },
   "dependencies": {
-    "@engramx/client": "^0.16.0-rc.14",
+    "@engramx/client": "^0.16.0-rc.15",
     "@icp-sdk/core": "^6.1.0",
     "@modelcontextprotocol/sdk": "^1.32.1",
     "zod": "^4.6.5"