How do I diagnose an MCP connection failure? #79
|
What should I check when a client gets an authentication, Origin, media-type, or method error instead of a working Bicho connection? |
Replies: 1 comment
|
First check the destination. Your installation's For an installation connection, requests need The status narrows the problem:
Clients without Check proxy header forwarding and avoid interactive browser challenges on the route. A 202 notification response with no body can be normal, not a missing tool result. |
First check the destination. Your installation's
/mcpis the authenticated investigation endpoint;https://bicho.fyi/mcpserves public documentation only. Use a Streamable HTTP client that initializes the protocol and can send a custom bearer header. Bicho does not implement OAuth.For an installation connection, requests need
Authorization: Bearer <admin-token>,Content-Type: application/json, andAccept: application/json, text/event-stream. BothAcceptmedia types are required even though responses use JSON. Let the MCP transport negotiate the protocol-version header.The status narrows the problem: