Cursor

Open Cursor settings → MCP → Add New Server, or edit ~/.cursor/config.json directly:

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

Restart Cursor. The memclaw_* tools become available in chat and inside Composer.

Set tenant_id to the project / workspace name so different repos keep their memories isolated. Cursor doesn't surface tool calls as prominently as Claude Code — if the model isn't using Caura, ask it explicitly to "use the memclaw tools to remember/recall…".

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 team or fleet should bind each agent to its own agent-scoped credential for trust gating, fleet membership, and per-agent keystones. Both kinds use the mc_ prefix on the wire; scope is set at mint time. See Per-agent keys.

Capture work automatically — the Interviewer

The MCP setup above lets Cursor call Caura. Separately, the Interviewer can read Cursor's own agent-transcripts (~/.cursor/projects/…/agent-transcripts) on a schedule and synthesize what the agent did into typed memories — no manual memclaw_write. It's read-only, opt-in per tenant, and gated behind a project allowlist; wire it with memclaw-interviewer --harness cursor or a ~/.cursor/hooks.json sessionEnd hook. See Interviewer → Setup.