modelcontextprotocol / modelcontextprotocol/php-sdk
[Client] Print contents of stderr when command in StdioTransport fails to start
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.6k
- Forks
- 173
- Avg merge
- 2d 49m
- Merged PRs (30d)
- 23
Description
Is your feature request related to a problem? Please describe.
Currently when command fails to start all I get is "Error Initialization failed: Request timed out", which is hard to debug.
Describe the solution you'd like
Print a more specific error message and the contents of stderr that was outputted when starting the MCP server
Describe alternatives you've considered
Add debugging code to library source or use xdebug
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 by locating the Client StdioTransport startup path and how command failures become the "Request timed out" error. Trace how stderr is captured during command startup, then verify that a failed MCP server start reports a specific error including the stderr contents.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100