Repository navigation
Error : No handler registered for notification method: notifications/stderr #377
Description
When I connect to the MCP server, I often encounter this error: "No handler registered for notification method: notifications/stderr". After investigating, I found that the registration of notification handlers is in the constructor of the McpAsyncClient class, but there is no handler registered for notifications/stderr.
Is this intentionally left unhandled, or is it a feature still under development? Could you provide more insights into the related design rationale?
Activity
feat: add ignorable JSON-RPC methods support for both client and server
chemicL commentedon Feb 19, 2026
Such notification is not part of the MCP Specification as far as I can tell. I see there was an attempt to silence unknown requests/notifications, see the discussion in #417 (comment).
Can you elaborate more what are your expectations for such non-standard notifications?
Kehrlann commentedon Jun 25, 2026
Closing due to inactivity.