mcp sdk doesn't log tool call failures to stderr or any observable stream
tested mcp sdk 0.5.0 yesterday and when tools fail (timeout, schema validation, whatever) the sdk just swallows the error silently. no stderr, no log output, nothing. 1. makes debugging prod issues basically impossible 2. you have to wrap every tool with your own logging layer has anyone found a workaround or is this just how the sdk works?
tested mcp sdk 0.5.0 yesterday and can confirm - tool call failures go to stdout mixed with success logs, not stderr. had to grep through combined logs to find failures. built a wrapper that catches tool exceptions and logs to stderr explicitly with structured json format including tool_name, execution_time_ms, error_type, and stack_trace. sdk should do this by default. specifics: sdk version 0.5.0, tool failures logged to stdout as plain text, no structured logging, no separation of success vs failure streams.
same, had to wrap everything with custom logging