Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
These docs are outdated. This section is no longer maintained. Current guides live in the Help Center.
Agents

Connect agents

Every way to wire an AI thing to Dock. 54 supported clients today across six categories. Pick the one that matches your stack.

How to pick

  • Already use a tool with a config block (Claude Code, Cursor, Windsurf, Zed, Cline, Claude Desktop): Native clients → one-click via OAuth + DCR.
  • Building a custom agent in code (LangChain, CrewAI, Pydantic AI, etc.): Frameworks & SDKs.
  • Wiring a local-model UI: Local model UIs.
  • Code-gen agent with auth (Devin, Replit, Bolt): Builders.
  • No-code/workflow tool: No-code.
  • Just curl: From scratch.

All connectors

Native clients

One-click setup. Most use OAuth + DCR, sign in via browser, never paste an API key.

Frameworks & SDKs

For agents you write yourself. Drop-in MCP/REST clients for every popular agent framework.

Local model UIs

Wire local-model chat UIs (LibreChat, Open WebUI, etc.) to your Dock workspaces over MCP.

Builders

Code-gen agents (Bolt, v0, Lovable, Replit, Devin) reading Dock for context + writing back.

No-code / Workflow

Visual flow tools (Zapier, n8n, Dify, Langflow, Flowise) with first-class Dock connectors.

From scratch

Just curl + a Bearer token. Or Python / Node SDK calls. The bare metal.

First, understand agent identity

Before you wire any client, read Agent overview: Dock treats agents as first-class principals with their own identities, keys, and audit trails. The connection flow you pick reflects which kind of identity the connecting agent claims.

Frequently asked questions

How do I connect an AI agent to Dock?
Pick your agent's setup guide from the catalog above (54 covered, grouped by category). Each guide walks through MCP setup with either OAuth 2.1 + DCR or a `dk_` Bearer key in under two minutes. Learn more →
Which AI clients work with Dock's MCP server?
Anything that speaks the MCP protocol. Native: Claude Code, Claude Desktop, Claude.ai web, ChatGPT, Cursor, Windsurf, Zed, Continue, Cline, Aider, Codex, GitHub Copilot, JetBrains AI, and more. Frameworks: OpenAI Agents SDK, LangGraph, LangChain, CrewAI, AutoGen, LlamaIndex, Vercel AI SDK, Pydantic AI, Mastra, Agno, Semantic Kernel. Learn more →
Does Dock work with Claude Code?
Yes. Run `claude mcp add dock --transport http https://trydock.ai/api/mcp`. Claude Code's built-in OAuth 2.1 + DCR handles auth, no key ceremony. Bearer-token auth is also supported via `--header`. Learn more →
Does Dock work with Cursor?
Yes. Open Cursor Settings → MCP → Add new MCP Server, set URL to `https://trydock.ai/api/mcp`, paste your `dk_` Bearer token. The 43 Dock tools surface in Cursor's chat panel after restart. Learn more →
Does Dock work with ChatGPT?
Yes, on Plus / Team / Enterprise tiers via Settings → Connectors → Add MCP Server. ChatGPT auto-registers via Dock's `/api/oauth/register` and opens a browser for OAuth consent. Learn more →
Can I connect my custom Python agent to Dock?
Yes. Use the MCP Python SDK to connect to `https://trydock.ai/api/mcp` with Bearer auth, or hit Dock's REST API directly with `httpx`. Both surface the same workspace state; pick MCP for tool-calling semantics, REST for direct CRUD. Learn more →
How do I find the right Dock setup guide for my agent?
The catalog above is grouped by category: Native (built-in MCP support), Frameworks (Python / TS SDK wrappers), Local UIs (Ollama, Open WebUI, AnythingLLM, LibreChat), Builders (v0, Bolt, Lovable, Replit, Devin), No-code (n8n, Zapier, Dify, Flowise, Langflow), From-scratch (raw Python, Node, curl).
What's the difference between Dock's MCP server and Dock's REST API for agents?
MCP is JSON-RPC over HTTP/SSE with the `tools/list` + `tools/call` handshake; ideal when your agent's runtime auto-discovers tools (Claude Code, Cursor, ChatGPT, etc.). REST is plain HTTPS endpoints; ideal for CI, cron, scripts, or any environment where MCP overhead isn't worth it. Both yield the same workspace state. Learn more →
Do all 54 Dock connectors support OAuth 2.1?
OAuth 2.1 + DCR support depends on the client, not Dock; Dock supports OAuth on every client that implements it (Claude Code, Claude Desktop, Claude.ai web, ChatGPT, etc.). Clients without OAuth 2.1 use the `dk_` Bearer token path; same Dock side, different auth ceremony. Learn more →
Can my agent talk to multiple Dock workspaces at once?
Yes. A single `dk_` key scoped to multiple workspaces grants access to all of them; the agent picks via `slug` on each tool call. Or, mint per-workspace keys for clean attribution and tighter permission boundaries (recommended for multi-tenant agent setups). Learn more →
Updated