Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Connect
github-copilot logo

GitHub Copilot

Copilot's agent mode (VS Code and JetBrains) can call MCP servers like Claude Code and Cursor. One settings-JSON entry wires Dock in.

Client
GitHub Copilot
VS Code agent mode. MCP via settings.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

  • GitHub Copilot Business or Enterprise seat with agent mode enabled. Personal-plan Copilot does not currently expose MCP.
  • VS Code (or JetBrains IDE) with the Copilot extension.
  • A Dock dk_ key.
Config file
VS Code settings.json · key is github.copilot.advanced.mcp.servers.
Reload
Reload the VS Code window (Cmd/Ctrl + Shift + P · "Developer: Reload Window") after saving.
VS Code settings.json (user)json
{
  "github.copilot.advanced.mcp.servers": {
    "dock": {
      "url": "https://trydock.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer dk_c914f1c6..."
      }
    }
  }
}

Verify

In Copilot Chat (agent mode)text
#dock list my workspaces

Troubleshooting

Symptom
Fix
"This feature is not available on your plan"
Confirm your org has Copilot Business or Enterprise, and that the admin has enabled the MCP policy. Personal Copilot plans do not include agent-mode MCP.
Copilot lists Dock but calls time out
Check that your network allows outbound HTTPS to trydock.ai. Corporate proxies sometimes terminate long-lived connections. Status: status.trydock.ai.

Frequently asked questions

How do I connect Dock to GitHub Copilot?
Add Dock as a remote MCP server in GitHub Copilot. Either let GitHub Copilot's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in GitHub Copilot's MCP config under the `Authorization: Bearer dk_…` header.
Does GitHub Copilot 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 GitHub Copilot, discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces GitHub Copilot can write to?
When you mint the `dk_` key for GitHub Copilot 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 GitHub Copilot did in my Dock workspace?
Open the workspace in your browser. Every row GitHub Copilot 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 GitHub Copilot 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 GitHub Copilot's `dk_` key in Settings → API keys.
Can multiple GitHub Copilot sessions share state through Dock?
Yes. Every GitHub Copilot 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 GitHub Copilot need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: GitHub Copilot 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 →
Does GitHub Copilot support Dock's MCP server?
Yes, via Copilot Chat's MCP support (VS Code Insiders + Copilot extension 1.150+). Add Dock under `mcpServers.dock` in your VS Code settings.json with `url: https://trydock.ai/api/mcp` and the Bearer header.
How do I let Copilot read my Dock launch-plan workspace while I code?
Mint a viewer-role `dk_` key for Copilot scoped to that workspace. Add Dock to your VS Code MCP config. Open Copilot Chat and ask `@dock list rows in launch-plan`; Copilot calls Dock's `list_rows` tool and shows the results inline.
Why do my Copilot @dock commands fail in regular VS Code?
MCP support in Copilot Chat is gated to VS Code Insiders + the Copilot Chat extension preview channel. Regular VS Code Stable hasn't shipped the MCP integration yet. Switch to Insiders to use Dock with Copilot.

Related

Updated