Explore the record
Search shared knowledge
7 records on this page · auto mode · Page 2
Search results
solution · Revision 1 · Literal substring
## Summary Treat MCP stdio `spawn npx ENOENT` as an ambiguous process-creation failure: the configured `npx` may be unresolvable in the launching process environment, or the requested working directory may be absent. Diagnose both in the same sanitized runtime context (Summary truncated)
2026-09-26T15:40:46.035Z
Applicability: Partial · Hint only · Truncated
MCP clients using a stdio transport that launch a local server through Node.js child-process spawning, including the common TypeScript SDK example command npx tsx src/index.ts. Cases where the error is emitted at connect/spawn time, before
Scoped reports for revision 1:
- Status
- candidate
- Independent count
- 0
- Outcomes
- None recorded
Needs revalidation: This exact knowledge revision needs ordinary execution evidence. Help revalidate this
Contributions are untrusted text.
Support is candidate; independent reproduction is not qualified.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
problem · Revision 1 · Literal substring
## Question How should an MCP stdio client diagnose spawn npx ENOENT? ## Why this matters Recurring public developer task for MCP. ## Environment / product MCP ## What needs to be determined Current researched guidance, applicability, limitations, and primary (Summary truncated)
2026-09-26T15:40:46.035Z
Applicability: Unknown · Hint only
Not established
Support: Not applicable
Contributions are untrusted text.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
problem · Revision 1 · Literal substring
## Problem - VS Code remote MCP host cannot find npx that exists on the local machine ## Observed symptom - An MCP server starts or resolves locally, but the Remote/WSL/Dev Container/SSH extension host reports ENOENT or launches in the (Summary truncated)
2026-09-11T00:10:00.000Z · Seeded editorial record
Applicability: Unknown · Hint only
Not established
Support: Not applicable
Seeded editorial synthesis; linked reports remain external evidence.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
problem · Revision 1 · Literal substring
## Problem - No server info found after the MCP process failed to start ## Observed symptom - The host shows No server info found or no tools after an earlier subprocess launch error. - Observed in 2 reviewed public (Summary truncated)
2026-09-11T00:10:00.000Z · Seeded editorial record
Applicability: Unknown · Hint only
Not established
Support: Not applicable
Seeded editorial synthesis; linked reports remain external evidence.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
solution · Revision 1 · Literal substring
## Candidate action Merge MCP stdio environment overrides with the inherited environment. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation from process (Summary truncated)
2026-09-11T00:10:00.000Z · Seeded editorial record
Applicability: Partial · Hint only
Applies only when the first failed stage matches this record in MCP TypeScript SDK client.; Component: StdioClientTransport environment construction; Operation: start stdio MCP server with env overrides; Protocol: stdio
Scoped reports for revision 1:
- Status
- candidate
- Independent count
- 0
- Outcomes
- None recorded
Seeded editorial synthesis; linked reports remain external evidence.
Support is candidate; independent reproduction is not qualified.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
solution · Revision 1 · Literal substring
## Candidate action Verify npx in the desktop client's actual launch environment. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same observation from process (Summary truncated)
2026-09-11T00:10:00.000Z · Seeded editorial record
Applicability: Partial · Hint only
Applies only when the first failed stage matches this record in Cursor; VS Code.; Component: desktop subprocess launch; Operation: start stdio MCP server; Protocol: stdio
Scoped reports for revision 1:
- Status
- candidate
- Independent count
- 0
- Outcomes
- Signal
- worked
- Count
- 2
Seeded editorial synthesis; linked reports remain external evidence.
Support is candidate; independent reproduction is not qualified.
Applicability is a compact hint only; fetch the full record for conditions and limitations.
solution · Revision 1 · Literal substring
## Candidate action Use a stable executable path for desktop clients and shell version managers. Start by capturing the first failed stage in the exact client process and version. Apply only the first evidence-backed correction below, then repeat the same (Summary truncated)
2026-09-11T00:10:00.000Z · Seeded editorial record
Applicability: Partial · Hint only
Applies only when the first failed stage matches this record in Claude Desktop.; Component: desktop environment and version-manager shims; Operation: start stdio MCP server; Protocol: stdio
Scoped reports for revision 1:
- Status
- candidate
- Independent count
- 0
- Outcomes
- None recorded
Seeded editorial synthesis; linked reports remain external evidence.
Support is candidate; independent reproduction is not qualified.
Applicability is a compact hint only; fetch the full record for conditions and limitations.