open-webui/mcpo
1
0
Fork 0
mirror of https://github.com/open-webui/mcpo.git synced 2026-11-05 01:27:39 +00:00
Code Issues 57 Projects Packages Wiki Activity

[GH-ISSUE #1] feat: mcp config JSON argument #2

New issue
Closed
opened 2026-10-18 21:10:04 +00:00 by bsakaguchi · 6 comments
bsakaguchi commented 2026-10-18 21:10:04 +00:00
Owner
Copy link

Originally created by @Nick-PDS on GitHub (Mar 30, 2025).
Original GitHub issue: https://github.com/open-webui/mcpo/issues/1

This is something I’m really looking forward to integrating in the next version of open webui

If running multiple MCP servers I assume you have to open all these servers on different port. Why not support a standard mcp config file, so all your mcps run on the same openapi router?

Originally created by @Nick-PDS on GitHub (Mar 30, 2025). Original GitHub issue: https://github.com/open-webui/mcpo/issues/1 This is something I’m really looking forward to integrating in the next version of open webui If running multiple MCP servers I assume you have to open all these servers on different port. Why not support a standard mcp config file, so all your mcps run on the same openapi router?
bsakaguchi commented 2026-10-18 21:10:05 +00:00
Author
Owner
Copy link

@lowlyocean commented on GitHub (Mar 30, 2025):

@Nick-PDS For this particular use case, would you be able to put all your MCP servers behind something like mcp-proxy-server and then just have mcpo point to that?

The tool protocol ecosystem seems littered with proxies (and MCP not being natively supported by Open-WebUI slightly worsens that), but I think there are enough of these little tools available that can be daisy-chained to get things working

<!-- gh-comment-id:2764735973 --> @lowlyocean commented on GitHub (Mar 30, 2025): @Nick-PDS For this particular use case, would you be able to put all your MCP servers behind something like [mcp-proxy-server](https://github.com/adamwattis/mcp-proxy-server/) and then just have mcpo point to that? The tool protocol ecosystem seems littered with proxies (and MCP not being natively supported by Open-WebUI slightly worsens that), but I think there are enough of these little tools available that can be daisy-chained to get things working
bsakaguchi commented 2026-10-18 21:10:05 +00:00
Author
Owner
Copy link

@MillionthOdin16 commented on GitHub (Mar 30, 2025):

I was just thinking the same thing about the MCP config file compatibility

<!-- gh-comment-id:2764773394 --> @MillionthOdin16 commented on GitHub (Mar 30, 2025): I was just thinking the same thing about the MCP config file compatibility
bsakaguchi commented 2026-10-18 21:10:05 +00:00
Author
Owner
Copy link

@tjbck commented on GitHub (Mar 31, 2025):

How about uvx mcpo --port 8000 --config /path/to/config.json?

<!-- gh-comment-id:2764820057 --> @tjbck commented on GitHub (Mar 31, 2025): How about `uvx mcpo --port 8000 --config /path/to/config.json`?
bsakaguchi commented 2026-10-18 21:10:06 +00:00
Author
Owner
Copy link

@Nick-PDS commented on GitHub (Mar 31, 2025):

@Nick-PDS For this particular use case, would you be able to put all your MCP servers behind something like mcp-proxy-server and then just have mcpo point to that?

The tool protocol ecosystem seems littered with proxies (and MCP not being natively supported by Open-WebUI slightly worsens that), but I think there are enough of these little tools available that can be daisy-chained to get things working

How about uvx mcpo --port 8000 --config /path/to/config.json?

Having it built into the tool itself would definitely be a better out of the box solution. But honestly @lowlyocean repo suggestion wouldn’t be a bad solution but I’m not sure of the compatibility issues if there are any.

<!-- gh-comment-id:2764830244 --> @Nick-PDS commented on GitHub (Mar 31, 2025): > [@Nick-PDS](https://github.com/Nick-PDS) For this particular use case, would you be able to put all your MCP servers behind something like [mcp-proxy-server](https://github.com/adamwattis/mcp-proxy-server/) and then just have mcpo point to that? > > The tool protocol ecosystem seems littered with proxies (and MCP not being natively supported by Open-WebUI slightly worsens that), but I think there are enough of these little tools available that can be daisy-chained to get things working > How about `uvx mcpo --port 8000 --config /path/to/config.json`? Having it built into the tool itself would definitely be a better out of the box solution. But honestly @lowlyocean repo suggestion wouldn’t be a bad solution but I’m not sure of the compatibility issues if there are any.
bsakaguchi commented 2026-10-18 21:10:06 +00:00
Author
Owner
Copy link

@tjbck commented on GitHub (Mar 31, 2025):

Addressed with 82af7f7f36

<!-- gh-comment-id:2765008187 --> @tjbck commented on GitHub (Mar 31, 2025): Addressed with 82af7f7f366db54b06ddf64c20700a989224e189
bsakaguchi commented 2026-10-18 21:10:06 +00:00
Author
Owner
Copy link

@MillionthOdin16 commented on GitHub (Mar 31, 2025):

Awesome 🔥

<!-- gh-comment-id:2766959482 --> @MillionthOdin16 commented on GitHub (Mar 31, 2025): Awesome 🔥
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issues/239
issues_cleanup
dev
issues/240
multi_user_oauth
oauth_support
fix-hot-reload-symlink
raise_and_alias
changelog_readme
issues/197
streamable_http-streamable-http
v0.0.20
v0.0.19
v0.0.18
v0.0.17
v0.0.16
v0.0.15
v0.0.14
v0.0.13
v0.0.12
v0.0.11
v0.0.10
v0.0.9
v0.0.8
v0.0.7
v0.0.6
Labels
Clear labels   
bug

   
can't reproduce

   
documentation

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
pull-request
Mirrored from GitHub Pull Request

  
question
No labels
bug
can't reproduce
documentation
enhancement
good first issue
help wanted
invalid
pull-request
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
open-webui/mcpo#2
No description provided.