Stratum

Setup · Watchlist

Framework setup

Publisher instructions.

Source evidence observed Oct 13, 2026.

Additional setup details required — see the specific gaps below.

1. 1

   Install framework / library

   Publisher instructions

   Node 22+ required. Register official stratum-mcp executable from @smartmemory/stratum; restart client.

   Publisher: Node >= 22, `npm install -g @smartmemory/stratum` or MCP config command npx with args ['-y','-p','@smartmemory/stratum','stratum-mcp']; Python engine retired.

   install cli and mcp binary · Publisher instructions

   npm install -g @smartmemory/stratum

   Copy

   publisher documented install or registration · Publisher instructions

   npm install @smartmemory/stratum

   Copy
2. 2

   Configure / authenticate

   MCP100 setup guide

   Node.js >=22. In Claude Code .mcp.json register {"mcpServers":{"stratum":{"command":"npx","args":["-y","-p","@smartmemory/stratum","stratum-mcp"]}}}. Avoid retired Python server and old v0.x specs.

   {
     "mcpServers": {
       "stratum": {
         "args": [
           "-y",
           "-p",
           "@smartmemory/stratum",
           "stratum-mcp"
         ],
         "command": "npx"
       }
     }
   }

   Copy
3. 3

   Check connection

   Suggested check

   Check that `stratum_plan` and `stratum_audit` tools are discoverable; validate a non-mutating sample v1 spec before any real flow execution.

4. 4

   Remove / uninstall / revoke

   MCP100 setup guide

   Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.

   Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.

   Local-only Stratum MCP server does not require account tokens in documented setup; provider credential revocation not applicable.