@engramx/owner-mcp
v0.4.0
Published
Owner-side MCP server for EngramX — reserve, activate, and check an engram YOU own, from any MCP host. The owner counterpart to @engramx/mcp (the operator server); it never operates memory.
Readme
@engramx/owner-mcp
The owner-side MCP server for EngramX — reserve, activate, and check an engram you own, from any MCP host (Claude Desktop, Codex, …).
It is the owner counterpart to @engramx/mcp (the operator server). This server never operates
memory — no read, no append. That is the append-only operator surface, kept in a separate package so an
operator host never gains owner powers.
| | lib / CLI | MCP server |
| --- | --- | --- |
| owner (create + own) | @engramx/owner | @engramx/owner-mcp ← this |
| operator (append-only) | @engramx/client | @engramx/mcp |
Reserve, then activate
The tools map to EngramX's cycle anti-drain:
engram_status— read-only: do you have nothing, a free reservation, or a live engram?engram_reserve— a free registry record (~$0). No canister, no spend. Idempotent.engram_activate— spawns the live canister (the platform funds it). The committing step.
Because reserving is free, a speculative "create" never wastes cycles — the host's approval prompt on
engram_activate is the natural gate on the actual spend.
Configure (MCP host mcpServers entry)
{
"command": "npx",
"args": ["-y", "@engramx/owner-mcp"],
"env": {
"ENGRAMX_REGISTRY": "<registry-canister-id>", // required
"ENGRAMX_OWNER_KEY_PATH": "~/.engramx/owner.key" // optional; default shown
// or: "ENGRAMX_OWNER_ICP_IDENTITY": "<icp-cli identity name>"
// local dev: "ENGRAMX_LOCAL": "1"
}
}The signing key is yours — EngramX never holds it. A single local key is a total-loss risk if lost; back it up, or use your icp-cli identity (or the web wizard with a wallet for real recovery).
After activating
You own the engram. To let an agent read/append its memory, connect it as an operator — a
separate, append-only step: npx @engramx/client pair <invite-code> --engram <id>. Owner ≠ operator,
by design.
Honesty
The record is tamper-evident, not immutable (the owner can overwrite; every change is a signed entry anyone can verify). Reserving and activating are free to you (the platform funds the spawn); paying to create is not a thing. Nothing is on a public fleet yet.
