Skip to content

The Board's MCP tools wait for a busy board and name an unreachable one - #10

Merged
marvin-bitterlich merged 1 commit into
mainfrom
mcp-survives-busy-board
Nov 7, 2026
Merged

marvin-bitterlich merged 1 commit into
mainfrom
mcp-survives-busy-board

Conversation

@marvin-bitterlich

Copy link
Copy Markdown
Contributor

Why?

Claude sessions read the Work Board through the work-board MCP server. In Marvin's sessions the server failed with "Connection closed" and its tools stayed gone for the whole session. It looked as if the server needed the Board at startup.

That is not the cause. The server starts, lists its tools and answers each call without a Board; a story now proves it. The session is registered as npx -y @shivaedev/work-board mcp …. npm keeps one cached install for that command. When a release pins another Effect version, npm refuses to update the cached copy (ERESOLVE … Conflicting peer dependency: effect@4.0.7), and the process exits before Claude Code connects. Every session since the Board left Platform's workspace hit this, whether the Board ran or not.

A second, smaller fault was in the server itself. Each tool call waited 10 seconds. The Board may spend up to 25 seconds on its Fleet view when Fleet is busy, so a busy Board was reported as "No board answers".

How?

Launch. The README now names pnpm dlx @shivaedev/work-board mcp <dir> for clients without a global install, and says why npx -y fails. pnpm resolves into a fresh folder per version, so a new Effect pin does not break it.

Wait. A tool call now waits 30 seconds: the Board's 25-second Fleet view budget (from #9) plus 5 seconds for the Board's own index and document reads. The MCP client takes the budget from the same constant as the Fleet view, so the two cannot drift apart.

Messages. A Board that does not answer in time is reported as busy ("did not answer within 30 seconds. It may be busy; try again."). A Board that cannot be reached is reported as "not reachable", with the command that starts it.

Callouts

  • This change does not repair Marvin's machine. His user config still runs npx -y @shivaedev/work-board, and npm's stale cached copy (0.30.1) stays until someone deletes that npx cache folder or changes the command to pnpm dlx.

work-board mcp waited 10 seconds per tool call, less than the 25 seconds
the Board may spend on its Fleet view, so a busy Fleet read as a stopped
board. It now waits 30 seconds, reports a slow board as busy and an
unreachable board as not reachable. The README warns against npx -y,
whose stale cached install stops the server from starting.
@marvin-bitterlich
marvin-bitterlich added this pull request to the merge queue Nov 7, 2026
Merged via the queue into main with commit ff60bbc Nov 7, 2026
16 checks passed
@marvin-bitterlich
marvin-bitterlich deleted the mcp-survives-busy-board branch November 7, 2026 00:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant