Set up Open WebUI
Self-hosted AI chat platform (125K+ GitHub stars). Connect Agentcy so your Open WebUI instance can query marketing data alongside any LLM provider.
- 01
Make sure your Open WebUI instance is on v0.6.31 or later (current is v0.8.12). Pull ghcr.io/open-webui/open-webui:latest and restart if on Docker.
- 02
Sign up at app.goagentcy.com and create an API key
- 03
Sign in to Open WebUI as an admin
- 04
Open Admin Panel → Settings → Integrations
- 05
Click + (Add Connection)
- 06
Type: MCP Streamable HTTP
- 07
Server URL: https://data.goagentcy.com/mcp
- 08
Auth: Bearer
- 09
Key: paste your agcy_... API key
- 10
Click Save — Open WebUI auto-discovers Agentcy’s tools
path: Admin Panel → Settings → Integrations
# Open WebUI uses an in-app form, not a JSON file.
# Open the UI, then fill in these fields exactly:
Type: MCP Streamable HTTP
Server URL: https://data.goagentcy.com/mcp
Auth: Bearer
Key: YOUR_AGENTCY_API_KEY
# DO NOT paste JSON into this form. Per Open WebUI's
# official docs, pasting MCP-style JSON crashes the UI.Open WebUI is UI-only — there is NO file-based or JSON paste-in config for MCP servers. Pasting MCP-style JSON into the form will crash the UI per Open WebUI’s own docs. Field labels and menu paths verified directly from Open WebUI source code (Integrations.svelte + i18n files). The Auth dropdown actually has 5 options: None, Bearer, OAuth 2.1, OAuth 2.1 (Static), Session — select Bearer for Agentcy. Direct remote HTTP MCP support is native since v0.6.31; no MCPO bridge needed (MCPO is only required for stdio or SSE servers). Operational note: set the WEBUI_SECRET_KEY environment variable in your Docker/Compose config to prevent token decryption errors on container restart. Selecting Bearer auth without entering a key sends an empty Authorization header that will be rejected.
Stuck or want to verify these instructions yourself? These are the documentation sources we used. If something here doesn't match what you see in your client, the vendor may have updated their UI — and we'll get this page updated.
- Open WebUI Docs — Model Context Protocol (MCP) (official, primary)
- GitHub source — Integrations.svelte (verified field labels + button text)
- Open WebUI — GitHub CHANGELOG.md (v0.8.11/v0.8.12 release notes)
- MCPO — stdio/SSE proxy bridge (only needed for non-HTTP transports)
- Open WebUI + native MCP integration walkthrough with screenshots (third-party, March 2026)
After connecting Open WebUI and configuring your data sources in the portal, ask questions about any of them in natural language: