I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
v0.6.23
Ollama Version (if applicable)
No response
Operating System
Ubuntu
Browser (if applicable)
Chrome
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
Use chat with attached MCP Tools
Actual Behavior
MCP Tools are missing from all models in the Workspace
Steps to Reproduce
Pull new image and recreate the container
Login to new instance
Chat as normal and only the local tools are listed
Check the model in the Workspace and all the MCP Tools are missing
/admin/settings/tools:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Additional Information
No response
Originally created by @cma2t3r on GitHub (Aug 21, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16796
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
v0.6.23
### Ollama Version (if applicable)
_No response_
### Operating System
Ubuntu
### 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
Use chat with attached MCP Tools
### Actual Behavior
MCP Tools are missing from all models in the Workspace
### Steps to Reproduce
1. Pull new image and recreate the container
2. Login to new instance
3. Chat as normal and only the local tools are listed
4. Check the model in the Workspace and all the MCP Tools are missing
<img width="1017" height="273" alt="Image" src="https://github.com/user-attachments/assets/7d6ba3b7-30fa-416c-ba51-731114c05c51" />
### Logs & Screenshots
Docker / Open-Webui log:
2025-08-21 21:16:15.501 | INFO | open_webui.utils.tools:get_tool_server_data:541 - Fetched data: {'openapi': {'openapi': '3.1.0', 'info': {'title': 'ddg-search', 'description': 'ddg-search MCP Server', 'version': '1.3.0'}, 'servers': [{'url': '/duckduckgo'}], 'paths': {'/search': {'post': {'summary': 'Search', 'description': 'Search DuckDuckGo and return formatted results.\n\nArgs:\n query: The search query string\n max_results: Maximum number of results to return (default: 10)\n ctx: MCP context for logging', 'operationId': 'tool_search_post', 'requestBody': {'content': {'application/json': {'schema': {'$ref': '#/components/schemas/search_form_model'}}}, 'required': True}, 'responses': {'200': {'description': 'Successful Response', 'content': {'application/json': {'schema': {'title': 'Response Tool Search Post'}}}}, '422': {'description': 'Validation Error', 'content': {'application/json': {'schema': {'$ref': '#/components/schemas/HTTPValidationError'}}}}}}}, '/fetch_content': {'post': {'summary': 'Fetch Content', 'description': 'Fetch and parse content from a webpage URL.\n\nArgs:\n url: The webpage URL to fetch content from\n ctx: MCP context for logging', 'operationId': 'tool_fetch_content_post', 'requestBody': {'content': {'application/json': {'schema': {'$ref': '#/components/schemas/fetch_content_form_model'}}}, 'required': True}, 'responses': {'200': {'description': 'Successful Response', 'content': {'application/json': {'schema': {'title': 'Response Tool Fetch Content Post'}}}}, '422': {'description': 'Validation Error', 'content': {'application/json': {'schema': {'$ref': '#/components/schemas/HTTPValidationError'}}}}}}}}, 'components': {'schemas': {'HTTPValidationError': {'properties': {'detail': {'items': {'$ref': '#/components/schemas/ValidationError'}, 'type': 'array', 'title': 'Detail'}}, 'type': 'object', 'title': 'HTTPValidationError'}, 'ValidationError': {'properties': {'loc': {'items': {'anyOf': [{'type': 'string'}, {'type': 'integer'}]}, 'type': 'array', 'title': 'Location'}, 'msg': {'type': 'string', 'title': 'Message'}, 'type': {'type': 'string', 'title': 'Error Type'}}, 'type': 'object', 'required': ['loc', 'msg', 'type'], 'title': 'ValidationError'}, 'fetch_content_form_model': {'properties': {'url': {'type': 'string', 'title': 'Url', 'description': ''}}, 'type': 'object', 'required': ['url'], 'title': 'fetch_content_form_model'}, 'search_form_model': {'properties': {'query': {'type': 'string', 'title': 'Query', 'description': ''}, 'max_results': {'type': 'integer', 'title': 'Max Results', 'description': '', 'default': 10}}, 'type': 'object', 'required': ['query'], 'title': 'search_form_model'}}}}, 'info': {'title': 'ddg-search', 'description': 'ddg-search MCP Server', 'version': '1.3.0'}, 'specs': [{'name': 'tool_search_post', 'description': 'Search DuckDuckGo and return formatted results.\n\nArgs:\n query: The search query string\n max_results: Maximum number of results to return (default: 10)\n ctx: MCP context for logging', 'parameters': {'type': 'object', 'properties': {'query': {'type': 'string', 'title': 'Query', 'description': ''}, 'max_results': {'type': 'integer', 'title': 'Max Results', 'description': '', 'default': 10}}, 'required': ['query']}}, {'name': 'tool_fetch_content_post', 'description': 'Fetch and parse content from a webpage URL.\n\nArgs:\n url: The webpage URL to fetch content from\n ctx: MCP context for logging', 'parameters': {'type': 'object', 'properties': {'url': {'type': 'string', 'title': 'Url', 'description': ''}}, 'required': ['url']}}]}
Browser console:
/admin/settings/tools:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-15 13:35:04 -05:00
I can't believe they overlooked this. This is the only way to use MCP, and they've screwed it up.
The way I see it, they should leave MCPO behind and migrate directly to MCP.
The more tools they have to maintain, the worse the maintainability.
<!-- gh-comment-id:3212250223 -->
@vk2r commented on GitHub (Aug 21, 2025):
I can't believe they overlooked this. This is the only way to use MCP, and they've screwed it up.
The way I see it, they should leave MCPO behind and migrate directly to MCP.
The more tools they have to maintain, the worse the maintainability.
MCPO is useful for those cases where the MCP Tool traffic needs to originate in a specific node to access an isolated/restricted resource.
<!-- gh-comment-id:3212265277 -->
@cma2t3r commented on GitHub (Aug 21, 2025):
MCPO is useful for those cases where the MCP Tool traffic needs to originate in a specific node to access an isolated/restricted resource.
Not sure if YouTube transcript tool is related, but that isn't working for me either.
<!-- gh-comment-id:3212310406 -->
@JHawx79 commented on GitHub (Aug 21, 2025):
Not sure if YouTube transcript tool is related, but that isn't working for me either.
In the past, when the MCP tool stopped working, simply restarting it resolved the issue. However, this time, even after deleting and re-adding it, the problem persists.
<!-- gh-comment-id:3212705605 -->
@zhangruicn commented on GitHub (Aug 22, 2025):
In the past, when the MCP tool stopped working, simply restarting it resolved the issue. However, this time, even after deleting and re-adding it, the problem persists.
Same issue, the + button in chat doesn't bring up enabled tools anymore either.
<!-- gh-comment-id:3212811642 -->
@healdgar commented on GitHub (Aug 22, 2025):
Same issue, the + button in chat doesn't bring up enabled tools anymore either.
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 @cma2t3r on GitHub (Aug 21, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16796
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.23
Ollama Version (if applicable)
No response
Operating System
Ubuntu
Browser (if applicable)
Chrome
Confirmation
README.md.Expected Behavior
Use chat with attached MCP Tools
Actual Behavior
MCP Tools are missing from all models in the Workspace
Steps to Reproduce
Logs & Screenshots
Docker / Open-Webui log:
2025-08-21 21:16:15.501 | INFO | open_webui.utils.tools:get_tool_server_data:541 - Fetched data: {'openapi': {'openapi': '3.1.0', 'info': {'title': 'ddg-search', 'description': 'ddg-search MCP Server', 'version': '1.3.0'}, 'servers': [{'url': '/duckduckgo'}], 'paths': {'/search': {'post': {'summary': 'Search', 'description': 'Search DuckDuckGo and return formatted results.\n\nArgs:\n query: The search query string\n max_results: Maximum number of results to return (default: 10)\n ctx: MCP context for logging', 'operationId': 'tool_search_post', 'requestBody': {'content': {'application/json': {'schema': {'$ref': '#/components/schemas/search_form_model'}}}, 'required': True}, 'responses': {'200': {'description': 'Successful Response', 'content': {'application/json': {'schema': {'title': 'Response Tool Search Post'}}}}, '422': {'description': 'Validation Error', 'content': {'application/json': {'schema': {'$ref': '#/components/schemas/HTTPValidationError'}}}}}}}, '/fetch_content': {'post': {'summary': 'Fetch Content', 'description': 'Fetch and parse content from a webpage URL.\n\nArgs:\n url: The webpage URL to fetch content from\n ctx: MCP context for logging', 'operationId': 'tool_fetch_content_post', 'requestBody': {'content': {'application/json': {'schema': {'$ref': '#/components/schemas/fetch_content_form_model'}}}, 'required': True}, 'responses': {'200': {'description': 'Successful Response', 'content': {'application/json': {'schema': {'title': 'Response Tool Fetch Content Post'}}}}, '422': {'description': 'Validation Error', 'content': {'application/json': {'schema': {'$ref': '#/components/schemas/HTTPValidationError'}}}}}}}}, 'components': {'schemas': {'HTTPValidationError': {'properties': {'detail': {'items': {'$ref': '#/components/schemas/ValidationError'}, 'type': 'array', 'title': 'Detail'}}, 'type': 'object', 'title': 'HTTPValidationError'}, 'ValidationError': {'properties': {'loc': {'items': {'anyOf': [{'type': 'string'}, {'type': 'integer'}]}, 'type': 'array', 'title': 'Location'}, 'msg': {'type': 'string', 'title': 'Message'}, 'type': {'type': 'string', 'title': 'Error Type'}}, 'type': 'object', 'required': ['loc', 'msg', 'type'], 'title': 'ValidationError'}, 'fetch_content_form_model': {'properties': {'url': {'type': 'string', 'title': 'Url', 'description': ''}}, 'type': 'object', 'required': ['url'], 'title': 'fetch_content_form_model'}, 'search_form_model': {'properties': {'query': {'type': 'string', 'title': 'Query', 'description': ''}, 'max_results': {'type': 'integer', 'title': 'Max Results', 'description': '', 'default': 10}}, 'type': 'object', 'required': ['query'], 'title': 'search_form_model'}}}}, 'info': {'title': 'ddg-search', 'description': 'ddg-search MCP Server', 'version': '1.3.0'}, 'specs': [{'name': 'tool_search_post', 'description': 'Search DuckDuckGo and return formatted results.\n\nArgs:\n query: The search query string\n max_results: Maximum number of results to return (default: 10)\n ctx: MCP context for logging', 'parameters': {'type': 'object', 'properties': {'query': {'type': 'string', 'title': 'Query', 'description': ''}, 'max_results': {'type': 'integer', 'title': 'Max Results', 'description': '', 'default': 10}}, 'required': ['query']}}, {'name': 'tool_fetch_content_post', 'description': 'Fetch and parse content from a webpage URL.\n\nArgs:\n url: The webpage URL to fetch content from\n ctx: MCP context for logging', 'parameters': {'type': 'object', 'properties': {'url': {'type': 'string', 'title': 'Url', 'description': ''}}, 'required': ['url']}}]}
Browser console:
/admin/settings/tools:1 Uncaught (in promise) Error: A listener indicated an asynchronous response by returning true, but the message channel closed before a response was received
Additional Information
No response
@vk2r commented on GitHub (Aug 21, 2025):
I can't believe they overlooked this. This is the only way to use MCP, and they've screwed it up.
The way I see it, they should leave MCPO behind and migrate directly to MCP.
The more tools they have to maintain, the worse the maintainability.
@cma2t3r commented on GitHub (Aug 21, 2025):
MCPO is useful for those cases where the MCP Tool traffic needs to originate in a specific node to access an isolated/restricted resource.
@JHawx79 commented on GitHub (Aug 21, 2025):
Not sure if YouTube transcript tool is related, but that isn't working for me either.
@jhemmond commented on GitHub (Aug 22, 2025):
Time to downgrade until this is figured out. Big feature to miss..
@papajbeautiful commented on GitHub (Aug 22, 2025):
+1
No tool servers available in models after upgrade.
@zhangruicn commented on GitHub (Aug 22, 2025):
In the past, when the MCP tool stopped working, simply restarting it resolved the issue. However, this time, even after deleting and re-adding it, the problem persists.
@healdgar commented on GitHub (Aug 22, 2025):
Same issue, the + button in chat doesn't bring up enabled tools anymore either.
@tjbck commented on GitHub (Aug 22, 2025):
#16803