Originally created by @17jmumford on GitHub (Jul 23, 2025).
Check Existing Issues
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.18 (latest)
Ollama Version (if applicable)
No response
Operating System
ubuntu-latest-arm on AWS
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
The expected behavior is that when one admin adds a Global Tool Server in the admin settings (as opposed to a user tool server in the user settings), other admins can see it, and it appears when added to groups or made public. See documentation here: https://docs.openwebui.com/openapi-servers/open-webui
Actual Behavior
Only the admin that created the Global Tool Server is able to see it.
Steps to Reproduce
The first admin creates a Global Tool Server (in our case, we are using MCPO)
The second admin logins and checks for the GTS. It is not there :(
Logs & Screenshots
console logs
The empty view for the second admin :(
NOTE: I am going to update this with the Docker logs soon, we just synced our deployment with Datadog.
Additional Information
Yeah this a weird one. Let me know if there is extra info you need from me. It sounds like some others have run into this as well: https://github.com/open-webui/open-webui/issues/12796. Hopefully this better documented issue helps though!
Originally created by @17jmumford on GitHub (Jul 23, 2025).
### 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.18 (latest)
### Ollama Version (if applicable)
_No response_
### Operating System
ubuntu-latest-arm on AWS
### 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
The expected behavior is that when one admin adds a Global Tool Server in the admin settings (as opposed to a user tool server in the user settings), other admins can see it, and it appears when added to groups or made public. See documentation here: https://docs.openwebui.com/openapi-servers/open-webui
### Actual Behavior
Only the admin that created the Global Tool Server is able to see it.
### Steps to Reproduce
1. The first admin creates a Global Tool Server (in our case, we are using MCPO)
2. The second admin logins and checks for the GTS. It is not there :(
### Logs & Screenshots
console logs
<img width="1101" height="505" alt="Image" src="https://github.com/user-attachments/assets/6a3d42f9-6e64-4956-bf6c-508e9222b8bc" />
The empty view for the second admin :(
<img width="1135" height="259" alt="Image" src="https://github.com/user-attachments/assets/d1263feb-160b-41cb-9b00-8caa70c644a4" />
NOTE: I am going to update this with the Docker logs soon, we just synced our deployment with Datadog.
### Additional Information
Yeah this a weird one. Let me know if there is extra info you need from me. It sounds like some others have run into this as well: https://github.com/open-webui/open-webui/issues/12796. Hopefully this better documented issue helps though!
GiteaMirror
added the bug label 2025-11-11 16:35:44 -06:00
We're unable to reproduce, could you confirm the tool servers data was saved correctly? (In the admin settings, not the user settings)
@tjbck commented on GitHub (Jul 23, 2025):
We're unable to reproduce, could you confirm the tool servers data was saved correctly? (In the admin settings, not the user settings)
We're unable to reproduce, could you confirm the tool servers data was saved correctly? (In the admin settings, not the user settings)
yes, let me get a screenshot from the first admin real quick
@17jmumford commented on GitHub (Jul 23, 2025):
> We're unable to reproduce, could you confirm the tool servers data was saved correctly? (In the admin settings, not the user settings)
yes, let me get a screenshot from the first admin real quick
Here is a screenshot from the first admin. He's left and returned to this page a bunch.
Additionally, he was able to attach it to a model:
But when I view that same model, the tool is not present:
@17jmumford commented on GitHub (Jul 23, 2025):
Here is a screenshot from the first admin. He's left and returned to this page a bunch.
<img width="4554" height="910" alt="Image" src="https://github.com/user-attachments/assets/d010e64b-ccf4-4949-ac66-97ee9012686a" />
Additionally, he was able to attach it to a model:
<img width="1062" height="328" alt="Image" src="https://github.com/user-attachments/assets/99f6ceac-d293-4e53-b99c-faa896710e6c" />
But when I view that same model, the tool is not present:
<img width="557" height="150" alt="Image" src="https://github.com/user-attachments/assets/d448def9-c709-4d50-b5bb-99ae92e61da0" />
I tried looking through our docker logs on Datadog. There are a lot of logs. This seemed to be most relevant one? Just a standard 304 AKA nothing changed on this page.
Generally, all seems well when I search for /tools in our logs
@17jmumford commented on GitHub (Jul 23, 2025):
I tried looking through our docker logs on Datadog. There are a lot of logs. This seemed to be most relevant one? Just a standard 304 AKA nothing changed on this page.
<img width="1230" height="150" alt="Image" src="https://github.com/user-attachments/assets/099cae58-d11a-4c26-8f55-8de9afe2ca72" />
Generally, all seems well when I search for /tools in our logs
<img width="1733" height="928" alt="Image" src="https://github.com/user-attachments/assets/e8ad08b1-eb43-404b-b4aa-602a39b182d4" />
could you show the server-mcp connection config (right gear in tools/general) ?
Is it config as public or private but with access for right groups?
@rgaricano commented on GitHub (Jul 23, 2025):
could you show the server-mcp connection config (right gear in tools/general) ?
Is it config as public or private but with access for right groups?
Here are some screenshots from the first dev. We've tried making it public, sharing it with groups, etc
@17jmumford commented on GitHub (Jul 23, 2025):
Here are some screenshots from the first dev. We've tried making it public, sharing it with groups, etc
<img width="1062" height="1006" alt="Image" src="https://github.com/user-attachments/assets/bd404509-bfd0-4296-839f-287029109f34" />
<img width="1062" height="1232" alt="Image" src="https://github.com/user-attachments/assets/62e9b070-b389-4b3c-8740-cc7a42c39e5f" />
Also recheck permissions for defaults & for groups, that its have Tool access & Tools Public Sharing enabled.
@rgaricano commented on GitHub (Jul 23, 2025):
Also recheck permissions for defaults & for groups, that its have Tool access & Tools Public Sharing enabled.
@PhilosophiMoonbeam commented on GitHub (Jul 23, 2025):
Am having these tool issues. No custom OpenAI Tool Server or MCPs, just bog standard tool selection for models.
Admins unaffected but model tools unavailable to other users.
@PhilosophiMoonbeam commented on GitHub (Jul 23, 2025):
Am having these tool issues. No custom OpenAI Tool Server or MCPs, just bog standard tool selection for models.
Admins unaffected but model tools unavailable to other users.
I have had a similar problem, which was due to misconfigured redis connection on a multi-replica OWUI deployment (on my end I added a tool but wasn't able to see it on the TOOL_SERVER_CONNECTIONS API). Mightn't be that case but writing this for future documentation.
@expruc commented on GitHub (Jul 23, 2025):
I have had a similar problem, which was due to misconfigured redis connection on a multi-replica OWUI deployment (on my end I added a tool but wasn't able to see it on the `TOOL_SERVER_CONNECTIONS` API). Mightn't be that case but writing this for future documentation.
Redeploying seems to have mostly fixed it. I wonder if cause is related to to what @expruc called out, as we do have a multi-replica deployment.
@17jmumford commented on GitHub (Jul 23, 2025):
Redeploying seems to have mostly fixed it. I wonder if cause is related to to what @expruc called out, as we do have a multi-replica deployment.
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 @17jmumford on GitHub (Jul 23, 2025).
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.18 (latest)
Ollama Version (if applicable)
No response
Operating System
ubuntu-latest-arm on AWS
Browser (if applicable)
Chrome
Confirmation
README.md.Expected Behavior
The expected behavior is that when one admin adds a Global Tool Server in the admin settings (as opposed to a user tool server in the user settings), other admins can see it, and it appears when added to groups or made public. See documentation here: https://docs.openwebui.com/openapi-servers/open-webui
Actual Behavior
Only the admin that created the Global Tool Server is able to see it.
Steps to Reproduce
Logs & Screenshots
console logs

The empty view for the second admin :(

NOTE: I am going to update this with the Docker logs soon, we just synced our deployment with Datadog.
Additional Information
Yeah this a weird one. Let me know if there is extra info you need from me. It sounds like some others have run into this as well: https://github.com/open-webui/open-webui/issues/12796. Hopefully this better documented issue helps though!
@tjbck commented on GitHub (Jul 23, 2025):
We're unable to reproduce, could you confirm the tool servers data was saved correctly? (In the admin settings, not the user settings)
@17jmumford commented on GitHub (Jul 23, 2025):
yes, let me get a screenshot from the first admin real quick
@17jmumford commented on GitHub (Jul 23, 2025):
Here is a screenshot from the first admin. He's left and returned to this page a bunch.
Additionally, he was able to attach it to a model:
But when I view that same model, the tool is not present:
@17jmumford commented on GitHub (Jul 23, 2025):
I tried looking through our docker logs on Datadog. There are a lot of logs. This seemed to be most relevant one? Just a standard 304 AKA nothing changed on this page.
Generally, all seems well when I search for /tools in our logs
@rgaricano commented on GitHub (Jul 23, 2025):
could you show the server-mcp connection config (right gear in tools/general) ?
Is it config as public or private but with access for right groups?
@17jmumford commented on GitHub (Jul 23, 2025):
Here are some screenshots from the first dev. We've tried making it public, sharing it with groups, etc
@17jmumford commented on GitHub (Jul 23, 2025):
We're going to re-deploy our instance to see if that fixes anything
@rgaricano commented on GitHub (Jul 23, 2025):
Also recheck permissions for defaults & for groups, that its have Tool access & Tools Public Sharing enabled.
@PhilosophiMoonbeam commented on GitHub (Jul 23, 2025):
Am having these tool issues. No custom OpenAI Tool Server or MCPs, just bog standard tool selection for models.
Admins unaffected but model tools unavailable to other users.
@expruc commented on GitHub (Jul 23, 2025):
I have had a similar problem, which was due to misconfigured redis connection on a multi-replica OWUI deployment (on my end I added a tool but wasn't able to see it on the
TOOL_SERVER_CONNECTIONSAPI). Mightn't be that case but writing this for future documentation.@17jmumford commented on GitHub (Jul 23, 2025):
Redeploying seems to have mostly fixed it. I wonder if cause is related to to what @expruc called out, as we do have a multi-replica deployment.