Claude Code
Claude Code uses UnifiedMemory through the remote MCP endpoint. It should get a Claude-scoped key with own-agent scope and only the capabilities needed for MCP tools.
Registry contract
This section is generated from integrations/agent_integrations.registry.json. Edit the registry or generator, not this block.
| Field | Value |
|---|---|
| Integration ID | claude-code |
| Label | Claude Code |
| Tier | remote_mcp_client |
| Setup mode | http_mcp |
| Agent ID | claude-code |
| App ID | claude |
| Source app / actor | source_app=claude, agent_id=claude-code; key metadata wins over request body hints |
| Default scope | own |
| Config paths | .mcp.json, ~/.claude.json, ~/.claude/settings.json |
| Capabilities | memory.read, memory.write, memory.recall, memory.delete, agent.context, agent.writeback, mesh.read, evidence.read, courtroom.read, canary.read |
| Supported tools | claudeBootstrap, claudeCapture, claudeStatus, um_store, um_search, um_profile, um_courtroom |
Capture policy
MCP-first recall and explicit capture; hooks may capture Edit, Write, Bash, and Task outcomes while skipping passive Read/Glob/Grep noise.
Install command(s)
claude mcp add --transport http --scope user --header "Authorization: Bearer {{KEY_REF}}" unified-memory {{MCP_URL}}
Verify command(s)
claude mcp list
claude mcp get unified-memory
Environment
{
"UNIFIED_MEMORY_API_KEY": "{{KEY_ENV_REF}}",
"UNIFIED_MEMORY_CONTAINER": "{{CONTAINER_TAG}}"
}
Risk notes
- Keep bearer keys in local user config or environment.
- Use user scope for machine setup; project scope only in trusted repos.
Official upstream docs
https://docs.anthropic.com/en/docs/claude-code/mcp
Scope and capabilities
| Setting | Value |
|---|---|
| Source app | claude |
| Default container | jeethendra |
| Default scope | own |
| Main endpoint | https://edge-api.jithendranara.dev/mcp |
Expected capabilities include recall/search, retain/writeback, agent context, Courtroom read, and canary/status checks.
Install
Issue a Claude-scoped key from Connections, then run:
claude mcp add --transport http --scope user \
--header "Authorization: Bearer <scoped-key>" \
unified-memory https://edge-api.jithendranara.dev/mcp
The option order matters: transport, scope, and header come before the server name and URL.
Verify
claude mcp list
Then ask Claude Code to list UnifiedMemory tools or run a memory recall canary. Verification should prove the selected key works; a browser-session preflight is not enough.
Writeback behavior
Claude should save durable outcomes, project decisions, and verified tool results. It should not retain whole assistant answers, greetings, terminal noise, or injected memory blocks.
Risk notes
- If Claude supplies an
agent_idin a tool body, UnifiedMemory should still use the key-bound Claude identity. - Cross-agent handoff should be explicit and limited to allowed memory refs.
Next steps
- Read Connect an Agent.
- Inspect memory with Courtroom.