Update Context7 MCP documentation to use standard Authorization header #688
Conversation
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
Switch from custom CONTEXT7_API_KEY header to industry standard Authorization: Bearer format for better compatibility and clarity
|
it already works with both, i'm not sure if we should refactor everything on the readme. do you think this is an important docs update? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Authorization: Bearerheader formatCONTEXT7_API_KEYheader to OAuth 2.0 standard formatChanges
claude mcp addcommand example in README"CONTEXT7_API_KEY: YOUR_API_KEY"to"Authorization: Bearer YOUR_CONTEXT7_API_KEY"Rationale
The
Authorization: Bearerformat is the industry standard for API authentication and provides: