Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Connect
cline logo

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_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.

Frequently asked questions

How do I connect Dock to Cline?
Add Dock as a remote MCP server in Cline. Either let Cline's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Cline's MCP config under the `Authorization: Bearer dk_…` header.
Does Cline work with Dock's MCP server?
Yes. Dock exposes 43 MCP tools at `https://trydock.ai/api/mcp` over HTTP transport with OAuth 2.1 + DCR and Bearer-token auth. Any MCP-spec-compliant client, including Cline, discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces Cline can write to?
When you mint the `dk_` key for Cline in Settings → API keys, pick the workspace from the dropdown. The key returns 403 on every other workspace regardless of what the prompt asks. To scope across multiple, mint multiple keys or add the agent as an explicit member of each. Learn more →
How do I see what Cline did in my Dock workspace?
Open the workspace in your browser. Every row Cline created or updated is stamped with the agent's identity (orb + name) in the createdBy / updatedBy field. The workspace activity feed shows every action chronologically. Learn more →
How do I undo a row Cline wrote to Dock?
Open the row, click the kebab menu, choose Delete (soft-delete preserves history). For bulk reverts use the activity feed to find the agent's session and delete its rows in batch. To prevent future writes, revoke Cline's `dk_` key in Settings → API keys.
Can multiple Cline sessions share state through Dock?
Yes. Every Cline session reads and writes the same workspace, so handoffs across machines or across long-running multi-session workflows just work. The Dock workspace IS the shared state; no separate message bus required.
Does Cline need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: Cline hits Dock's discovery endpoint at `/.well-known/oauth-authorization-server` and auto-registers as a client. The `dk_` Bearer token path is fine for owned-code agents and CI scripts; pick whichever fits your stack. Learn more →
How do I add Dock as an MCP server in Cline?
Cline's MCP support uses the standard `claude_dev_mcp_settings.json` (or VS Code workspace settings under `cline.mcpServers`). Add Dock with URL + Bearer. Restart Cline; the 43 Dock tools surface in chat.
Why doesn't Cline see Dock tools after I added the MCP server?
Cline reads MCP config on extension activation. Reload VS Code (⌘-shift-P → Reload Window) after editing the MCP settings. Confirm the server shows green-dot in Cline's MCP panel.
Can Cline write its plan + execution log to a Dock workspace?
Yes. Tell Cline at session start to mirror its plan to a Dock doc surface and append execution logs. Your team tracks Cline's progress in real time in the Dock UI without watching the IDE.

Related

Updated