Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Connect
warp logo

Warp

Warp's Agent Mode accepts remote MCP servers. Add Dock once and the Warp terminal can read and write your Dock workspaces alongside shell operations.

Client
Warp
AI-first terminal. MCP via Agent Mode settings.
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

  • Warp installed (macOS, Linux, Windows) with Agent Mode enabled.
  • A Dock dk_ key.
UI path
Warp · Settings · AI · MCP Servers · Add custom server
MCP server form values (as JSON)json
{
  "name": "dock",
  "url": "https://trydock.ai/api/mcp",
  "headers": {
    "Authorization": "Bearer dk_c914f1c6..."
  }
}

Verify

In Warp Agent Modetext
Using dock, list my workspaces.

Troubleshooting

Symptom
Fix
Warp Agent can't see Dock tools
Agent Mode must be toggled on per session. Click the AI icon in the Warp input bar and pick "Agent Mode".

Frequently asked questions

How do I connect Dock to Warp?
Add Dock as a remote MCP server in Warp. Either let Warp's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Warp's MCP config under the `Authorization: Bearer dk_…` header.
Does Warp 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 Warp, discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces Warp can write to?
When you mint the `dk_` key for Warp 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 Warp did in my Dock workspace?
Open the workspace in your browser. Every row Warp 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 Warp 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 Warp's `dk_` key in Settings → API keys.
Can multiple Warp sessions share state through Dock?
Yes. Every Warp 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 Warp need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: Warp 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 Warp's Agent Mode?
Open Warp Settings → Agent Mode → MCP Servers, click Add. Set the URL to `https://trydock.ai/api/mcp`, pick HTTP transport, paste your `dk_` Bearer token. Save and start a new Agent Mode session.
Why does Warp's Agent Mode not see Dock tools after I added the server?
Existing Agent Mode sessions don't auto-reload MCP servers. Open a new Agent Mode prompt (⌘-' twice) and the Dock tools surface. Confirm the server shows green-dot in Settings → Agent Mode → MCP Servers.
Can I use Dock with Warp's Workflows feature?
Yes, but at the REST API layer (Warp Workflows are shell-command templates, not MCP). Use `curl` with your `dk_` Bearer to append a row or update a doc section from any saved workflow.

Related

Updated