I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
Expected Behavior
search the web using configure search provider ollama cloud search and have fetch MCP available for fetching other raw urls.
Actual Behavior
result:
1: search returns results, fetch
2: MCP gets triggered and fetrhes raw content from result links (I can see result json with raw web contents)
3: ### STUCK ###
Steps to Reproduce
reproduction:
configure ollama cloud search in settings for search tool.
load some model that allows tools like llama3.2:3b and enable web search tool from open-webui.
ask the model to search the web and sumarize results.
Logs & Screenshots
ollama logs:
2025-10-02T21:57:42.988Z|time=2025-10-02T21:57:42.988Zlevel=WARNsource=harmonyparser.go:482msg="harmony parser: no reverse mapping found for function name"harmonyFunctionName=search
Additional Information
web->MCP_FETCH->¿web?
should be
web->web_fetch->web || prompts <-> fetch_mcp
As documented, if one tries to register two mcp with the same name or that provide the same tool an error or warning appears but this scenario seems to break that unbreakable rule.
Originally created by @gattytto on GitHub (Oct 4, 2025).
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Pip Install
### Open WebUI Version
v0.6.32 (latest)
### Ollama Version (if applicable)
0.12.3
### Operating System
nvidia runtime, kubernetes upstream, ubuntu, lxd/baremetal
### Browser (if applicable)
chrome
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
search the web using configure search provider ollama cloud search and have fetch MCP available for fetching other raw urls.
### Actual Behavior
result:
1: search returns results, fetch
2: MCP gets triggered and fetrhes raw content from result links (I can see result json with raw web contents)
3: ### STUCK ###
### Steps to Reproduce
reproduction:
configure ollama cloud search in settings for search tool.
mcpo config:
```json
{
"fetch": {
"command": "uvx",
"args": ["mcp-server-fetch"]
},
}
```
load some model that allows tools like ```llama3.2:3b``` and enable web search tool from open-webui.
ask the model to search the web and sumarize results.
### Logs & Screenshots
ollama logs:
```verilog
2025-10-02T21:57:42.988Z | time=2025-10-02T21:57:42.988Z level=WARN source=harmonyparser.go:482 msg="harmony parser: no reverse mapping found for function name" harmonyFunctionName=search
```
### Additional Information
web->MCP_FETCH->¿web?
should be
web->web_fetch->web || prompts <-> fetch_mcp
As documented, if one tries to register two mcp with the same name or that provide the same tool an error or warning appears but this scenario seems to break that unbreakable rule.
GiteaMirror
added the bug label 2025-11-11 17:00:20 -06:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @gattytto on GitHub (Oct 4, 2025).
Check Existing Issues
Installation Method
Pip Install
Open WebUI Version
v0.6.32 (latest)
Ollama Version (if applicable)
0.12.3
Operating System
nvidia runtime, kubernetes upstream, ubuntu, lxd/baremetal
Browser (if applicable)
chrome
Confirmation
README.md.Expected Behavior
search the web using configure search provider ollama cloud search and have fetch MCP available for fetching other raw urls.
Actual Behavior
result:
1: search returns results, fetch
2: MCP gets triggered and fetrhes raw content from result links (I can see result json with raw web contents)
3: ### STUCK ###
Steps to Reproduce
reproduction:
configure ollama cloud search in settings for search tool.
mcpo config:
load some model that allows tools like
llama3.2:3band enable web search tool from open-webui.ask the model to search the web and sumarize results.
Logs & Screenshots
ollama logs:
Additional Information
web->MCP_FETCH->¿web?
should be
web->web_fetch->web || prompts <-> fetch_mcp
As documented, if one tries to register two mcp with the same name or that provide the same tool an error or warning appears but this scenario seems to break that unbreakable rule.
@gattytto commented on GitHub (Oct 4, 2025):
screenshots
https://github.com/ollama/ollama/issues/11991#issuecomment-3363379465
@tjbck commented on GitHub (Oct 4, 2025):
You should give it an id, it'll be prepended to all tool function names.