Check Existing Issues

• I have searched for any existing and/or related issues.
• I have searched for any existing and/or related discussions.
• I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
• I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

v0.6.41

Ollama Version (if applicable)

No response

Operating System

Ubuntu

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

When running in a multi-node clustered environment with active Redis config sync in place, newly created tool servers should propagate to all nodes in the cluster and work uniformly across all users connecting to all servers.

Actual Behavior

Only works on the node it was created on, never propagates out.

• MCP OAuth clients are registered into in-memory oauth_client_manager at startup and during the config POST (backend/
  open_webui/main.py:1934-1955, backend/open_webui/routers/configs.py:162-194).
• OAuth handlers 404 when the client is missing (backend/open_webui/utils/oauth.py:560-578).
• Redis/DB sync exists for TOOL_SERVER_CONNECTIONS and OpenAPI spec cache, but not for the MCP OAuth client registry.
• Users randomly fail MCP OAuth flows in multi-node deployments, depending on which node the LB selects.

Steps to Reproduce

Create a new streamble HTTP OAuth 2.1 MCP server with a multi node cluster without sticky sessions enabled and try to use it. It will only work 1 out of how ever many nodes times you refresh at random.

Logs & Screenshots

Additional Information

PR incoming