Model Context Protocol (MCP) servers expose operations that chat models can call. Open WebUI can connect to an MCP server and make its tools available in a conversation without rewriting them as native plugins.

Native MCP connections use Streamable HTTP. A server that only supports stdio needs a bridge such as mcpo before Open WebUI can use it; that bridge exposes an OpenAPI connection instead. OAuth-based servers also need their provider registration and authorization in place before tools can run.

The server URL must be reachable from the Open WebUI backend, not just from the browser. For Docker Desktop deployments, a host service is usually reached through host.docker.internal; services on a shared Docker Compose network can use their service names. An administrator account and a model with native tool-calling support are required.

Steps to connect an MCP server in Open WebUI:

  1. Confirm that your existing server exposes a Streamable HTTP MCP endpoint.
    MCP endpoint: https://mcp.example.com/mcp

    Calculator MCP below is an existing server running the official MCP SDK calculator tool, add(a, b). The sample hostname represents your server's actual endpoint, including its MCP path. Container-local localhost does not refer to a server on the Docker host.

    External tools can read data or perform operations with the server's permissions. The unauthenticated connection below is suitable only for a trusted private server with a harmless tool. A publicly accessible server needs authentication and restricted access.

  2. Open the user menu from your avatar.
  3. Select Settings.
  4. Enter Integrations in the settings search.
  5. Select Integrations under Admin.
  6. Click the Add Connection plus beside External Tool Servers.
  7. Switch Type from OpenAPI to MCP Streamable HTTP.

    The type label is a toggle. MCP support is marked experimental in Open WebUI 0.12.4; an ordinary OpenAPI endpoint does not become an MCP server by changing this setting.

  8. Enter Calculator MCP in Name.

    The connection ID is generated from the name. A different server can have a name that describes its own tools.

  9. Enter your server's complete MCP endpoint in URL.
  10. Select None under Auth for the private server that requires no credentials.

    None must match the server's authentication policy. Removing authentication from a protected server is not a connection fix. OAuth setup is a separate prerequisite; encrypted OAuth tokens also depend on a persistent WEBUI_SECRET_KEY.

  11. Click the circular-arrow Verify Connection control beside URL.

    Connection successful confirms the MCP handshake and tool discovery. It does not prove that the selected model can call a tool. A failed connection points to the endpoint, backend reachability, TLS trust, or authentication.

  12. Connect the MCP server using the dialog's Save button.

    The server appears under External Tool Servers with its toggle enabled.

  13. Return to the chat with Back.
  14. Open the model selector in the message composer.
  15. Select a model that supports native tool calling.

    company-chat:latest here is an Ollama model based on Qwen2.5 with tool support. A model that can chat but cannot emit tool calls will not complete the MCP operation.

  16. Reload the chat page to refresh the saved tool-server list.

    The active model remains visible in the composer. A chat page opened before the connection was saved can retain an older tool list.

  17. Open Integrations using the diamond-shaped icon beside the composer's plus.
  18. Open Tools in the Integrations menu.
  19. Enable Calculator MCP for the current chat.

    The tool counter appears beside the wrench. Registration makes the server available; this toggle selects it for the conversation.

  20. Enter a prompt that explicitly requests the server's tool.
    Call calculator-mcp_add with a=37 and b=58. Report the returned number.

    The tool name combines the connection ID with the advertised tool name. For a different server, a harmless query using one of its tools supplies the equivalent test.

  21. Send the prompt with the upward-arrow Send message button.
  22. Open View Result from calculator-mcp_add to inspect the tool's returned number.

    The expanded call shows inputs 37 and 58, output 95, and the model's reply reporting that value. A number in the reply alone does not establish that the MCP server was called. A connection error or a reply without a tool result leaves the integration unproven.

Share this guide