Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
  • ¿Algo no está bien?
#55 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
docker, javascript
Área
cli, tooling

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
1
Forks
2
Merge medio
19 h 52 min
PR fusionados (30 d)
11

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de IBM/contextforge-examples

Todos los issues de IBM/contextforge-examples

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.