Invite-only.
Dock
Connect

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_live_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).

Related