I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.
Verify Feature Scope
I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
Problem Description
When working with MCP servers, individual users authenticate via OAuth to the upstream MCP. This is stored in the oauth_sessions table. Occasionally users have the desire to disconnect from a mcp, to re-authenticate to a different account, or need to refresh the connection for some reason. Currently the only way to do this is to delete the coresponding row in the oauth_sessions table.
Desired Solution you'd like
Provide a mechanism for users to disconnect/remove their credentials. A suggestion would be to add this to the tools menu, an example below of the UX of Gemini enterprise.
Additionally, as a nicety, add an option in the admin panel under users or connections to clear specific user connections or all connections for a specific MCP connection.
Alternatives Considered
Manually removing records from oauth_sessions DB table.
Additional Context
No response
Originally created by @anengineerdude on GitHub (Apr 23, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24039
### Check Existing Issues
- [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
### Verify Feature Scope
- [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
### Problem Description
When working with MCP servers, individual users authenticate via OAuth to the upstream MCP. This is stored in the `oauth_sessions` table. Occasionally users have the desire to disconnect from a mcp, to re-authenticate to a different account, or need to refresh the connection for some reason. Currently the only way to do this is to delete the coresponding row in the `oauth_sessions` table.
### Desired Solution you'd like
Provide a mechanism for users to disconnect/remove their credentials. A suggestion would be to add this to the tools menu, an example below of the UX of Gemini enterprise.
<img width="369" height="311" alt="Image" src="https://github.com/user-attachments/assets/81414f78-0a9c-48f1-b4ad-29caaa557269" />
Additionally, as a nicety, add an option in the admin panel under users or connections to clear specific user connections or all connections for a specific MCP connection.
### Alternatives Considered
Manually removing records from `oauth_sessions` DB table.
### Additional Context
_No response_
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 @anengineerdude on GitHub (Apr 23, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/24039
Check Existing Issues
Verify Feature Scope
Problem Description
When working with MCP servers, individual users authenticate via OAuth to the upstream MCP. This is stored in the
oauth_sessionstable. Occasionally users have the desire to disconnect from a mcp, to re-authenticate to a different account, or need to refresh the connection for some reason. Currently the only way to do this is to delete the coresponding row in theoauth_sessionstable.Desired Solution you'd like
Provide a mechanism for users to disconnect/remove their credentials. A suggestion would be to add this to the tools menu, an example below of the UX of Gemini enterprise.
Additionally, as a nicety, add an option in the admin panel under users or connections to clear specific user connections or all connections for a specific MCP connection.
Alternatives Considered
Manually removing records from
oauth_sessionsDB table.Additional Context
No response
@dude75 commented on GitHub (Apr 23, 2026):
Yes, that's a great idea. I also have to clean the database manually.
@tjbck commented on GitHub (Apr 24, 2026):
Addressed in dev.