mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-09 23:35:09 -05:00
feat: User Level MCP Connections #6645
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#6645
Reference in New Issue
Block a user
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?
Originally created by @P0u4a on GitHub (Oct 10, 2025).
Check Existing Issues
Problem Description
It's great to see MCP connections are now supported. I've noticed at the moment only admins can create them globally. However, in an enterprise setting, having only the admin be able to add tools greatly diminishes the benefits of MCP, since admins can't add tools that require bearer token auth (the token is unique to each user).
Desired Solution you'd like
Extend the existing MCP support to allow users to to set their connection type to MCP and create MCP connections within the "External Tools" tab in settings. Of course, assuming the user has been granted permission to create external tools.
Alternatives Considered
No response
Additional Context
We could just use the OpenAPI tool server mode. However, this reduces adoption for our team due to the increased complexity when connecting to the proxy server, and we would really prefer to use the new MCP support.
@frenzybiscuit commented on GitHub (Oct 10, 2025):
Why cant you use this?
@P0u4a commented on GitHub (Oct 10, 2025):
As a non-admin user I don't see the option to change the connection type to MCP. It seems like it's only possible via the Admin setting, as it mentions in the docs also https://docs.openwebui.com/features/mcp#-quick-start
@frenzybiscuit commented on GitHub (Oct 10, 2025):
https://docs.openwebui.com/openapi-servers/mcp
@tjbck commented on GitHub (Oct 10, 2025):
Will not be supported due to security issues, use OAuth2.1 MCP servers instead.
@P0u4a commented on GitHub (Oct 11, 2025):
I understand the security implications, but the oauth spec in the protocol is not so great either with DCR, so using bearer auth is the most appropriate method for our use case. I don’t really see the problem if it’s locked behind an admin-assigned permission, not to mention you can already do user level tools via the OpenAPI tool server method, so I don’t see why it’s not the same for MCP, seems like a feature gap.
@P0u4a commented on GitHub (Oct 15, 2025):
@tjbck Could you take another look at this. There will be many MCP servers that won't support DCR like Github.
@tjbck commented on GitHub (Oct 15, 2025):
You can just use tokens as well, did you mean user specified tokens?
@P0u4a commented on GitHub (Oct 15, 2025):
Yeah user specified. In this case we know this is safe to do because it's an internal app with internal users.