Skip to content

fix: follow-ups to server/discover serving - #463

Merged
gmegidish merged 1 commit into
mainfrom
fix/mcp-serving-followups
Oct 1, 2026
Merged

gmegidish merged 1 commit into
mainfrom
fix/mcp-serving-followups

Conversation

@gmegidish

Copy link
Copy Markdown
Member

Follow-ups to #451.

  • mount /mcp on POST only, so the GET/DELETE 405 routes below it are reachable again (behind app.all they were dead code)
  • pass onerror to serveStdio too: the factory runs lazily on the first message, so a throwing createMcpServer() was answered with a silent -32603 instead of being logged
  • run the legacy initialize and tools/list tests through createMcpHandler, the entry production uses, instead of InMemoryTransport

Test plan

  • npm run build, npm run lint
  • npx playwright test test/server-discover.test.ts (3 passed)
  • built server: GET/DELETE /mcp → 405, legacy tools/list → 200, server/discover → 200

- mount /mcp on POST only so the GET/DELETE 405 routes are reachable again
- pass onerror to serveStdio so a failing factory is logged, not swallowed
- run the legacy initialize and tools/list tests through createMcpHandler
@gmegidish
gmegidish merged commit 2d5c1fa into main Oct 1, 2026
7 checks passed
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