Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Connect
cursor logo

Cursor

Add Dock to Cursor and your AI pair-programmer can read, write, and co-edit any Dock workspace from inside the editor. Two minutes end-to-end.

Client
Cursor
Editor-native. Supports remote MCP over HTTP with Bearer auth.
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 recent Cursor build (MCP remote support landed in 2025).
  • A Dock dk_ key. Mint one in Settings · API keys, or with npx -y @trydock/cli key new.
Config file (user)
~/.cursor/mcp.json
Config file (project)
.cursor/mcp.json in the repo root. Project config overrides user config for that workspace only.
Reload
Cursor reloads MCP servers on save. Open the MCP panel (Cmd/Ctrl + Shift + P · "MCP: List Servers") to confirm Dock went green.
~/.cursor/mcp.jsonjson
{
  "mcpServers": {
    "dock": {
      "url": "https://trydock.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer dk_c914f1c6..."
      }
    }
  }
}

Verify

Ask Cursor's agenttext
@dock list my workspaces

Troubleshooting

Symptom
Fix
Dock shows red in the MCP panel
Usually a 401. Open Settings · API keys on trydock.ai, confirm the key is still listed, re-copy, re-paste. Make sure the value is exactly Bearer dk_... (space between Bearer and token).
Agent "doesn't see" the Dock tools
Cursor scopes tools per composer. Type @dock once in the composer to attach the MCP. After that, the 63 tools show up in the tool picker for every follow-up turn.
Config changes don't take effect
Fully quit and relaunch Cursor (not just close the window). Some MCP registry state is process-scoped.

Frequently asked questions

How do I connect Dock to Cursor?
Add Dock as a remote MCP server in Cursor. Either let Cursor's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Cursor's MCP config under the `Authorization: Bearer dk_…` header.
Does Cursor 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 Cursor, discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces Cursor can write to?
When you mint the `dk_` key for Cursor 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 Cursor did in my Dock workspace?
Open the workspace in your browser. Every row Cursor 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 Cursor 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 Cursor's `dk_` key in Settings → API keys.
Can multiple Cursor sessions share state through Dock?
Yes. Every Cursor 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 Cursor need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: Cursor 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 →
How do I install the Dock MCP in Cursor?
Open Cursor Settings → MCP, click Add new MCP Server. Set Command type to URL/HTTP, enter `https://trydock.ai/api/mcp`, paste your `dk_` key as the Bearer token (or use OAuth). Restart Cursor and the 43 Dock tools appear in the chat panel. Learn more →
Why can Cursor see Dock's MCP but get 401 on every call?
Auth header isn't being sent. Re-open Settings → MCP, confirm the Bearer token is set under Headers (not Args). The format is `Authorization: Bearer dk_...` (with the space). Save and restart Cursor.
How is Dock different from Cursor's built-in @web for project context?
Cursor's @web is read-only general-purpose web search. Dock is your team's shared workspace (rows + docs) that Cursor can both read AND write to with attribution. Useful when Cursor is generating code that should drop a record in your launch tracker, or appending to a design-decisions doc your team also edits.

Related

Updated