Connect
Claude Desktop
Claude Desktop supports remote MCP connectors in Settings. Paste Dock's URL, approve in the browser, done. No JSON editing required.
Client
Claude Desktop
macOS and Windows app. Remote MCP via Settings · Connectors.
HTTP JSON-RPC (streamable-http)
Dock MCP
trydock.ai/api/mcp
37 tools · OAuth 2.1 + DCR · Bearer
Auth path
1
Client fetches
/.well-known/oauth-authorization-server.2
Self-registers via DCR, opens your browser to Dock consent.
3
Dock returns an access token, client uses it on every request.
Prerequisites
- Claude Desktop installed (Pro, Max, Team, or Enterprise plan).
- A Dock account. Dock is invite-only during beta. Request access at trydock.ai.
UI path
Claude Desktop · Settings · Connectors · Add custom connector
URL to paste
https://trydock.ai/api/mcpAuth
Claude opens a browser window to Dock's OAuth consent screen. Click Approve, the tab closes itself, Claude stores the token.
Prefer local stdio (older Claude Desktop builds, corporate sandbox)? Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows) and spawn the @trydock/mcp bridge with DOCK_API_KEY in env. Same 63 tools, Bearer auth instead of OAuth.
Verify
Using the Dock connector, list my workspaces.Troubleshooting
Symptom
Fix
"Connector failed to add"
Claude couldn't reach
trydock.ai/api/mcp. Check status.trydock.ai. If Dock is green, your network is likely blocking outbound HTTPS on that host.OAuth opens, but the tab hangs on consent
Third-party cookies are blocked. Sign in to
trydock.ai/login manually in the same browser, then retry the Connect flow.Want to revoke
Dock Settings · OAuth clients · Revoke the "Claude" entry. Claude's next call triggers re-authorization.
Frequently asked questions
- How do I connect Dock to Claude Desktop?
- Add Dock as a remote MCP server in Claude Desktop. Either let Claude Desktop's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Claude Desktop's MCP config under the `Authorization: Bearer dk_…` header.
- Does Claude Desktop 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 Claude Desktop, discovers them via the standard `tools/list` handshake. Learn more →
- How do I limit which Dock workspaces Claude Desktop can write to?
- When you mint the `dk_` key for Claude Desktop 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 Claude Desktop did in my Dock workspace?
- Open the workspace in your browser. Every row Claude Desktop 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 Claude Desktop 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 Claude Desktop's `dk_` key in Settings → API keys.
- Can multiple Claude Desktop sessions share state through Dock?
- Yes. Every Claude Desktop 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 Claude Desktop need OAuth or a dk_ API key for Dock?
- Either works. OAuth 2.1 + DCR is the recommended path: Claude Desktop 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 to my Claude Desktop config?
- Open `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows), add Dock under `mcpServers.dock` with `url: https://trydock.ai/api/mcp` and the Bearer header. Restart Claude Desktop. Learn more →
- Why don't I see Dock tools in Claude Desktop after adding the config?
- Restart Claude Desktop fully (quit, not just close the window). Claude Desktop reads `claude_desktop_config.json` on launch only. Confirm valid JSON (no trailing commas) via `cat | jq .` first; a parse error makes Claude silently skip the file.
- Does Claude Desktop support Dock's OAuth 2.1 flow?
- Yes, via the same `mcpServers` config (point `url` at Dock; Claude Desktop opens a browser for OAuth on first call). For older Claude Desktop versions without DCR, fall back to the `dk_` Bearer header path.