[Client] Print contents of stderr when command in StdioTransport fails to start

Open
#332 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
php
Domain
backend

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.

Description

enhancement

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

Dominant language
PHP
Stars
1.6k
Forks
173
Avg merge
2d 49m
Merged PRs (30d)
23

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from modelcontextprotocol/php-sdk

All issues in modelcontextprotocol/php-sdk

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.