open-webui/mcpo

Fork 0

mirror of https://github.com/open-webui/mcpo.git synced 2026-11-05 01:27:39 +00:00

[GH-ISSUE #124] issue: `Connection Failed` from user settings, but works from admin settings #55

New issue

Closed

opened 2026-10-18 21:11:00 +00:00 by bsakaguchi · 3 comments

bsakaguchi commented

2026-10-18 21:11:00 +00:00

Owner

Originally created by @abdessalaam on GitHub (May 9, 2025).
Original GitHub issue: https://github.com/open-webui/mcpo/issues/124

Check Existing Issues

I have searched the existing issues and discussions.
I am using the latest version of mcpo.

mcpo Version

v0.0.13

Open WebUI Version (if applicable)

v0.6.7 (latest)

Operating System

Ubuntu 24.04

Browser (if applicable)

No response

Confirmation

I have read and followed all instructions in README.md.
I am using the latest version of both MCPO and Open WebUI.
I have included the browser console logs.
I have included the Docker container logs.
I have listed steps to reproduce the bug in detail.

Expected Behavior

I run mcpo in docker following this set-up #86
When I want to add a new tool in OpenWebUI Admin Settings -> Tools, it works:

http://host.docker.internal:5002/memory

I would expect that adding exactly the same configuration and API token under my User Settings -> Tools should work as well.

Actual Behavior

When I try to add exactly the same setup under my User Settings -> Tools, the connection fails. The message is simply Connection failed.

Steps to Reproduce

Go to OpenWebUI Admin Settings -> Tools
Add a new mcpo server, e.g http://host.docker.internal:5002/memory and API
Check the connection -- this should work.
Delete if needed, and go to OpenWebUI User Settings -> Tools
Add a new mcpo server, e.g http://host.docker.internal:5002/memory and API
Check the connection -- Connection failed.

Logs & Screenshots

There are no logs visible in the docker logs, sadly, apart from the standard:

ai-mcpo                 | 2025-05-09T20:09:18.697375437Z INFO:     Started server process [1]
ai-mcpo                 | 2025-05-09T20:09:18.697451565Z INFO:     Waiting for application startup.
ai-mcpo                 | 2025-05-09T20:09:20.522993616Z Knowledge Graph MCP Server running on stdio
ai-mcpo                 | 2025-05-09T20:09:21.046925361Z INFO:     Application startup complete.
ai-mcpo                 | 2025-05-09T20:09:21.047104217Z INFO:     Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)
ai-mcpo                 | 2025-05-09T20:09:37.193510454Z Starting MCP OpenAPI Proxy with config file: /app/config.json
ai-mcpo                 | 2025-05-09T20:13:21.458538953Z INFO:     xx.xx.xx.xx:zzzz - "GET / HTTP/1.1" 404 Not Found
ai-mcpo                 | 2025-05-09T20:13:21.771740104Z INFO:     xx.xx.xx.xx:zzzz - "GET /favicon.ico HTTP/1.1" 404 Not Found
ai-mcpo                 | 2025-05-09T20:13:25.185304791Z INFO:     xx.xx.xx.xx:zzzz - "GET /docs HTTP/1.1" 200 OK
ai-mcpo                 | 2025-05-09T20:13:25.432911844Z INFO:     xx.xx.xx.xx:zzzz - "GET /openapi.json HTTP/1.1" 200 OK

Additional Information

No response

Originally created by @abdessalaam on GitHub (May 9, 2025). Original GitHub issue: https://github.com/open-webui/mcpo/issues/124 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of mcpo. ### mcpo Version v0.0.13 ### Open WebUI Version (if applicable) v0.6.7 (latest) ### Operating System Ubuntu 24.04 ### 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** MCPO and Open WebUI. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have listed steps to reproduce the bug in detail. ### Expected Behavior I run mcpo in docker following this set-up #86 When I want to add a new tool in OpenWebUI Admin Settings -> Tools, it works: `http://host.docker.internal:5002/memory` I would expect that adding exactly the same configuration and API token under my User Settings -> Tools should work as well. ### Actual Behavior When I try to add exactly the same setup under my User Settings -> Tools, the connection fails. The message is simply `Connection failed`. ### Steps to Reproduce 1. Go to OpenWebUI Admin Settings -> Tools 2. Add a new mcpo server, e.g `http://host.docker.internal:5002/memory` and API 3. Check the connection -- this should work. 4. Delete if needed, and go to OpenWebUI User Settings -> Tools 5. Add a new mcpo server, e.g `http://host.docker.internal:5002/memory` and API 6. Check the connection -- `Connection failed`. ### Logs & Screenshots There are no logs visible in the docker logs, sadly, apart from the standard: ``` ai-mcpo | 2025-05-09T20:09:18.697375437Z INFO: Started server process [1] ai-mcpo | 2025-05-09T20:09:18.697451565Z INFO: Waiting for application startup. ai-mcpo | 2025-05-09T20:09:20.522993616Z Knowledge Graph MCP Server running on stdio ai-mcpo | 2025-05-09T20:09:21.046925361Z INFO: Application startup complete. ai-mcpo | 2025-05-09T20:09:21.047104217Z INFO: Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit) ai-mcpo | 2025-05-09T20:09:37.193510454Z Starting MCP OpenAPI Proxy with config file: /app/config.json ai-mcpo | 2025-05-09T20:13:21.458538953Z INFO: xx.xx.xx.xx:zzzz - "GET / HTTP/1.1" 404 Not Found ai-mcpo | 2025-05-09T20:13:21.771740104Z INFO: xx.xx.xx.xx:zzzz - "GET /favicon.ico HTTP/1.1" 404 Not Found ai-mcpo | 2025-05-09T20:13:25.185304791Z INFO: xx.xx.xx.xx:zzzz - "GET /docs HTTP/1.1" 200 OK ai-mcpo | 2025-05-09T20:13:25.432911844Z INFO: xx.xx.xx.xx:zzzz - "GET /openapi.json HTTP/1.1" 200 OK ``` ### Additional Information _No response_

bsakaguchi

2026-10-18 21:11:00 +00:00

closed this issue
added the
bug
label

bsakaguchi commented

2026-10-18 21:11:01 +00:00

Author

Owner

@nickfixit commented on GitHub (May 21, 2025):

How do we resolve this. It's frustrating

@nickfixit commented on GitHub (May 21, 2025): How do we resolve this. It's frustrating

bsakaguchi commented

2026-10-18 21:11:02 +00:00

Author

Owner

@u6tory commented on GitHub (Jun 15, 2025):

Same issue. My case was caused by a Mixed Content problem. My OpenWebUI is hosted on HTTPS, but MCPO was on HTTP. I solved this by adding HTTPS to my MCPO server. Adding tools for admin settings is in progress on the backend, but for user settings, it's on the frontend, browser-side.

@u6tory commented on GitHub (Jun 15, 2025): Same issue. My case was caused by a Mixed Content problem. My OpenWebUI is hosted on HTTPS, but MCPO was on HTTP. I solved this by adding HTTPS to my MCPO server. Adding tools for admin settings is in progress on the backend, but for user settings, it's on the frontend, browser-side.

bsakaguchi commented

2026-10-18 21:11:02 +00:00

Author

Owner

@taylorwilsdon commented on GitHub (Aug 2, 2025):

When I want to add a new tool in OpenWebUI Admin Settings -> Tools, it works:

http://host.docker.internal:5002/memory

I would expect that adding exactly the same configuration and API token under my User Settings -> Tools should work as well.

To clarify, that is not how it works. If you add from user settings -> tools, the calls take place on the client side - from your browser to the tool server. When added centrally in the admin panel, the calls are made from the server backend, not the client, so if you're running something on localhost on your laptop you'll only be able to reach it that way by user-scoped tool installation.

Closing as this is unrelated to MCPO / just related to Open WebUI, but u6tory has a great callout to check - if you're getting errors, look in your open webui logs to see if it's something like mixed http/https or a network path issue (ie trying to use localhost when the tool server isn't running on the same host as open-webui)

@taylorwilsdon commented on GitHub (Aug 2, 2025): >When I want to add a new tool in OpenWebUI Admin Settings -> Tools, it works: >http://host.docker.internal:5002/memory > I would expect that adding exactly the same configuration and API token under my User Settings -> Tools should work as well. To clarify, that is not how it works. If you add from user settings -> tools, the calls take place on the client side - from your browser to the tool server. When added centrally in the admin panel, the calls are made from the server backend, not the client, so if you're running something on localhost on your laptop you'll only be able to reach it that way by user-scoped tool installation. Closing as this is unrelated to MCPO / just related to Open WebUI, but u6tory has a great callout to check - if you're getting errors, look in your open webui logs to see if it's something like mixed http/https or a network path issue (ie trying to use localhost when the tool server isn't running on the same host as open-webui)