Invite-only.
Dock
Connect

Zed

Zed calls MCP servers "context servers" in its Assistant panel. Drop Dock into settings.json and it becomes a callable context for every Assistant conversation.

Client
Zed
Editor with agentic panel. Context servers in settings.json.
HTTP JSON-RPC (streamable-http)
Dock MCP
trydock.ai/api/mcp
37 tools · OAuth 2.1 + DCR · Bearer
Auth path
1
Mint a dk_ key in Dock Settings → API keys.
2
Paste it as Authorization: Bearer dk_… in the client config.
3
Client calls Dock MCP directly on every request.

Prerequisites

  • Zed installed (macOS or Linux).
  • A Dock dk_ key.
Config file
~/.config/zed/settings.json (Linux/macOS) or open via Zed Preferences · Settings.
Reload
Zed applies settings on save. No restart needed.
~/.config/zed/settings.json (merge)json
{
  "context_servers": {
    "dock": {
      "command": {
        "path": "npx",
        "args": ["-y", "@trydock/mcp"],
        "env": {
          "DOCK_API_KEY": "dk_live_c914f1c6..."
        }
      }
    }
  }
}

Zed's context-server schema only accepts stdio today. Dock ships an official npm bridge that forwards stdio JSON-RPC to trydock.ai/api/mcp: @trydock/mcp. When Zed adds first-class remote MCP support, swap this entry for a direct URL config.

Verify

In the Assistant paneltext
@dock list my workspaces

Troubleshooting

Symptom
Fix
Context server shows "failed to start"
The npx bridge couldn't run. Check that Node 20+ is on PATH (node --version). If you're using nvm, Zed may not see the shim; use the absolute path to npx.
Dock tools not offered by the Assistant
Zed loads context servers lazily. Type @dock in the Assistant panel to attach the context explicitly.

Related