Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

feat: mcpo documentation is dead in the water with no quick prebuilt docker path

未关闭
#627 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

  • #1289 来自 @Wenjunyun123 —— 已关闭,未合并

评估

难度
2/5
预计耗时
半天
新手友好度
35/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
技术栈
docker, docker-compose
领域
documentation

调研方向

从 docs.openwebui.com/openapi-servers/mcp/ 的 MCP 文档开始,并将其中的设置指南与 mcpo 仓库进行比较。记录一条使用 Docker 或 Docker Compose 的完整路径,包括用户在哪里配置其 MCP server,以及如何启动和停止它。完成标准是:用户可以复制配置,将其指向现有 server,运行 docker compose up,并使用 docker compose down 将其移除。

由索引模型根据 Issue 内容生成。

描述

documentation help wanted
Check Existing Issues
  • I have searched the existing issues and discussions.
Problem Description

NOTE: THIS IS A DOCUMENTATION COMPLAINT NOT A CODE COMPLAINT

Openwebui is considered far behind in the MCP category due to how it handles MCP. This is often repeated on web forums.

https://docs.openwebui.com/openapi-servers/mcp/

https://github.com/open-webui/mcpo

The MCP documentation is... very slow to figure out a solution that doesn't impact the rest of my dev machine. I don't want to build a docker container locally! If you're making all your users run pip install natively or build a docker container to use MCP, that's a bad strategy.

If I already have a MCP server working with claude code, the user would want to do a minimum to get it working with openwebui

Desired Solution you'd like
  • Update the documentation to have a single docker command/docker compose command which instantly runs the proxy. This also means no impact to the rest of the machine, as the container would be easily removed with a docker compose down command.
    • Note: the docker-compose.yml file would be the configuration file to point to the correct MCP server

This documentation makes setup easy. Make a new folder for the proxy, copy the docker-compose.yml file there and edit it to point to the correct MCP server, run docker compose up, and that's it. The user can see what proxies are running via docker ps.

Alternatives Considered

No response

Additional Context

No response

主要语言
JavaScript
星标
892
派生
630
平均合并
2 天 3 小时
30 天内合并 PR
52

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

open-webui/docs 的其他 Issue

查看 open-webui/docs 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。