bobshell 2.0.5: configured MCP servers never connect (createSession sees empty config; endpoint verified healthy via curl)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 38/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- docker, javascript
调研方向
Start from the stack in ~/.bob/logs/shell/bob-shell-*.log: createSession in dist/bob.js (around the reported line) versus bob mcp list / bob mcp add-json, which already see ~/.bob/settings/mcp.json and /workspace/.bob/mcp.json. Trace how workspace startupForWorkspace / startAllSessions loads config.mcpServers versus the listing registry. Done when a server listed as enabled actually starts a session (or docs/examples only advertise the one path 2.0.5 supports). Also note add-json ENOENT if /workspace/.bob is missing.
由索引模型根据 Issue 内容生成。
描述
Summary
Bob Shell 2.0.5 never connects configured MCP servers in bob chat or bob run: the session layer's createSession reports Server '<name>' not found in config even though the configuration is present, valid, and visible to bob mcp list. The server itself is healthy — a plain curl MCP handshake from inside the same container, with the same URL and key from the same config file, completes initialize, tools/list, and tools/call successfully.
Evidence
Config installed by the bobshell entrypoint at ~/.bob/settings/mcp.json (user-global, exactly as the bobshell example documents):
{"mcpServers": {"fast_time": {"httpURL": "http://host.docker.internal:8080/servers/<id>/mcp/", "headers": {"Authorization": "Bearer <key>"}, "disabled": false}}}
-
bob mcp listsees it:fast_time: | enabled | unknown | global. -
Every session attempt fails (from
~/.bob/logs/shell/bob-shell-*.log):
debug [workspace][fast_time] Starting session (serverKey: /opt/app-root/src/.bob/settings/mcp.json::fast_time)
error [workspace][fast_time] Session failed to start — Server 'fast_time' not found in config
at bAr.createSession (dist/bob.js:515:18139) … startServerSession … startAllSessions … startupForWorkspace
info [workspace][fast_time] Scheduling reconnect attempt (max 3) → gives up
-
The same config placed at the workspace path
/workspace/.bob/mcp.jsonchanges nothing — same error. -
Letting bob write the file itself —
bob mcp add-json fast_time '<json>'(aftermkdir -p /workspace/.bob) printsAdded MCP server "fast_time" to /workspace/.bob/mcp.json— and the nextbob runstill reports the server absent from its toolset. -
The endpoint is healthy from inside the same container, same URL, same key (curl):
POST initialize → HTTP 200, mcp-session-id returned
POST tools/list → all 8 fast-time tools
POST tools/call → {"result":{"content":[{"text":"curl-ping"}],"isError":false}}
- Side observation:
bob mcp add-jsoncrashes withENOENT: open '/workspace/.bob/mcp.json'when the directory does not exist, instead of creating it.
Interpretation
Two config systems disagree inside 2.0.5: the listing/registry layer reads the mcp.json files (hence bob mcp list works and the serverKey carries the file path), but the workspace session hub passes an empty or different config.mcpServers into createSession, so no configured server can ever start. Both the documented user-global location (~/.bob/settings/mcp.json, the one the bobshell container example installs) and the workspace location were tried.
Environment
- Image:
ghcr.io/ibm/cfex-bobshell:latest(digest sha256:08dfb398…, created 2026-10-05); also reproduced on a fresh local Containerfile build resolving the same version - bob 2.0.5, commit 2dc180906
- Remote MCP server: streamable HTTP, no OAuth
Ask
MCP servers configured in either documented location should connect. If only one location is supported in 2.0.5, the bobshell example and the in-CLI docs need to match it.
- 主要语言
- Python
- 星标
- 1
- 派生
- 2
- 平均合并
- 19 小时 52 分钟
- 30 天内合并 PR
- 11
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
IBM/contextforge-examples 的其他 Issue
-
难度 2/5 半天 新手友好度 78/100
IBM/contextforge-examples#29 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 55/100
IBM/contextforge-examples#37 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 72/100
IBM/contextforge-examples#38 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 72/100
IBM/contextforge-examples#32 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 68/100
IBM/contextforge-examples#33 ·
维护者通常 1 天内回复
查看 IBM/contextforge-examples 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
anchore/grype-db#1149 · 1 条评论 ·
维护者通常 1 天内回复
-
[Bug]: `hermes plugins update` clones an entire monorepo twice - `subdir` is resolved but dropped at both catalog-update call sites可能已有人在做 @HootRock 今天认领。 未关闭comp/cli P2 type/perf
难度 2/5 1-3 小时 新手友好度 72/100
NousResearch/hermes-agent#142417 · 2 条评论 ·
维护者通常 1 天内回复
-
SMC SPEC
难度 2/5 1-3 小时 新手友好度 70/100
tenstorrent/tt-oca-harness#3287 ·
维护者通常 1 天内回复
-
bug enhancement python
难度 2/5 1-3 小时 新手友好度 85/100
DewaldOosthuizen/tech-cheat-sheets-and-notes#392 ·
维护者通常 1 天内回复
-
security
难度 2/5 1-3 小时 新手友好度 72/100
fabriziosalmi/wildbox#801 ·
维护者通常 1 天内回复