Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Connect
flowise logo

Flowise

Flowise bills itself as low-code LangChain. Its MCP Tool node wraps any remote MCP server so you can drag Dock onto your agent canvas.

Client
Flowise
Low-code LLM flow builder. MCP Tool node.
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

  • Flowise (cloud or self-hosted).
  • A Dock dk_ key.
Node
Tools · MCP · Remote Streamable HTTP
MCP node configjson
{
  "url": "https://trydock.ai/api/mcp",
  "headers": {
    "Authorization": "Bearer dk_c914f1c6..."
  }
}

Troubleshooting

Symptom
Fix
Node errors on save
Older Flowise versions only supported stdio MCP. Upgrade, or use the @trydock/mcp bridge as a stdio fallback.

Frequently asked questions

How do I connect Dock to Flowise?
Add Dock as a remote MCP server in Flowise. Either let Flowise's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Flowise's MCP config under the `Authorization: Bearer dk_…` header.
Does Flowise 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 Flowise, discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces Flowise can write to?
When you mint the `dk_` key for Flowise 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 Flowise did in my Dock workspace?
Open the workspace in your browser. Every row Flowise 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 Flowise 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 Flowise's `dk_` key in Settings → API keys.
Can multiple Flowise sessions share state through Dock?
Yes. Every Flowise 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 Flowise need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: Flowise 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 Flowise?
Flowise's MCP node accepts any compliant MCP server. Drop an MCP node into your chatflow, set URL to `https://trydock.ai/api/mcp` and the Bearer header. The 43 Dock tools auto-register.
Can a Flowise chatflow query my Dock workspace data?
Yes. Use the Dock MCP node's `list_rows` or `search` tools, pass the result through Flowise's LLM node for synthesis. Useful for chatbots that need to answer questions about your team's Dock workspace state.
How do I have Flowise write chat outputs back to Dock for review?
Add a Dock MCP node calling `append_doc_section` after your LLM node. Each chatflow run appends the response to a Dock doc; your team can review and comment in the Dock UI.

Related

Updated