Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Connect
continue logo

Continue

Continue works across VS Code and JetBrains IDEs. One config file drives both. Add Dock once and your agent sees it everywhere.

Client
Continue
Open-source IDE agent. Config at ~/.continue/config.json.
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

  • Continue extension installed in your IDE.
  • A Dock dk_ key.
Config file
~/.continue/config.json
Reload
Continue watches the config file and reloads in-place. The MCP status dot in the Continue panel flips to green within a second.
~/.continue/config.json (merge experimental.mcpServers)json
{
  "experimental": {
    "mcpServers": {
      "dock": {
        "url": "https://trydock.ai/api/mcp",
        "transport": "http",
        "headers": {
          "Authorization": "Bearer dk_c914f1c6..."
        }
      }
    }
  }
}

Verify

In the Continue chattext
@dock list my workspaces

Troubleshooting

Symptom
Fix
Dock doesn't appear in the MCP dropdown
MCP is still behind the experimental flag in Continue. Make sure the entry nests under experimental.mcpServers, not at the root.
Every call errors with "unsupported transport"
Older Continue builds only support stdio transport. Upgrade to the latest release, or use the @trydock/mcp bridge as a stdio fallback (same JSON shape as other stdio MCPs).

Frequently asked questions

How do I connect Dock to Continue?
Add Dock as a remote MCP server in Continue. Either let Continue's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Continue's MCP config under the `Authorization: Bearer dk_…` header.
Does Continue 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 Continue, discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces Continue can write to?
When you mint the `dk_` key for Continue 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 Continue did in my Dock workspace?
Open the workspace in your browser. Every row Continue 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 Continue 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 Continue's `dk_` key in Settings → API keys.
Can multiple Continue sessions share state through Dock?
Yes. Every Continue 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 Continue need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: Continue 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 add Dock as an MCP server in Continue?
Continue 0.9.250+ supports MCP. Edit `~/.continue/config.json`, add Dock under `mcpServers.dock` with URL + Bearer. Continue auto-reloads on config save; the Dock tools surface in chat immediately.
Can Continue's slash commands call Dock tools?
Yes. Define a custom slash command in Continue's config that wraps a Dock MCP tool call. e.g. `/dock-row` could trigger `create_row` with templated args, scoped to a specific Dock workspace.
How do I have Continue write code-review notes to a Dock workspace?
After a Continue review session, ask it to call Dock's `create_row` with the file, function, and review notes as columns. Your team gets a Dock-backed log of every code review Continue performed.

Related

Updated