Cursor

Cursor should connect through the remote MCP endpoint with a scoped key. Use it for project recall, Courtroom inspection, and controlled writeback from coding sessions.

Registry contract

This section is generated from integrations/agent_integrations.registry.json. Edit the registry or generator, not this block.

Field	Value
Integration ID	cursor
Label	Cursor
Tier	remote_mcp_client
Setup mode	editor_mcp_config
Agent ID	cursor
App ID	cursor
Source app / actor	source_app=cursor, agent_id=cursor; key metadata wins over request body hints
Default scope	own
Config paths	~/.cursor/mcp.json, .cursor/mcp.json
Capabilities	memory.read, memory.write, memory.recall, memory.delete, agent.context, agent.writeback, mesh.read, evidence.read, courtroom.read, canary.read
Supported tools	um_store, um_search, um_profile, um_courtroom

Capture policy

MCP tool calls are explicit; no automatic transcript writeback unless Cursor agent instructions call capture tools.

Install command(s)

Merge the rendered mcpServers.unified-memory block into Cursor MCP settings.

Verify command(s)

Reload Cursor
List MCP tools or run one memory search

Config template

{
  "mcpServers": {
    "unified-memory": {
      "headers": {
        "Authorization": "Bearer {{KEY_REF}}"
      },
      "url": "{{MCP_URL}}"
    }
  }
}

Risk notes

• Cursor uses top-level mcpServers.
• Do not overwrite existing MCP servers.

Official upstream docs

https://docs.cursor.com/advanced/model-context-protocol

Scope and capabilities

Setting	Value
Source app	cursor
Default container	jeethendra
Default scope	own
MCP URL	https://edge-api.jithendranara.dev/mcp

Config template

Add a server entry like this to your Cursor MCP config:

{
  "mcpServers": {
    "unified-memory": {
      "url": "https://edge-api.jithendranara.dev/mcp",
      "headers": {
        "Authorization": "Bearer <scoped-key>"
      }
    }
  }
}

Verify

Use Cursor's MCP tool list and run a recall canary. The selected key should show Cursor-scoped capabilities and agent_scope=own.

Writeback behavior

Cursor should retain durable implementation decisions, file-level fixes, and verified tool outcomes. It should not store entire code-review chats or copied terminal logs as a single memory.