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.7.2

Ollama Version (if applicable)

No response

Operating System

Ubuntu 24.04

Browser (if applicable)

No response

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 URL entered by the user (https://api.example.com/mcp/) should be saved and used exactly as provided, preserving the trailing slash.

Actual Behavior

When configuring a Model Context Protocol (MCP) server via the OpenWebUI web interface, a trailing slash (/) at the end of the server URL is automatically removed upon saving. This causes the client to send requests to an incorrect endpoint, triggering a server-side redirect (301). During this redirect, critical authentication headers (like Authorization: Bearer) are lost or the request method changes, ultimately resulting in a 400 Bad Request error.

This is a critical issue for integrating with MCP servers (like Bitrix24) that strictly require a specific path format.

Steps to Reproduce

Go to the MCP servers configuration section in the OpenWebUI settings.

Add a new server with a URL that requires a trailing slash (e.g., https://api.example.com/mcp/).

Save the configuration.

Observe that the saved/displayed URL is now https://api.example.com/mcp (slash is missing).

Attempt to use this MCP server. The client will fail to connect, and the logs will show a 301 Moved Permanently followed by a 400 Bad Request.

Logs & Screenshots

docker logs

httpx._client:_send_single_request:1740 - HTTP Request: POST https://mcp.bitrix24.tech/mcp "HTTP/1.1 301 Moved Permanently"
httpx._client:_send_single_request:1740 - HTTP Request: GET https://mcp.bitrix24.tech/mcp/ "HTTP/1.1 400 Bad Request"

Additional Information

No response