[Client] StdioTransport hangs after successful initialize on Windows (fwrite EINVAL on the second request)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 47/100
Línea de trabajo
Start with the client-side Mcp\Client\Transport\StdioTransport write path and how it handles child stdin on Windows; the issue provides a minimal client and server repro. Run the repro on Windows and trace why the second request fails with fwrite EINVAL while the first succeeds. Done means listTools() returns the advertised tool or fails promptly with a catchable exception.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Environment
- OS: Windows 11 (10.0.26200), x64
- PHP: 8.4.27 (CLI, NTS)
- mcp/sdk: 0.9.0
- Server: built with the same SDK (0.9.0), served over
Mcp\Server\Transport\StdioTransport - Triggered both directly via
Mcp\Client\Builderand throughsymfony/mcp-bundle1.0.0-BETA1
Description
On Windows, the client-side Mcp\Client\Transport\StdioTransport hangs after a successful
initialize handshake. The first request (initialize/discover) is written and answered fine; the
second request (tools/list) fails to write to the child's stdin and the call never returns.
Observed directly with the SDK client:
[info] Protocol connected to transport {"transport":"Mcp\\Client\\Transport\\StdioTransport"}
[info] Started MCP server process {"command":"php \"...\""}
[debug] Sending request {"id":1,"method":"server\/discover"}
[debug] Sent message to server {...}
[debug] Suspending fiber for response {"id":1}
[info] Client connected and initialized ← handshake OK
[debug] Sending request ← tools/list
[debug] Notice: fwrite(): Write of 270 bytes failed with errno=22 Invalid argument
[error] Failed to list the tools of MCP server "coroner", it contributes none for the next 60 seconds.
php client.php (repro below) then hangs indefinitely (> 5 minutes, no return, no exception —
had to kill the process). conn->listTools() never comes back.
Minimal repro
composer.json:
{
"require": {
"mcp/sdk": "^0.9.0",
"symfony/finder": "^8.0",
"psr/log": "^3.0"
}
}
server.php — a one-tool server, same SDK:
<?php
require __DIR__.'/vendor/autoload.php';
use Mcp\Server;
use Mcp\Server\Capability\Attribute\McpTool;
use Mcp\Server\Transport\StdioTransport;
class PingTools
{
#[McpTool(name: 'ping', description: 'Returns pong')]
public function ping(): string
{
return 'pong';
}
}
exit(
\Mcp\Server::builder()
->setServerInfo('ping-server', '0.0.1')
->setDiscovery(__DIR__, ['.'], excludeDirs: ['vendor'])
->build()
->run(new StdioTransport())
);
client.php:
<?php
require __DIR__.'/vendor/autoload.php';
use Mcp\Client\Builder;
use Mcp\Client\Transport\StdioTransport;
$client = (new Builder())->build();
$conn = $client->connect(new StdioTransport(
command: 'php',
args: [__DIR__.'/server.php'],
cwd: __DIR__,
));
$tools = $conn->listTools(); // ← hangs here on Windows
echo 'TOOLS: '.count($tools)."\n";
$result = $conn->callTool('ping', []);
echo 'ping: '.json_encode($result->content)."\n";
$client->disconnect();
php client.php → prints nothing after connect, hangs forever.
What I ruled out
- Not the protocol era: pinning the client to
2025-11-25changes nothing; the same failure
happens when the client negotiates the modern era (2026-07-28). - Not the server: the same server process responds correctly to a hand-rolled
proc_openclient (write JSON lines, blockingfgets) — initialize,notifications/initialized,
tools/list,tools/callall work, repeatedly, over many writes. - Not HTTP: the same server exposed over the bundle's HTTP transport works flawlessly with
the SDK's HTTP client.
Two additional observations that may help:
- The failing write is always the second one; the first (initialize/discover) succeeds.
- When the parent process is started from Git Bash, the spawned child additionally fails to
resolvephpat all ('php' is not recognized as an internal or external commandin the
child's stderr — POSIX-stylePATHnot survivingproc_openon Windows), which surfaces as
connection retries. That one is likely an environment quirk rather than an SDK bug, but it
makes the client's failure mode hard to diagnose: the child's stderr only shows up at debug
log level, while the user-facing error is a generic "Failed to list the tools …".
Expected behavior
listTools() returns the advertised tools on Windows, exactly like on Linux/macOS — or at the
very least fails fast with a catchable exception instead of hanging.
Workaround we ship
Serve over HTTP instead of STDIO for the bundled client (works perfectly on Windows):
transports: { http: true } + client transport: http.
- Lenguaje dominante
- PHP
- Estrellas
- 1.7k
- Forks
- 206
- Merge medio
- 1 d 19 h
- PR fusionados (30 d)
- 100
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de modelcontextprotocol/php-sdk
-
[Client] `Builder::addRequestHandler()` rejects the SDK's own handlers under PHPStanPosiblemente ocupada @xixi-box la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
modelcontextprotocol/php-sdk#768 ·
Los mantenedores suelen responder en 1 día
-
[Server] Handler type uses bare Closure, hard to decorate RegistryInterface under strict PHPStanAbiertoServer
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
modelcontextprotocol/php-sdk#468 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
[Client] `callTool()` cannot defer `input_required` or send a later retry (MRTR)Posiblemente ocupada @xixi-box la tomó hoy. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 30/100
modelcontextprotocol/php-sdk#767 ·
Los mantenedores suelen responder en 1 día
-
[Server] Answer arguments the input schema refuses with an `isError` result from revision 2025-11-25 onPosiblemente ocupada @falisco la tomó hoy. Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 25/100
modelcontextprotocol/php-sdk#763 ·
Los mantenedores suelen responder en 1 día
-
[Server] A `float $x = INF` default makes `tools/list` fail for all toolsPosiblemente ocupada @andre-schade la tomó hace 2 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 25/100
modelcontextprotocol/php-sdk#756 ·
Los mantenedores suelen responder en 1 día
Todos los issues de modelcontextprotocol/php-sdk
Issues similares
-
Change: check an identifier filter the same way in every tool - the order of somcp_search_ordersAbiertoconsistency enhancement Orders
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
novalo-dev/Prestashop-MCP-Server#343 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
claude
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
sprain/sprainocchio#45 ·
Los mantenedores suelen responder en 1 día
-
sync-en
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
sync-en
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día