Invite-only.
Dock
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/mcp
Auth
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 37 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.

Related