Connect Cursor, VS Code and Windsurf

All three editors read an MCP config file. Point it at the Gate’s HTTP endpoint, /mcp/native, with an agent key.

Before you start

• A running Deedglass server and an agent key, from the Quickstart.

1. Paste the config

Each block is what deedglass mcp snippet --transport http --client <editor> prints.

Cursor

Put it in .cursor/mcp.json in your project, or ~/.cursor/mcp.json for every project.

.cursor/mcp.json

{
  "mcpServers": {
    "deedglass": {
      "headers": {
        "Authorization": "Bearer dg_test_REPLACE_ME"
      },
      "url": "http://127.0.0.1:8080/mcp/native"
    }
  }
}

VS Code

VS Code reads a root .mcp.json first, then .vscode/mcp.json. It asks for the key once and keeps it in its secret storage.

.mcp.json

{
  "inputs": [
    {
      "description": "Deedglass agent API key (dg_test_… or dg_live_…)",
      "id": "deedglass-api-key",
      "password": true,
      "type": "promptString"
    }
  ],
  "servers": {
    "deedglass": {
      "headers": {
        "Authorization": "Bearer ${input:deedglass-api-key}"
      },
      "type": "http",
      "url": "http://127.0.0.1:8080/mcp/native"
    }
  }
}

Windsurf

Windsurf reads ~/.config/devin/mcp_config.json.

~/.config/devin/mcp_config.json

{
  "mcpServers": {
    "deedglass": {
      "headers": {
        "Authorization": "Bearer dg_test_REPLACE_ME"
      },
      "serverUrl": "http://127.0.0.1:8080/mcp/native"
    }
  }
}

Replace dg_test_REPLACE_ME with your key, then reload the editor’s MCP servers.

2. Or wrap a stdio server

The same deedglass mcp wrap line works in every editor. Cursor’s generated form:

.cursor/mcp.json

{
  "mcpServers": {
    "scratch": {
      "command": "/Users/you/txv/product/bin/deedglass",
      "args": [
        "mcp",
        "wrap",
        "--connector",
        "scratch",
        "--",
        "/usr/local/bin/npx",
        "-y",
        "@modelcontextprotocol/server-filesystem@2026.8.31",
        "/tmp/deedglass-demo"
      ],
      "env": {
        "DEEDGLASS_API_KEY": "dg_test_REPLACE_ME",
        "DEEDGLASS_SERVER": "http://127.0.0.1:8080",
        "PATH": "/usr/local/bin:/opt/homebrew/bin:/usr/bin:/bin"
      }
    }
  }
}

deedglass mcp snippet --client cursor|vscode|windsurf --connector <name> -- <command> [args…] prints yours.

3. Check it

Ask the editor’s agent for something your policy denies. The tool result names the rule and the deed; deedglass actions list shows the same action.

What it doesn’t do

• Editor agents also edit files and run terminal commands without MCP. The Gate governs MCP tool calls only.
• Config file locations change between editor releases. When a path here stops working, run deedglass mcp snippet from the newest CLI.
• A config file with a pasted key is a secret. Keep it out of git, or use VS Code’s prompt.

Next

• Your first policy
• MCP compatibility: the spec revisions and clients tested.