MCP servers imported from ~/.claude.json, ~/.codex/config.toml or .mcp.json fail to start in chats (missing launcher, ENOENT)

Abierto
  • ¿Algo no está bien?
#766 0 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
ai-infra-agents, backend

Línea de trabajo

Start in packages/agent-app/src/runtime/domains/mcp.ts, especially syncDetected() and the thread-config builder around line 304; compare them with the add and update handlers that call writeLauncher(). Trace how detected entries are stored and how launcher scripts are generated, then check that new and changed stdio servers with arguments use launchers matching their current settings. Done when the acceptance cases work for Claude Code, Codex, and folder .mcp.json sources.

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

Descripción

Problem

MCP servers that Muster detects from ~/.claude.json, ~/.codex/config.toml or a folder's .mcp.json fail to start in a chat when they are stdio servers with arguments, which covers almost every npx … or uvx … server. The agent reports them as failed with ENOENT (Claude Code, for example, shows posix_spawn '…/mcp-launchers/<id>.sh'). Settings › MCP servers still shows the same servers as healthy, because its own test starts the command directly.

Turning a server off and on in Settings makes it work, because that writes its launcher. The bug comes back for any server detected later.

Cause

In packages/agent-app/src/runtime/domains/mcp.ts:

  • The thread config points every stdio server with arguments at its launcher script, <dataDir>/mcp-launchers/<id>.sh (line 304): 
    configOverrides[`${key}.command`] = entry.args.length ? launcher(entry.id) : entry.command;
  • Only the add and update handlers call writeLauncher() (lines 332 and 340).
  • syncDetected() (line 123) stores detected servers but never writes their launcher. A new detected server therefore has no script. A detected server whose command or arguments change keeps a stale script that still runs the old command.

Expected

  • Every stdio server with arguments that is handed to an agent has a launcher matching its current command and arguments, whatever its source (Settings, ~/.claude.json, ~/.codex/config.toml, .mcp.json).
  • For example, syncDetected() could call writeLauncher() for new or changed entries, or the thread-config builder could write the launcher when it is missing or out of date before it uses the path.

Acceptance

  1. With a fresh data folder and a stdio server with arguments in ~/.claude.json (e.g. npx -y @modelcontextprotocol/server-memory), a new Claude Code chat lists the server as connected and can call its tools, without anyone opening Settings.
  2. The same works for a server in ~/.codex/config.toml in a Codex chat, and for one in a folder's .mcp.json.
  3. Changing a detected server's arguments in its source file makes the next chat start it with the new arguments.

Seen on Muster Agent 0.3.14 and 0.3.15 (Linux, Arch) and still present on main (b2c9d8836).

Lenguaje dominante
TypeScript
Estrellas
3
Forks
0
Merge medio
17 h 33 min
PR fusionados (30 d)
163

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 musterhq/muster-code

Todos los issues de musterhq/muster-code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.