You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Repo-scoped tools fail with -32020 "missing Mcp-Param-owner header" in claude.ai chats; the same calls work from Claude Code #3917
In a claude.ai chat using the GitHub connector (the hosted remote server), every tool that takes owner and repo fails with -32020 header mismatch: missing Mcp-Param-owner header. Tools without those parameters work in the same chat. The same connector, signed in as the same account, answers the repo-scoped calls in Claude Code (the desktop app's Code tab).
This looks like the error in #3311, which was closed on 2026-10-02.
Affected version
The hosted remote server, used as a claude.ai connector on 2026-11-21. I can't see its version or which protocol version the claude.ai client negotiates.
Steps to reproduce the behavior
In a claude.ai chat with the GitHub connector enabled and no repositories attached:
get_me: works.
search_repositories with user:<login> fork:true: works (same total_count as in Claude Code).
list_commits on a public repository of another owner, with sha set to a branch: fails.
get_file_contents failed with the same error.
Expected vs actual behavior
Expected: step 3 returns the commits, as the same call does from Claude Code.
Actual: step 3 returns
The MCP server returned HTTP 400 for this tool call. Server error detail: header mismatch: missing Mcp-Param-owner header for parameter "owner" (error code -32020)
The tool schemas mark owner and repo with x-mcp-header. I don't know whether the claude.ai client should be sending the projected headers for the protocol version it negotiates, or whether the server should accept the parameters from the body for that version, as #3311 describes.
Logs
None beyond the error above; the chat shows only the tool results.
Checked against main at 9a72d8d (2026-11-20). I could not find a repo-side path that produces this error for a client on 2025-11-25, so the useful next step is the failing request's headers rather than a server change.
What the code does
The -32020 text comes from go-sdk v1.8.0 mcp/streamable_headers.go. validateMcpHeaders returns early when Mcp-Protocol-Version is absent or below 2026-07-28; from that version on it requires Mcp-Method, Mcp-Name, and a matching Mcp-Param-* header for every present annotated argument. docs/streamable-http.md documents the same contract, and pkg/inventory/header_params_test.go exercises the real Streamable HTTP handler with owner/repo only in the JSON body:
env -u PYTHONPATH go test ./pkg/inventory -run 'TestTypedHeaderParamsHTTP/typed=false/inventory' -count=1 -v
At 2025-11-25 the missing-headers case is accepted. At 2026-07-28 the same body is rejected with HTTP 400 and code -32020, which is the assertion that guard is written for.
What that means for this report
A -32020 from the hosted endpoint means the tools/call carried Mcp-Protocol-Version: 2026-07-28 or later and did not carry Mcp-Param-owner and Mcp-Param-repo. That is the client half of SEP-2243: on a 2026-07-28 session the client mirrors arguments annotated with x-mcp-header into those headers. The claude.ai connector does negotiate that era. Public traces of it show clientInfo=Anthropic/ClaudeAI/1.0.0 with proto=2026-07-28 (anthropics/claude-ai-mcp#1027), and the same calls succeeding in Claude Code is consistent with that client projecting the headers.
Why I did not send a patch
The annotation is deliberate and load bearing. pkg/github/header_params_test.go requires every tool with owner or repo to project it so the remote proxy never falls back to re-parsing the body, and #3454 restored the corresponding validation on purpose. Accepting absent headers at 2026-07-28 would change the documented transport contract and drop the routing and attribution check for every client, not only this one. #3854 is a different case: the tools it exempts are only reachable from MCP App views, which have no API to set request headers.
Suggested next step
Capture one failing tools/call from claude.ai, including all request headers.
If it shows Mcp-Protocol-Version: 2026-07-28 with Mcp-Method and Mcp-Name but no Mcp-Param-owner, the gap is in the connector's SEP-2243 mirroring. Either project the annotated arguments or negotiate 2025-11-25, which this server also serves. That belongs with the connector, not in this repository.
If it shows 2025-11-25 and still returns 400, then the served build diverges from main, since current main cannot produce that response on a legacy session, and the server version or proxy in front of it is the thing to inspect.
Until then, the same calls work through Claude Code, or through a local or self-hosted server placed behind a proxy that adds the two headers.
Activity
Shanmukh-l33t commentedon Nov 22, 2026
Checked against
mainat9a72d8d(2026-11-20). I could not find a repo-side path that produces this error for a client on2025-11-25, so the useful next step is the failing request's headers rather than a server change.What the code does
The
-32020text comes from go-sdk v1.8.0mcp/streamable_headers.go.validateMcpHeadersreturns early whenMcp-Protocol-Versionis absent or below2026-07-28; from that version on it requiresMcp-Method,Mcp-Name, and a matchingMcp-Param-*header for every present annotated argument.docs/streamable-http.mddocuments the same contract, andpkg/inventory/header_params_test.goexercises the real Streamable HTTP handler withowner/repoonly in the JSON body:At
2025-11-25the missing-headers case is accepted. At2026-07-28the same body is rejected with HTTP 400 and code-32020, which is the assertion that guard is written for.What that means for this report
A
-32020from the hosted endpoint means thetools/callcarriedMcp-Protocol-Version: 2026-07-28or later and did not carryMcp-Param-ownerandMcp-Param-repo. That is the client half of SEP-2243: on a2026-07-28session the client mirrors arguments annotated withx-mcp-headerinto those headers. The claude.ai connector does negotiate that era. Public traces of it showclientInfo=Anthropic/ClaudeAI/1.0.0withproto=2026-07-28(anthropics/claude-ai-mcp#1027), and the same calls succeeding in Claude Code is consistent with that client projecting the headers.Why I did not send a patch
The annotation is deliberate and load bearing.
pkg/github/header_params_test.gorequires every tool withownerorrepoto project it so the remote proxy never falls back to re-parsing the body, and #3454 restored the corresponding validation on purpose. Accepting absent headers at2026-07-28would change the documented transport contract and drop the routing and attribution check for every client, not only this one. #3854 is a different case: the tools it exempts are only reachable from MCP App views, which have no API to set request headers.Suggested next step
Capture one failing
tools/callfrom claude.ai, including all request headers.Mcp-Protocol-Version: 2026-07-28withMcp-MethodandMcp-Namebut noMcp-Param-owner, the gap is in the connector's SEP-2243 mirroring. Either project the annotated arguments or negotiate2025-11-25, which this server also serves. That belongs with the connector, not in this repository.2025-11-25and still returns400, then the served build diverges frommain, since currentmaincannot produce that response on a legacy session, and the server version or proxy in front of it is the thing to inspect.Until then, the same calls work through Claude Code, or through a local or self-hosted server placed behind a proxy that adds the two headers.
Related: #3311, #3834, #3854.