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.

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_id in 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.