Claim Context7 library and fix MCP config#3
Merged
Conversation
Claim the Context7 library: add `url` + `public_key` to context7.json. This is
the `pk_` claim key, which Context7's claim flow explicitly has you commit and
push to the default branch for ownership verification.
Make the bundled MCP config keyless in both mcp.json (Cursor) and .mcp.json
(Claude Code), and correct the README key note.
The files previously forwarded the key with `${env:CONTEXT7_API_KEY}`, which is
Cursor-only syntax. Claude Code doesn't parse the `env:` prefix — it would send
the literal `${env:CONTEXT7_API_KEY}` string as the header and warn on every
startup. The validate-plugins gate also requires the two files to be
byte-identical, which per-tool key syntax makes impossible.
Keyless is correct in both tools, satisfies the byte-identical gate, and drops
the warning. The rate-limit key (ctx7sk-, a secret, not committable) has no
effect until Context7 fetching goes live, so it's wired via env var later,
alongside the .context7-library-id flip.
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.
What
url+public_keytocontext7.json. This is thepk_claim key, which Context7's claim flow explicitly has you commit and push to the default branch for ownership verification.mcp.json(Cursor) and.mcp.json(Claude Code), and correct the README key note.Why
The MCP files forwarded the Context7 key with
${env:CONTEXT7_API_KEY}, which is Cursor-only syntax. Claude Code doesn't parse theenv:prefix — it would send the literal${env:CONTEXT7_API_KEY}string as the header and warn on every startup. Thevalidate-pluginsgate also requires the two files to be byte-identical, which per-tool key syntax makes impossible.Keyless is correct in both tools, satisfies the byte-identical gate, and drops the warning. The rate-limit key (
ctx7sk-, a secret — not committable) has no effect until Context7 fetching goes live, so it's wired via env var later, alongside the.context7-library-idflip.Validation
pnpm check:allis green: typecheck, polished schema (14 files),validate-plugins, snapshot verify (14 match).context7.jsonis valid JSON with the claim key present.Follow-up (not in this PR)
This PR lets Context7 verify ownership off
main. It does not turn on live fetching — the skill still reads from the local snapshot untiliterable-android/.context7-library-idholds the real library ID (still theTODO-PHASE-3placeholder). Flipping that ID and the source-priority wording is a separate PR once Context7 crawls the corpus.🤖 Generated with Claude Code