Connect Claude Desktop

Claude Desktop starts MCP servers as local processes. Deedglass gives it one: a small bridge to the Gate, or a wrapper around a server you already use.

Before you start

A running Deedglass server and an agent key. The Quickstart gives you both.
The deedglass binary on disk. Claude Desktop needs its full path.

1. Add the bridge

deedglass mcp serve speaks MCP over stdio to Claude Desktop and HTTP to the server’s /mcp/native. This is the config deedglass mcp snippet --transport http --client claude-desktop prints:

{
  "mcpServers": {
    "deedglass": {
      "args": [
        "mcp",
        "serve",
        "--connector",
        "native"
      ],
      "command": "/Users/you/txv/product/bin/deedglass",
      "env": {
        "DEEDGLASS_API_KEY": "dg_test_REPLACE_ME",
        "DEEDGLASS_SERVER": "http://127.0.0.1:8080"
      }
    }
  }
}

Open Claude Desktop › Settings › Developer › Edit Config, paste it inside mcpServers, set command to the output of which deedglass and DEEDGLASS_API_KEY to your key, then quit and reopen Claude Desktop.

2. Or wrap a server it already runs

Put deedglass mcp wrap --connector <name> -- in front of the server’s own command. The generated config for the demo’s filesystem server:

{
  "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"
      }
    }
  }
}

Make yours with deedglass mcp snippet --client claude-desktop --connector <name> -- <command> [args…]. PATH is set because Claude Desktop starts servers without your shell’s PATH.

3. Check it

Ask Claude to list the files it may see, then to delete one. The delete comes back blocked by policy, with the rule and the deed id in the tool result, and Claude Desktop shows it as a normal tool answer.

What it doesn’t do

Claude Desktop keeps the key in its config file in plain text. Use a dg_test_ key with only the default scopes, and roll it if the file leaves your machine.
It doesn’t install anything: you paste the config yourself.
Tools Claude Desktop has outside MCP never reach the Gate.

Connect Claude Desktop

1. Add the bridge

2. Or wrap a server it already runs

3. Check it

What it doesn’t do

Next