Repository navigation
Conversation
- 后端 web/mcp_admin.py(APIRouter /api/mcp/*):节点增删改/启停/实时探测; 变更走 gateway.sh stop → 改 openclaw.json → start(状态所有权在 gateway); 探测不碰 gateway:HTTP 直连握手(urllib 空响应自动降级 curl HTTP/2), stdio 用子进程 JSON-RPC 行协议 - 前端设置新增「MCP 节点」分类:节点卡片(tile+pill 徽章,st-env 卡片规范)、 工具清单实时展开、新增表单(HTTP/本地进程双形态)、删除确认 - 方向:MCP 工具层与 skill 插槽互补——插槽适合确定性流水线的固定参数位, MCP 适合 agent 按任务自主调用的通用能力。自有/第三方能力做成 MCP 节点 挂进来即可用,无需为每个平台写一次性插槽适配
Collaborator
|
感谢提供 MCP 节点通讯录、工具清单探测和设置界面的实现!可视化管理外部工具有价值,但我核对后认为当前实现不能直接作为通用工具层合入。 它实际只改硬编码 在临时配置和函数/进程替身上复现了三项问题:
建议借鉴通讯录和工具列表界面,后续按当前底座分别接入其支持的 MCP 配置,先做好可验证的状态、凭据展示边界和不中断活跃任务的应用流程,再讨论扩大工具能力。本轮关闭、不合并;感谢贡献。此次复查只用了合成数据,没有真实启动 MCP 节点、修改配置或重启服务。 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
方向:通用 MCP 工具层,与 skill 插槽互补
现状:Easel 对接外部能力走 skill 插槽(
.envprovider:IMG_BASE_URL/MUSIC_PROVIDER/VOICE_PROVIDER…)。每接一个新平台,都要为对应插槽写一次性适配脚本,agent 能力层与插槽耦合,自有/第三方能力的接入成本高。MCP 工具层是另一条路:能力做成 MCP 节点挂进来,agent 按任务自主调用,无需逐平台适配。两者互补——插槽适合确定性流水线的固定参数位,MCP 适合 agent 自主选择的通用能力。本 PR 落地后者的基础设施:设置里的 MCP 节点配置面板。
功能
设置新增「MCP 节点」分类:
实现要点
web/mcp_admin.py(独立 APIRouter/api/mcp/*,不改现有路由)scripts/gateway.sh stop → 改 openclaw.json → start(约 20s,串行化 asyncio.Lock,配置 tmp 原子替换)测试(自部署实例,OpenClaw 2026.11.3)
tsc -b && vite build通过(前端零类型错误)