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.
Related
- MCP-side overview — protocol-level setup pattern.
- API auth — for agents using REST instead of MCP.