Invite-only.
Dock
Connect

Cursor

Add Dock to Cursor and your AI pair-programmer can read, write, and co-edit any Dock workspace from inside the editor. Two minutes end-to-end.

Client
Cursor
Editor-native. Supports remote MCP over HTTP with Bearer auth.
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

  • A recent Cursor build (MCP remote support landed in 2025).
  • A Dock dk_ key. Mint one in Settings · API keys, or with npx @trydock/cli key new.
Config file (user)
~/.cursor/mcp.json
Config file (project)
.cursor/mcp.json in the repo root. Project config overrides user config for that workspace only.
Reload
Cursor reloads MCP servers on save. Open the MCP panel (Cmd/Ctrl + Shift + P · "MCP: List Servers") to confirm Dock went green.
~/.cursor/mcp.jsonjson
{
  "mcpServers": {
    "dock": {
      "url": "https://trydock.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer dk_live_c914f1c6..."
      }
    }
  }
}

Verify

Ask Cursor's agenttext
@dock list my workspaces

Troubleshooting

Symptom
Fix
Dock shows red in the MCP panel
Usually a 401. Open Settings · API keys on trydock.ai, confirm the key is still listed, re-copy, re-paste. Make sure the value is exactly Bearer dk_... (space between Bearer and token).
Agent "doesn't see" the Dock tools
Cursor scopes tools per composer. Type @dock once in the composer to attach the MCP. After that, the 37 tools show up in the tool picker for every follow-up turn.
Config changes don't take effect
Fully quit and relaunch Cursor (not just close the window). Some MCP registry state is process-scoped.

Related