github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-12 00:43:31 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #23782] issue: Bug: MCP connection succeeds in Admin Console but fails in User Extensions page (UI & field mismatch) #35602

New Issue
Closed
opened 2026-04-25 09:46:49 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-25 09:46:49 -05:00
Owner
Copy Link

Originally created by @lovesec on GitHub (Apr 16, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23782

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

Docker

Open WebUI Version

v0.8.10

Ollama Version (if applicable)

No response

Operating System

Ubuntu 22.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

Verification successful

Actual Behavior

Environment
Open WebUI version: v0.8.10 (issue first observed)

Admin Console version: v0.8.12 (UI differences still present)

Steps to Reproduce
Admin Console (works)
Go to: Admin Console → Settings → Integrations

Click Add Connection

Select MCP Stream HTTP

Fill in:

Name

Description

URL

Authentication: None

Save → Connection succeeds

User Extensions Page (fails)
Go to: User Settings → Extensions

Click Add Extension Tool

Select MCP Stream HTTP

Fill in the exact same values as used in Admin Console

Save → Connection fails

Actual Result
Admin Console: MCP tool connects successfully

User Extensions page: Same configuration fails to connect

User cannot use MCP tools that work for the admin

Expected Result
Both Admin Console and User Extensions should use the same MCP connection logic

A valid MCP configuration should succeed in both places

UI fields and internal parameters should be consistent

UI / Field Differences (Critical)
Admin Console – Add/Edit Connection
Fields shown:

Type: MCP Stream HTTP

Name

ID (only visible in Edit mode)

Description

URL

Authentication: None

Advanced section

Function name filter list

Warning: MCP is experimental

Buttons: Save / Delete

User Extensions – Add Extension Tool
Fields shown:

Type: MCP Stream HTTP

Name

Description

URL

Authentication: No authentication

No ID field

No Advanced section

No function filter list

Button: Save

Impact
Users cannot use MCP tools that administrators have configured

MCP tools cannot be shared across the organization

Inconsistent UI suggests inconsistent backend handling

Hard to debug because Admin and User flows behave differently

Possible Root Causes
Admin Console and User Extensions use different MCP client implementations

Missing fields (ID, advanced metadata) cause User Extensions to send incomplete MCP handshake

User Extensions may not follow the same HTTP streaming protocol

User Extensions may not handle redirects (common in Lark/Feishu MCP endpoints)

Request
Please unify:

MCP configuration schema

MCP connection logic

UI fields between Admin Console and User Extensions

So that MCP tools behave consistently across both entry points.

Steps to Reproduce

no

Logs & Screenshots

Image Image

Additional Information

No response

Originally created by @lovesec on GitHub (Apr 16, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23782 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] 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!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.8.10 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 22.04 ### Browser (if applicable) _No response_ ### 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 Verification successful ### Actual Behavior Environment Open WebUI version: v0.8.10 (issue first observed) Admin Console version: v0.8.12 (UI differences still present) Steps to Reproduce Admin Console (works) Go to: Admin Console → Settings → Integrations Click Add Connection Select MCP Stream HTTP Fill in: Name Description URL Authentication: None Save → Connection succeeds User Extensions Page (fails) Go to: User Settings → Extensions Click Add Extension Tool Select MCP Stream HTTP Fill in the exact same values as used in Admin Console Save → Connection fails Actual Result Admin Console: MCP tool connects successfully User Extensions page: Same configuration fails to connect User cannot use MCP tools that work for the admin Expected Result Both Admin Console and User Extensions should use the same MCP connection logic A valid MCP configuration should succeed in both places UI fields and internal parameters should be consistent UI / Field Differences (Critical) Admin Console – Add/Edit Connection Fields shown: Type: MCP Stream HTTP Name ID (only visible in Edit mode) Description URL Authentication: None Advanced section Function name filter list Warning: MCP is experimental Buttons: Save / Delete User Extensions – Add Extension Tool Fields shown: Type: MCP Stream HTTP Name Description URL Authentication: No authentication No ID field No Advanced section No function filter list Button: Save Impact Users cannot use MCP tools that administrators have configured MCP tools cannot be shared across the organization Inconsistent UI suggests inconsistent backend handling Hard to debug because Admin and User flows behave differently Possible Root Causes Admin Console and User Extensions use different MCP client implementations Missing fields (ID, advanced metadata) cause User Extensions to send incomplete MCP handshake User Extensions may not follow the same HTTP streaming protocol User Extensions may not handle redirects (common in Lark/Feishu MCP endpoints) Request Please unify: MCP configuration schema MCP connection logic UI fields between Admin Console and User Extensions So that MCP tools behave consistently across both entry points. ### Steps to Reproduce no ### Logs & Screenshots <img width="1168" height="964" alt="Image" src="https://github.com/user-attachments/assets/75628728-9231-425d-9af4-ae5cf5b3eda0" /> <img width="956" height="738" alt="Image" src="https://github.com/user-attachments/assets/dcf963a7-1d14-4ebb-aa23-c5053de78c02" /> ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-25 09:46:49 -05:00
GiteaMirror commented 2026-04-25 09:46:50 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Apr 17, 2026):

User level MCP is not supported.

<!-- gh-comment-id:4264910521 --> @tjbck commented on GitHub (Apr 17, 2026): User level MCP is not supported.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#35602
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?