Connect
claude-web logo

Claude.ai (web + Projects)

Claude.ai on the web supports custom remote MCP connectors in both Chat and Projects. Add Dock once at the account level and every conversation (including every Project) can call the 13 Dock tools.

Client
Claude.ai (web + Projects)
Browser-based Claude. Custom connector via Settings.
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.ai account (any paid tier that has custom connectors).
  • A Dock account.
UI path
Claude.ai · Settings · Connectors · Add custom connector
URL
https://trydock.ai/api/mcp
Scope
Account-level. Every Project and every Chat for this account can use the connector. Per-project disable is available on each Project's settings.

Verify

In Chat or Projecttext
Use the Dock connector to list my workspaces, then append a new row to content-pipeline with title "Hello from Claude.ai" and status "drafted".

Troubleshooting

Symptom
Fix
Connector added but tools don't show up in a Chat
Claude enables connectors per conversation. In a Chat, click the Tools picker and toggle Dock on. In Projects, toggle Dock from the Project's sidebar.
401 on tool calls after a few weeks
Dock access tokens expire after 30 days. Claude triggers a refresh automatically; if it fails (e.g. you revoked the token), re-authorize by clicking the connector entry in Settings.

Frequently asked questions

How do I connect Dock to Claude.ai (Web)?
Add Dock as a remote MCP server in Claude.ai (Web). Either let Claude.ai (Web)'s OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Claude.ai (Web)'s MCP config under the `Authorization: Bearer dk_…` header.
Does Claude.ai (Web) 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.ai (Web), discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces Claude.ai (Web) can write to?
When you mint the `dk_` key for Claude.ai (Web) 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.ai (Web) did in my Dock workspace?
Open the workspace in your browser. Every row Claude.ai (Web) 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.ai (Web) 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.ai (Web)'s `dk_` key in Settings → API keys.
Can multiple Claude.ai (Web) sessions share state through Dock?
Yes. Every Claude.ai (Web) 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.ai (Web) need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: Claude.ai (Web) 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 →
Does Claude.ai web support Dock as an MCP server?
Yes, on Pro and Team tiers, via Settings → Custom Connectors. Add Dock with URL `https://trydock.ai/api/mcp` and Claude.ai handles the OAuth 2.1 + DCR flow automatically. Learn more →
Can free Claude.ai users connect to Dock?
Custom MCP connectors are gated to Pro and Team tiers on Claude.ai. Free users can use Claude Desktop (free) or Claude Code (free with API auth) instead, both of which support Dock.
How do I share a Claude.ai conversation about my Dock data with a teammate?
Two paths. Use Claude.ai's native share-conversation feature (the Claude link). Or, ask Claude to append the conversation summary to a Dock doc surface; the doc URL is then shareable to anyone with workspace access (and your team can comment in-line on the summary).

Related

Updated