Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Connect
n8n logo

n8n

n8n's AI Agent nodes accept MCP servers as tools. Add Dock once and every AI Agent workflow can call create_row, update_row, list_rows, etc. For non-AI workflows, use the HTTP Request node against Dock's REST API.

Client
n8n
Workflow automation. MCP Tool node + HTTP Request for REST.
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

  • n8n (cloud or self-hosted).
  • A Dock dk_ key.
Node
Add a MCP Client Tool node to your AI Agent.
MCP Client Tool parametersjson
{
  "connectionType": "HTTP Streamable",
  "url": "https://trydock.ai/api/mcp",
  "authentication": {
    "type": "header",
    "headerName": "Authorization",
    "headerValue": "Bearer dk_c914f1c6..."
  }
}

Troubleshooting

Symptom
Fix
AI Agent can't discover tools
Make sure the MCP Client Tool node is connected to the AI Agent's ai_tool input, not the main flow.

Frequently asked questions

How do I connect Dock to n8n?
Add Dock as a remote MCP server in n8n. Either let n8n's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in n8n's MCP config under the `Authorization: Bearer dk_…` header.
Does n8n 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 n8n, discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces n8n can write to?
When you mint the `dk_` key for n8n 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 n8n did in my Dock workspace?
Open the workspace in your browser. Every row n8n 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 n8n 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 n8n's `dk_` key in Settings → API keys.
Can multiple n8n sessions share state through Dock?
Yes. Every n8n 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 n8n need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: n8n 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 n8n?
n8n 1.65+ supports MCP via the MCP Client node. Add a credential pointing at `https://trydock.ai/api/mcp` with your `dk_` Bearer; use the MCP Client node in your workflow to call any Dock tool.
Can n8n trigger a Dock workflow when a row changes?
Yes. Set up a Dock webhook pointing at an n8n Webhook node, filter on `row.created` or `row.updated` events. n8n then routes the payload through your workflow (Slack, email, downstream API, etc).
How do I have n8n write Slack-DM responses to a Dock workspace?
Use n8n's Slack trigger → MCP Client (`create_row`) → Dock. Each DM appends a row to a Dock workspace with the message text + author + timestamp; your team sees the inbox without leaving Dock.

Related

Updated