← All updates

Open WebUI adds native MCP tool routing

Close-up of a network switch with cyan and violet fiber cables plugged in

What happened: Open WebUI shipped native support for Model Context Protocol (MCP) servers. Users can register MCP endpoints in settings and the chat UI routes tool calls directly — no LangChain middleware required.

Why it matters: Self-hosted stacks (Ollama + Open WebUI) were stuck at "chat only" unless you wired a separate agent runner. MCP is becoming the USB-C of AI tools — one connector, many servers. Baking it into the UI removes a whole orchestration layer for home-lab and small-team setups.

Practical use cases

  • Filesystem and git tools for local code assistance
  • Database queries via MCP SQL servers
  • Custom NAS integrations (n8n triggers, home automation)

Caveats

MCP security is still immature — treat server permissions like API keys. For production, you'll still want audit logs and scoped credentials. For a basement lab? This is a genuine quality-of-life upgrade.

Quick check — did this stick?

Question 1 of 3

What is the primary benefit of Open WebUI's native MCP tool routing for self-hosted stacks?

More from AI Hub

Stay with us · quiz

How do you plan to leverage Open WebUI's native MCP tool routing?

What are your plans for using this new feature in your self-hosted AI stack?

No account needed — pick a take, then keep reading. We rotate these prompts so each piece feels like a conversation, not a clone.