mirror of
https://github.com/open-webui/open-webui.git
synced 2026-08-30 17:25:30 -05:00
feat: Annoying notifications about no connection to the tools server #5873
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#5873
Reference in New Issue
Block a user
Originally created by @hz61p1 on GitHub (Jul 25, 2025).
Check Existing Issues
Problem Description
When self-hosting openwebui in the cloud and connecting the tool's servers at the user level, notifications constantly pop up when opening openwebui about the inability to connect if the user has not launched mcpo locally, which is not always possible, for example on a phone
Desired Solution you'd like
Add control over the activation of server tools at the chat level, similar to how they are selectively enabled if added globally
Alternatives Considered
No response
Additional Context
No response
@rgaricano commented on GitHub (Jul 26, 2025):
Just disable the tools if mcpo it's down, this can be done through UI.
As it's logic, if are server side tools its have to be enabled/disabled by admins.
Other way is add its in client side, against same mcpo but with public IP.
e.g. yesterday I did some test for this "issue": https://github.com/open-webui/open-webui/issues/15939
same mcpo server, server side and client side tools.
@hz61p1 commented on GitHub (Jul 26, 2025):
Sounds like a crutch)) I have a dozen servers connected to my work machine, and I always need them. They always run in the background, so they are always available, but when I open my phone for personal reasons or something else, I get a dozen notifications saying that I cannot connect. If I turn them off, I will have to turn them back on when I return to my work machine. Moreover, they cannot be quickly turned off or on; you have to go to the settings every time. And I can't configure them globally because I need access to local files and other things that are only on my work machine
@rgaricano commented on GitHub (Jul 27, 2025):
Why can't you connect from the phone and you get errors? That's what I don't understand: why are the tools server(s) turned off? or why aren't the IPs unreachable?
And as I said, one solution is to have them as a direct connection for tools in the user panel, and then you can disable them from permissions.
But yes, that same switch would be good for the server side, similar to the one for connections.
@hz61p1 commented on GitHub (Jul 27, 2025):
Because they are launched locally, they are only accessible via localhost:8000/*