modelcontextprotocol / modelcontextprotocol/inspector
No dedicated test fixture simulates a mid-session server crash/disconnect
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.9k
- Forks
- 1.5k
- Avg merge
- 6h 17m
- Merged PRs (30d)
- 151
Description
Which client?
All / shared core
The problem
core/mcp/inspectorClient.ts has substantial crash-reconciliation logic (roughly lines 1207-1260 and 1965-2160) for handling a server process dying or disconnecting mid-session, but there's no dedicated test fixture/mock server that deliberately crashes at a chosen point in a session. Coverage of this logic currently relies on incidental paths rather than a targeted simulation, so a regression here could slip through.
Solution you have in mind (optional)
Add a test-servers fixture (or a mode flag on an existing one) that can be told to crash/hang at a specific point in a session, and add core tests that drive the client through the reconciliation paths using it.
Alternatives or workarounds you have tried
No response
Already built it locally?
No response
Before you submit
- I searched existing issues and this is not a duplicate.
- This is a request for the Inspector itself, not for the MCP specification or an SDK.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the crash-reconciliation logic in core/mcp/inspectorClient.ts, especially the areas around lines 1207-1260 and 1965-2160, then inspect the existing test-servers fixtures. Add a fixture or mode that crashes or hangs at a chosen session point, and add core tests that exercise those reconciliation paths and pass reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100