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

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

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

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

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
68/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
typescript
領域
ai-infra-agents, backend

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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

主要言語
TypeScript
スター
3
フォーク
0
平均マージ
17時間 33分
マージ済み PR（30日）
163

環境構築

はじめの一歩

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

musterhq/muster-code のほかの issue

musterhq/muster-code の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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