Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
MCP · Setup

Connecting clients

For MCP-aware clients, "connecting" is one config block. The client handles OAuth + DCR automatically. Per-client setup pages live under Agents; this page is the protocol-side overview.

The config block (every client)

Most MCP clients accept a JSON config snippet describing each MCP server. For Dock:

{
  "mcpServers": {
    "dock": {
      "url": "https://trydock.ai/api/mcp"
    }
  }
}

That's it. On first use, the client triggers the OAuth flow in your browser, you sign in, you're connected. No API key paste, no client_id registration.

Per-client setup pages

Exact config-file paths + verification commands for each supported client live in the Agents book:

Browse the Agents book for the full list (54 entries).

Verifying the connection

Once configured, ask the client to list available tools. You should see Dock's 43 tools (list_workspaces, create_row, etc.) in the result.

From the CLI:

# Lists every tool the MCP server exposes
dock mcp tools list

Troubleshooting

  • OAuth flow doesn't open browser: some terminal-only clients can't open URLs. Either paste the URL manually or set DOCK_API_KEY for headless auth (see the per-client page).
  • Tools list is empty: token expired, re-authorize via the client's reconnect flow.
  • 403 on tool call: the scope wasn't granted during OAuth. Disconnect and reconnect, granting the missing scope.
  • Confirm-token errors on upgrade/downgrade: expected. See dangerous-ops handshake.