# Open WebUI MCP Server: Web Search in 5 Steps

> Add a web-search MCP server to Open WebUI: MCP (Streamable HTTP), Bearer key, a tool list that fits your Ollama context. 28 tools measured 13,947 tokens.

[Home](https://quanticdata.io/)/[Blog](https://quanticdata.io/blog/)/Open WebUI MCP Server: Web Search in 5 Steps

# Open WebUI MCP Server: Web Search in 5 Steps

MCP & agentsOct 2, 2026·5 min read·By [Aldo Morese](https://quanticdata.io/about/), founder of QuanticData

Open WebUI MCP server setup: External Tool Servers, type MCP (Streamable HTTP), QuanticData URL with the web tools, Bearer key

On this page [Before you start](/blog/open-webui-mcp-server/#before-you-start) [The 5 steps](/blog/open-webui-mcp-server/#the-5-steps) [Pick the tool set for your model's context](/blog/open-webui-mcp-server/#pick-the-tool-set-for-your-model-s-context) [Troubleshooting "Failed to connect to MCP server"](/blog/open-webui-mcp-server/#troubleshooting-failed-to-connect-to-mcp-server)

To add a web-search MCP server to Open WebUI, an admin opens Settings, Admin, Integrations, adds an External Tool Server of type MCP (Streamable HTTP) with the server URL and a Bearer key, and saves. Size the tool list to the model: our 28 tools measured 13,947 tokens on 2 October 2026, the three web tools 4,215.

Open WebUI is the chat interface many people put in front of Ollama, and since v0.6.31 it supports MCP natively, without the mcpo proxy older guides still describe. That makes it the easiest way to give a whole team's local models web access: one admin adds the server, access control decides who gets it, and every chat can switch the tools on. This guide does that with a hosted web-data server and explains the settings that make it work on small models.

## Before you start

| Requirement | Why |
| --- | --- |
| Open WebUI v0.6.31 or newer | Native MCP arrived in that release; Open WebUI's own MCP support is Streamable HTTP only |
| An admin account | MCP servers can only be added by administrators, by design |
| A model with reliable tool calling | Open WebUI's docs: MCP connects the tools, it does not improve the model's ability to use them |
| A QuanticData API key | Sent as the Bearer token; created in the dashboard |

Why admin-only? Open WebUI's documentation explains that an MCP server runs inside its trust boundary with the connecting user's scope, unlike an OpenAPI tool server, so registering one is reserved for admins. Users still get the tools; they just cannot add servers.

## The 5 steps

1. Open **Settings**, then **Admin**, then **Integrations**.

2. Under **External Tool Servers**, click **Add Connection**. The Integrations page has several sections; it has to be this one.

3. Set **Type** to **MCP (Streamable HTTP)**, not OpenAPI. Pasting an MCP config into an OpenAPI connection is the documented cause of the infinite loading screen.

4. Enter the **Server URL** `https://api.quanticdata.io/mcp?tools=web`, set **Auth** to **Bearer** and paste your API key in the **Key** field.

5. **Save**, restarting Open WebUI if it asks.

Then, in a chat, click **+**, open **Integrations**, then **Tools**, and enable the QuanticData tools. To limit who sees them, scope the connection with Access Control to the right users or groups.

Open WebUI also offers an **OAuth 2.1** auth mode using dynamic client registration, which our endpoint supports (see [how our MCP OAuth works](https://quanticdata.io/blog/mcp-server-oauth/)). With OAuth each user connects their own account; Open WebUI warns that OAuth 2.1 tools cannot be set as default tools on a model, and that `WEBUI_SECRET_KEY` must be set or OAuth tokens break on every container restart. For a single shared key, Bearer is simpler.

## Pick the tool set for your model's context

Open WebUI usually sits in front of Ollama, and Ollama gives a model 4k tokens of context on GPUs under 24 GiB of VRAM, 32k between 24 and 48 GiB, and recommends at least 64,000 for web search and agents. Every enabled tool's definition travels with every request. Measured from what our server returns, tokens as characters divided by four:

| Server URL suffix | Tools | Definition tokens | Use with |
| --- | --- | --- | --- |
| (none) | all 28 | 13,947 | models at 32K context or more |
| ?tools=research | search, search_and_read, scrape, map, batch, batch_status | 5,122 | 16K and up |
| ?tools=web | search, search_and_read, scrape | 4,215 | 8K and up |
| ?tools=lite | search_and_read | 356 | 4K models |
| ?tools=collectors | list_collectors, run_collector, collector_run_status | 829 | add to any set for ready-made datasets |

Nothing stops you adding the server twice under two names, for example a lite connection for the small default model and a full one for a 64K model, and scoping each with Access Control. Results matter as much: a default `search_and_read` returned 3,986 tokens, and with `top_n` 2 and `max_tokens` 1,500 it returned 1,858. Put those limits in the model's system prompt in Open WebUI so the model sends them. The full budget for 4K to 64K is in [local LLM web search with MCP](https://quanticdata.io/blog/local-llm-web-search-mcp/).

## Troubleshooting "Failed to connect to MCP server"

- **Bearer without a key.** Open WebUI sends an empty `Authorization: Bearer` header if the Key field is blank, and servers reject it. Paste the key, or our endpoint answers 401.

- **Empty Function Name Filter List.** Open WebUI's docs list a known bug: if the filter list is empty, try adding a single comma.

- **Handshake timeout.** The MCP initialize call has a 10-second default timeout (`MCP_INITIALIZE_TIMEOUT`). A server with many tools can take longer on a cold start; raise it or use a smaller tool set.

- **Wrong type.** Infinite loading after saving means the connection was created as OpenAPI. Disable it and add it again as MCP.

- **The model never calls the tools.** Check the tools are enabled in the chat, then the model: switch to one trained for tool calling, and to a smaller tool set if the context is small.

The other local stacks use the same endpoint: [giving Ollama internet access](https://quanticdata.io/blog/give-ollama-internet-access/) for a terminal, [LM Studio MCP web search](https://quanticdata.io/blog/lm-studio-mcp-web-search/) for the desktop app. Every argument of every tool is in the [API documentation](https://quanticdata.io/docs/), and the [QuanticData MCP server](https://quanticdata.io/mcp-server/) page lists all clients. Billing is per successful call: every account gets $2 of free API usage each month, and failed requests are never billed.

### Sources & further reading

- [Model Context Protocol (MCP), Open WebUI documentation (fetched 2 October 2026)](https://docs.openwebui.com/features/extensibility/mcp/)

- [How do I add MCP servers in Open WebUI 0.6.31?, r/OpenWebUI](https://www.reddit.com/r/OpenWebUI/comments/1ns8mdq/how_do_i_add_mcp_servers_in_open_webui_0631/)

- [Context length, Ollama documentation](https://docs.ollama.com/context-length)

- [mcpo, MCP-to-OpenAPI proxy (open-webui on GitHub)](https://github.com/open-webui/mcpo)

## FAQ

Quick answers on open webui mcp server.

[Something else? Ask us](mailto:hello@quanticdata.io)

### Does Open WebUI support MCP servers?

Yes, natively since v0.6.31, over Streamable HTTP. An admin adds the server under Settings, Admin, Integrations, External Tool Servers, with Type set to MCP (Streamable HTTP).

### Do I still need mcpo for Open WebUI?

Not for Streamable HTTP servers on v0.6.31 or newer. mcpo, the MCP-to-OpenAPI proxy, was the route before native support and is still useful for stdio-only servers.

### Why can only admins add MCP servers in Open WebUI?

Open WebUI's docs explain that an MCP server runs inside its trust boundary with the connecting user's scope, so registering one is admin-gated. Admins can then grant the tools to users or groups with Access Control.

### How do I fix "Failed to connect to MCP server" in Open WebUI?

Check that Bearer auth has a key, add a comma to an empty Function Name Filter List, raise MCP_INITIALIZE_TIMEOUT if the handshake is slow, and make sure the connection type is MCP, not OpenAPI.

### How many tokens does a web MCP server add in Open WebUI?

Ours sends 13,947 tokens of definitions with all 28 tools, 4,215 with the web set and 356 with the lite set, measured 2 October 2026. Choose the set with ?tools= in the server URL.

## Web search for every model in Open WebUI

One admin connection, MCP over Streamable HTTP, a tool set sized to your models. Every account gets $2 of free API usage each month, and failed requests are never billed.

[Start free — $2/month included](https://quanticdata.io/signup/)[Explore Web Scraping MCP Server for AI Agents](https://quanticdata.io/mcp-server/)

## Related reading

[MCP & agents Give Ollama Internet Access: 360-Token Setup Ollama runs models, it does not browse. To give an Ollama model internet access you put an MCP client in front of it and connect a web-search server. On 2 October 2026 our full tool list measured 13,947 tokens, more than Ollama's 4,096-token default, so the setup below loads one tool for 356 tokens and caps every result. Read more](https://quanticdata.io/blog/give-ollama-internet-access/) [MCP & agents LM Studio MCP Web Search: 14K vs 360 Tokens LM Studio has been an MCP host since version 0.3.17, so web search is one block in mcp.json. The catch is in LM Studio's own docs: servers built for cloud models can flood a local context. We measured ours on 2 October 2026: 13,947 tokens for all 28 tools, 4,215 for the three web tools, 356 for one. Read more](https://quanticdata.io/blog/lm-studio-mcp-web-search/) [MCP & agents Qwen Web Search MCP: Qwen3 Online via Ollama A local Qwen3 model gets web search through Qwen-Agent, which speaks MCP. The config has one trap: a server with a URL is treated as SSE unless you set the type to streamable-http. On 2 October 2026 our full tool list measured 13,947 tokens; one tool measured 356, small enough for a 4K Qwen on a laptop. Read more](https://quanticdata.io/blog/qwen-web-search-mcp/)

---

Source: https://quanticdata.io/blog/open-webui-mcp-server/ · Site index for AI: https://quanticdata.io/llms.txt