Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Connect
windsurf logo

Windsurf

Add Dock to Windsurf's Cascade agent with a single MCP config entry. Works the same in Cascade Chat and in agent mode.

Client
Windsurf
Cascade agent. Remote MCP via mcp_config.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

  • Windsurf installed and signed in (any plan with Cascade).
  • A Dock dk_ key.
Config file
~/.codeium/windsurf/mcp_config.json
Reload
Windsurf rescans MCP configs on session start. Open the Cascade panel · "Restart MCP servers" to refresh without a full relaunch.
~/.codeium/windsurf/mcp_config.jsonjson
{
  "mcpServers": {
    "dock": {
      "url": "https://trydock.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer dk_c914f1c6..."
      }
    }
  }
}

Verify

Ask Cascadetext
Using the dock MCP, list my workspaces.

Troubleshooting

Symptom
Fix
Cascade says "no MCP servers available"
Config parse error. Run cat ~/.codeium/windsurf/mcp_config.json | jq . to confirm the JSON is valid. Trailing commas are the usual culprit.
401 on every tool call
Bearer header malformed. Check there's a space between Bearer and the token, and that you haven't wrapped the token in additional quotes.
Dock tools disappear mid-session
Windsurf occasionally drops MCP connections on long sessions. "Restart MCP servers" from the Cascade panel reconnects without losing conversation state.

Frequently asked questions

How do I connect Dock to Windsurf?
Add Dock as a remote MCP server in Windsurf. Either let Windsurf's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Windsurf's MCP config under the `Authorization: Bearer dk_…` header.
Does Windsurf 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 Windsurf, discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces Windsurf can write to?
When you mint the `dk_` key for Windsurf 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 Windsurf did in my Dock workspace?
Open the workspace in your browser. Every row Windsurf 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 Windsurf 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 Windsurf's `dk_` key in Settings → API keys.
Can multiple Windsurf sessions share state through Dock?
Yes. Every Windsurf 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 Windsurf need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: Windsurf 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 Windsurf?
Open Windsurf Settings → MCP, click Add Server. Set Type to HTTP, URL to `https://trydock.ai/api/mcp`, paste your `dk_` Bearer token under Headers. Restart Windsurf and the 43 Dock tools appear in Cascade chat.
Why does Windsurf's Cascade not surface Dock tools?
Windsurf only loads MCP servers on startup; if you added Dock mid-session, restart. Confirm the server shows green in Settings → MCP. If it's red, the auth header is wrong (look for `Bearer ` with the space prefix).
How do I have Windsurf write generated docs to a Dock workspace?
Ask Cascade `use the Dock MCP to append a section to my product-spec doc`. Cascade calls `append_doc_section` with markdown; the section lands at the end of the doc body and your team sees it via SSE in real time.

Related

Updated