VS Code

VS Code-compatible MCP clients can use UnifiedMemory through the same remote MCP endpoint as Cursor and Codex.

Registry contract

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

Field	Value
Integration ID	vscode
Label	VS Code
Tier	remote_mcp_client
Setup mode	editor_mcp_config
Agent ID	vscode
App ID	vscode
Source app / actor	source_app=vscode, agent_id=vscode; key metadata wins over request body hints
Default scope	own
Config paths	.vscode/mcp.json, user MCP config
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 workspace instructions call capture tools.

Install command(s)

Merge the rendered servers.unified-memory block into VS Code MCP settings.

Verify command(s)

Reload VS Code
Use MCP command palette to confirm UnifiedMemory tools

Config template

{
  "servers": {
    "unified-memory": {
      "headers": {
        "Authorization": "Bearer {{KEY_REF}}"
      },
      "type": "http",
      "url": "{{MCP_URL}}"
    }
  }
}

Risk notes

• VS Code uses top-level servers, not Cursor's mcpServers shape.
• Do not commit literal keys to a public workspace.

Official upstream docs

https://code.visualstudio.com/docs/copilot/reference/mcp-configuration

Scope and capabilities

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

Config template

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

Verify

Use your VS Code client's MCP server status view or tool list. Then run one recall canary and one Courtroom read.

Memory behavior

• Workspace-specific memory remains scoped to the key's identity.
• Shared owner facts require promotion.
• Review/quarantine/forensic rows are operator state, not prompt context.

Troubleshooting

If tools list but calls fail, check that the key has both MCP access and the specific memory capability being invoked.