MCP: friendly 405 on a non-POST /mcp (browser GET explains itself) - #139
Merged
Conversation
Hitting /mcp in a browser returned a cryptic JSON-RPC parse error (-32700). A non-POST is not a JSON-RPC call; per Streamable HTTP, GET is for an SSE stream we don't offer in v1 → respond 405 (Allow: POST) with a human-readable body — name, version, protocolVersion, and how to use it (POST JSON-RPC / MCP Inspector / curl). POST behavior is unchanged. Test: GET → 405 + the info body. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hitting
/mcpin a browser returned a cryptic-32700 Parse error. A non-POST isn't a JSON-RPC call; per the Streamable HTTP transport,GETis for an SSE stream we don't offer in v1 → respond 405 (Allow: POST) with a human-readable body (name, version, protocolVersion, and how to use it: POST JSON-RPC / MCP Inspector / curl). POST behavior is unchanged.Verified on dev — a browser GET now returns the info message instead of a parse error. Test: GET → 405 + info body.
🤖 Generated with Claude Code