Invite-only.
Dock
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/mcp
Auth header
Authorization · Bearer dk_live_...

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.

Related