Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Connect
supermaven logo

Supermaven

Supermaven is best known for fast inline completion, but its Chat mode (Enterprise) supports MCP servers. Wire Dock into the chat config to pull workspace context on demand.

Client
Supermaven
Fast inline completion. Chat-mode MCP on enterprise tier.
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

  • Supermaven Enterprise (Chat + MCP).
  • A Dock dk_ key.
Config file
~/.supermaven/chat.json
chat.jsonjson
{
  "mcpServers": {
    "dock": {
      "url": "https://trydock.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer dk_c914f1c6..."
      }
    }
  }
}

Troubleshooting

Symptom
Fix
Inline completions ignore Dock context
MCP only augments Chat, not inline completion. Invoke Chat to use Dock tools.

Frequently asked questions

How do I connect Dock to Supermaven?
Add Dock as a remote MCP server in Supermaven. Either let Supermaven's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Supermaven's MCP config under the `Authorization: Bearer dk_…` header.
Does Supermaven 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 Supermaven, discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces Supermaven can write to?
When you mint the `dk_` key for Supermaven 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 Supermaven did in my Dock workspace?
Open the workspace in your browser. Every row Supermaven 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 Supermaven 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 Supermaven's `dk_` key in Settings → API keys.
Can multiple Supermaven sessions share state through Dock?
Yes. Every Supermaven 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 Supermaven need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: Supermaven 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 →
Can Supermaven use Dock as a context source?
Supermaven's chat-mode (Pro tier) supports MCP servers. Add Dock under Supermaven Settings → MCP Servers with URL + Bearer. Chat mode can then call Dock tools as part of its completion context.
Does Supermaven's free tier support Dock?
MCP support is gated to Supermaven Pro / Enterprise. Free-tier inline completions don't have tool-calling. Use Cursor or Continue (both free) for MCP-powered Dock integration.
How does Dock fit Supermaven's context-window-as-codebase model?
Supermaven indexes your codebase for completions; Dock holds your team's shared task + design state. Pair them: Supermaven for code completions, Dock for tracking what Supermaven and your team are building.

Related

Updated