docs: static-header auth on claude.ai, and why there is no outputSchema - #64
Merged
Merged
Conversation
The README said a static bearer token cannot work on claude.ai; an org admin can now add a connector with a static header (beta, limited orgs). No tool declares an outputSchema, deliberately: the spec makes it binding, Lexware payloads are open-ended, and Claude's clients still fail on declared output schemas (anthropics/claude-ai-mcp #673, #485, #1016). The decision is recorded in shared.ts and pinned by a test.
This was referenced Sep 22, 2026
marselsel
changed the base branch from
feat/audience-resource-indicator
to
main
September 22, 2026 21:57
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.
Part 6 of 8 in the MCP best-practices stack. Stacked on #63, so merge in order.
Changes
README: it no longer says a static bearer token can't work on claude.ai. Claude's authentication docs list
static_headers: a "Fixed credential … entered by an organization administrator as a request header when adding the connector", in beta for a limited set of organizations, sent "exactly as you enter it" (so the admin typesBearer <token>). OAuth stays the recommendation wherever users sign in individually.outputSchema: deliberately not added (the finding was low priority). The spec makes a declared schema binding ("Servers MUST provide structured results that conform to this schema"), and the SDK turns any mismatch into an error result, while Lexware's payloads are open-ended. Claude's clients also still fail on declared output schemas:anyOfbreaks the connectorThe decision is recorded in
src/tools/shared.ts, where someone adding a schema would look. A test pins it until those issues are fixed. The JSON text block from feat: include structuredContent as JSON text in every tool result #62 is what makes results readable to the model instead.Verification
npm testpasses all 480 tests, including the new "declares no outputSchema" check.