Invite-only.
Dock
Connect

Cline

Cline exposes MCP server management from its side panel. Add Dock through the UI, or edit the backing JSON directly.

Client
Cline
VS Code extension. MCP config via side panel or cline_mcp_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

  • VS Code with the Cline extension installed.
  • A Dock dk_ key.
Config file
~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
UI shortcut
Cline side panel · MCP Servers icon · Add MCP server. Pastes the JSON for you.
Reload
Cline reloads on save. No VS Code restart needed.
cline_mcp_settings.json (merge)json
{
  "mcpServers": {
    "dock": {
      "url": "https://trydock.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer dk_live_c914f1c6..."
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Keep autoApprove empty for Dock: every tool call mutates or reads shared state, so manual approval gives you a chance to catch an agent that's about to overwrite the wrong workspace.

Verify

In Clinetext
Use the dock MCP server and list my workspaces.

Troubleshooting

Symptom
Fix
Dock listed but shows "connecting..." forever
Cline occasionally fails the initial MCP handshake on remote servers. Toggle disabled to true, save, toggle back to false, save. Cline reconnects cleanly.
Tools work once, then fail
VS Code reloaded the window, killing the stdio pipe. This isn't a concern for Dock (remote MCP), but if you see it you're probably on an older Cline build. Update the extension.

Related