Claude Code

Claude Code supports MCP out of the box. Two minutes total.

Install

Add a .mcp.json at the repo root (or to your global Claude Code settings):

{
"mcpServers": {
  "memclaw": {
    "url": "https://memclaw.net/mcp",
    "headers": { "X-API-Key": "mc_xxx" }
  }
}
}

Restart Claude Code. The memclaw_* tools become available — Claude Code will surface them to you on first use and ask permission like any other tool.

Going to production: use a per-agent key

The mc_ quickstart key above is a tenant-scoped credential — fine for personal use. Anything that ships a fleet of agents should bind each agent to its own agent-scoped credential for trust gating, fleet membership, and per-agent keystones. The MCP server accepts the credential on either X-API-Key: mc_… or Authorization: Bearer mc_… — both tenant-scoped and agent-scoped credentials share the mc_ prefix; scope is set at mint time. See Per-agent keys for the atomic provisioning flow.

Using it

Just talk to the model:

Remember that this repo uses pnpm, not npm.

What did we decide about the auth flow?

The tool calls happen automatically. See the full tool surface in the agent skill at /docs/agents.

Tips

• Use a per-fleet API key so memories from different projects stay separate. Set tenant_id to the project name.

• The Caura memclaw skill (~/.claude/skills/memclaw) ships richer prompting. Install it:

  curl -s "https://memclaw.net/api/v1/install-skill?agent=claude-code" | bash