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

未关闭
  • 哪里不对？
#766 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
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 分钟
30 天内合并 PR
163

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

musterhq/muster-code 的其他 Issue

查看 musterhq/muster-code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。