Connect
Devin
Devin supports MCP servers on its Machines and keeps auth state across sessions. Add Dock once and every Devin run on that Machine can read, write, and seal rows.
Client
Devin
Cognition's autonomous SWE. MCP support + Knowledge for REST.
HTTP JSON-RPC (streamable-http)
Dock MCP
trydock.ai/api/mcp
37 tools · OAuth 2.1 + DCR · Bearer
Auth path
1
Mint a
dk_ key in Dock Settings → API keys.2
Paste it as
Authorization: Bearer dk_… in the client config.3
Client calls Dock MCP directly on every request.
Prerequisites
- A Devin workspace with Machines enabled.
- A Dock
dk_key.
UI path
Devin Workspace · Settings · Machines · MCP servers · Add
URL
https://trydock.ai/api/mcpAuth header
Authorization · Bearer dk_...As a fallback, create a Devin Knowledge entry titled Dock API access with the base URL, auth header format, and a pointer to https://trydock.ai/openapi.json. Devin will use it to generate REST calls when MCP isn't available.
Verify
In a Devin sessiontext
Use the dock MCP server to list my workspaces, then append a task row describing the current session.Troubleshooting
Symptom
Fix
MCP status shows "unauthorized"
Devin stores MCP secrets per-Machine. Check that you added the Authorization header to the Machine you're actually using in the current session, not a different one.
Devin writes the key into planning docs
Prefix your prompts with: "The Dock token is stored as a Machine MCP secret. Never echo it back or write it to a file." Devin respects this consistently.
Frequently asked questions
- How do I connect Dock to Devin?
- Add Dock as a remote MCP server in Devin. Either let Devin's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Devin's MCP config under the `Authorization: Bearer dk_…` header.
- Does Devin 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 Devin, discovers them via the standard `tools/list` handshake. Learn more →
- How do I limit which Dock workspaces Devin can write to?
- When you mint the `dk_` key for Devin 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 Devin did in my Dock workspace?
- Open the workspace in your browser. Every row Devin 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 Devin 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 Devin's `dk_` key in Settings → API keys.
- Can multiple Devin sessions share state through Dock?
- Yes. Every Devin 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 Devin need OAuth or a dk_ API key for Dock?
- Either works. OAuth 2.1 + DCR is the recommended path: Devin 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 →
- Can Devin call Dock's MCP server?
- Yes, via Devin's MCP support. In Devin Settings → Tools → MCP Servers, add Dock with URL `https://trydock.ai/api/mcp` and Bearer auth. Devin's planning + execution loop can then call any of Dock's 43 tools.
- How do I have Devin write its task plans to a Dock workspace?
- Tell Devin in your initial prompt to mirror its task plan to a Dock doc surface via `update_doc` or `append_doc_section`. Your team can then track Devin's progress + leave comments inline as it executes.
- Can Devin and a human teammate collaborate on the same Dock workspace?
- Yes. Devin is just a signed agent in Dock; its writes show up alongside human edits in real time via SSE. Comments addressed to Devin (via @mention or webhook trigger) can route into Devin's task queue.