What it is
The standing answer to “my agent keeps coding against last year’s API.” context7 exposes two tools, Resolve Library ID and Query Documentation, that fetch current, version-pinned docs for thousands of libraries and drop them into context.
How it was vetted
Read the source at commit a9d7c77 (2026-07-10) and booted the published package
(@upstash/context7-mcp, boots clean over stdio or HTTP). The question for a
docs-fetching tool isn’t “can it write.” It holds no local access. It’s where does
my query go?
- It’s a hosted-service proxy.
searchLibrariesandfetchLibraryContextbothfetch()https://context7.com/api/v2/...with yourqueryand library name as parameters. The natural-language query is the thing you’re working on, and it goes to Upstash’s servers. Expected for a hosted docs corpus, disclosed in the code, but the single fact worth knowing before you install. - Nothing local is touched. No filesystem access, no shell, no environment scraping. The only outbound calls are to the Context7 API and standard OAuth and JWKS endpoints for the optional authenticated mode.
- No hidden telemetry. Beyond the documentation API it exists to call, there’s no analytics SDK in the dependency tree.
- Auth is optional. Runs free and keyless (rate-limited by client IP); a
CONTEXT7_API_KEYraises the limit. Nothing is required to try it.
