Get startedCLIAPIMCPWebDesktopAgentsSupportBillingChangelog
Connect
open-webui logo

Open WebUI

Open WebUI is a popular self-hosted chat UI. Its MCP adapter accepts remote servers via the Admin · Tools panel. Add Dock once and expose it to any model you've wired up.

Client
Open WebUI
Self-hosted ChatGPT-style UI. MCP via Tools panel.
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

  • Open WebUI deployed (Docker or pip).
  • A Dock dk_ key.
UI path
Admin · Settings · Tools · MCP · Add server
MCP server entryjson
{
  "name": "dock",
  "url": "https://trydock.ai/api/mcp",
  "headers": {
    "Authorization": "Bearer dk_c914f1c6..."
  }
}

Troubleshooting

Symptom
Fix
"MCP not enabled" banner
Set ENABLE_MCP=true in the Open WebUI container environment. Restart.

Frequently asked questions

How do I connect Dock to Open WebUI?
Add Dock as a remote MCP server in Open WebUI. Either let Open WebUI's OAuth 2.1 + DCR flow handle auth (recommended; no credential ceremony), or paste a scoped Dock `dk_` API key in Open WebUI's MCP config under the `Authorization: Bearer dk_…` header.
Does Open WebUI 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 Open WebUI, discovers them via the standard `tools/list` handshake. Learn more →
How do I limit which Dock workspaces Open WebUI can write to?
When you mint the `dk_` key for Open WebUI 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 Open WebUI did in my Dock workspace?
Open the workspace in your browser. Every row Open WebUI 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 Open WebUI 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 Open WebUI's `dk_` key in Settings → API keys.
Can multiple Open WebUI sessions share state through Dock?
Yes. Every Open WebUI 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 Open WebUI need OAuth or a dk_ API key for Dock?
Either works. OAuth 2.1 + DCR is the recommended path: Open WebUI 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 a tool server in Open WebUI?
Open WebUI supports OpenAPI-compatible tool servers. Use Dock's `/openapi.json`: in Open WebUI Admin → Tools → Add Server, paste the OpenAPI URL and your `dk_` Bearer. Or wrap Dock's MCP server with `mcpo` for direct MCP-style integration.
Can Open WebUI's pipelines write to a Dock workspace?
Yes. Use Open WebUI's pipeline functions to call Dock's REST API at any pipeline stage. Pre-prompt: enrich with Dock context (`list_rows`). Post-response: append to a Dock doc (`append_doc_section`) for audit.
Does Open WebUI's MCP support work with Dock's OAuth 2.1?
Open WebUI's MCP integration currently uses Bearer-token auth via OpenAPI tool servers. For full OAuth 2.1 + DCR, use a downstream client (Claude Desktop, Cursor) that supports the protocol; Open WebUI is great for the simpler Bearer path.

Related

Updated