CLI & commands

The @stratta/mcp package is both the MCP server and a small CLI for setup. You rarely run it directly. Your Claude client launches it. These commands cover install and authentication.

Add to Claude Code#

claude mcp add stratta --scope user -- npx -y @stratta/mcp

--scope user registers the server for your user, so it is there in every project. Without it, the command writes to the current folder's config and the server exists only there.

Shortcut: stratta#

Every command works through npx, but a global install gives you a shorter name:

npm install -g @stratta/mcp

stratta doctor
stratta whoami

The global install is for you only: your agent launches the server through npx, and keeps working without it.

Log in#

npx -y @stratta/mcp login

Opens your browser on Stratta, where you see which machine is asking for access and for which organisation, then you authorise it. The key comes back over an ephemeral port bound to 127.0.0.1 and is written to ~/.stratta/config.json (owner-only, mode 0600). Run it again anytime to replace the key.

Without a browser#

npx -y @stratta/mcp login --paste

Waits for a key created at Intégrations › Clés d’API (API keys), input hidden. For a managed machine or CI, the key can also come from the environment:

claude mcp add stratta --scope user --env STRATTA_API_KEY=sk_strt_xxx -- npx -y @stratta/mcp

Add to Claude Desktop#

After login, add the server to claude_desktop_config.json (Settings → Developer → Edit Config):

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

See Install in Claude Desktop for the full walkthrough, including keeping the key in the config via an env block.

Global install (optional)#

npm install -g @stratta/mcp

Then reference the binary directly instead of npx:

{
  "mcpServers": {
    "stratta": {
      "command": "stratta-mcp"
    }
  }
}

Run the server directly#

For local testing only. Your Claude client normally does this:

npx -y @stratta/mcp

It connects over stdio and logs to stderr (stdout is reserved for the MCP protocol). Inspect it with the official MCP inspector:

npx @modelcontextprotocol/inspector npx -y @stratta/mcp

Simple mode and tool families#

By default the local server announces all 59 tools (full mode), about 67,000 characters of schemas that the agent reads in every conversation. Simple mode announces only the 10 norm-reading tools (about 11,000 characters).

claude mcp add stratta --scope user -- npx -y @stratta/mcp --simple

The families: norms (always on: get_methodology, whoami, list_norms, get_toc, get_subtree, get_section, search_in_norm, search_corpus, get_cross_refs, get_figure), dossiers (dossiers, questions, decisions, attachments, templates, deliverables, office methods), sites (the site sheet) and ingest (ingestion, local only). An unknown family is ignored.

When to choose what. Simple mode is enough for an agent that reads norms: less context used, faster answers. Add dossiers or sites when you work on a project. Keep full mode for ingestion, or while you do not yet know what you need.

For the remote connector, no command line is needed: on AI Agents, each agent's Tools menu offers All tools, Norms and dossiers, Norms and sites and Simple: norms only. The agent sees the change the next time it connects. Only the announced list is filtered: a call to a hidden tool still works.

Command summary#

Related#