Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

bobshell 2.0.5: configured MCP servers never connect (createSession sees empty config; endpoint verified healthy via curl)

オープン
  • 何か問題がありますか？
#55 コメント 2 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
38/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
docker, javascript
領域
cli, tooling

調査の方向性

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}}}

  1. bob mcp list sees it: fast_time: | enabled | unknown | global.

  2. 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

  1. The same config placed at the workspace path /workspace/.bob/mcp.json changes nothing — same error.

  2. Letting bob write the file itself — bob mcp add-json fast_time '<json>' (after mkdir -p /workspace/.bob) prints Added MCP server "fast_time" to /workspace/.bob/mcp.json — and the next bob run still reports the server absent from its toolset.

  3. 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}}
  1. Side observation: bob mcp add-json crashes with ENOENT: 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
平均マージ
1時間 13分
マージ済み PR（30日）
8

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

IBM/contextforge-examples のほかの issue

IBM/contextforge-examples の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。