github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-11 10:34:13 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #18233] issue: MCP Tools are not Properly Namespaced #138267

New Issue
Closed
opened 2026-05-25 09:54:46 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-25 09:54:46 -05:00
Owner
Copy Link

Originally created by @daryltucker on GitHub (Oct 11, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18233

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

latest

Ollama Version (if applicable)

No response

Operating System

Debian 13

Browser (if applicable)

No response

Confirmation

  • 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

As a consumer and client of MCP Servers, I expect Open WebUI to properly namespace the tools and methods available upon ingestion and processing.

Actual Behavior

Open WebUI flattens all methods into a single namespace meaning....

twitter.post
zipcodelookup.post

Are collapsed down to post, clash, and cause issues.

Steps to Reproduce

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-memory"]
    },
    "memory2": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-memory"]
    }
  }
}

Logs & Screenshots

open_webui.utils.tools:get_tools:199 - Tool tool_search_post already exists in another tools!

Additional Information

This is not the job of the MCP Server. The job of the MCP Server is to provide the tools, and no single tool has two identically named methods, because... well it cannot.

Other MCP Server clients handle this just fine, and namespace the methods under the providing tool.

The warning is also not helpful at all, simply claiming there is a method clash, without telling the User which tools are involved for resolution...
And since Inspector doesn't work against mcpo....

I am specifically seeing a lot of fetch or post clashes.

https://github.com/open-webui/mcpo/issues/242
https://github.com/modelcontextprotocol/inspector/issues/860

Originally created by @daryltucker on GitHub (Oct 11, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/18233 ### 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 Docker ### Open WebUI Version latest ### Ollama Version (if applicable) _No response_ ### Operating System Debian 13 ### Browser (if applicable) _No response_ ### 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 As a consumer and client of MCP Servers, I expect Open WebUI to properly namespace the tools and methods available upon ingestion and processing. ### Actual Behavior Open WebUI flattens all methods into a single namespace meaning.... `twitter.post` `zipcodelookup.post` Are collapsed down to `post`, clash, and cause issues. ### Steps to Reproduce ```json { "mcpServers": { "memory": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-memory"] }, "memory2": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-memory"] } } } ``` ### Logs & Screenshots ``` open_webui.utils.tools:get_tools:199 - Tool tool_search_post already exists in another tools! ``` ### Additional Information This is not the job of the MCP Server. The job of the MCP Server is to provide the tools, and no single tool has two identically named methods, because... well it cannot. Other MCP Server clients handle this just fine, and namespace the methods under the providing tool. The warning is also not helpful at all, simply claiming there is a method clash, without telling the User which tools are involved for resolution... And since Inspector doesn't work against `mcpo`.... I am specifically seeing a lot of `fetch` or `post` clashes. https://github.com/open-webui/mcpo/issues/242 https://github.com/modelcontextprotocol/inspector/issues/860
GiteaMirror added the bug label 2026-05-25 09:54:46 -05:00
GiteaMirror commented 2026-05-25 09:54:56 -05:00
Author
Owner
Copy Link

@daryltucker commented on GitHub (Oct 11, 2025):

Hey, actually they are... no idea where that came from...

<!-- gh-comment-id:3392923641 --> @daryltucker commented on GitHub (Oct 11, 2025): Hey, actually they are... no idea where that came from...
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#138267
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?