@upstash/context7-mcp@4.0.3
Clients now validate authorization responses against the OAuth issuer that Clerk returns, improving OAuth flow correctness.
Context7
Up-to-date code documentation for LLMs and AI code editors, delivered via MCP
$
npx @buildinternet/releases get context7Mon
Wed
Fri
AugSepOctNovDecJanFebMarAprMayJunJulAug
LessMore
Releases31Avg Interval3dAvg Cadence10/mo
@upstash/context7-opencode@0.1.0
New @upstash/context7-opencode package registers the hosted Context7 MCP server and the context7-mcp skill. Authentication defaults to OAuth, falling back to CONTEXT7_API_KEY or an apiKey plugin option.
@upstash/context7-mcp@4.0.0
Migrated the Context7 MCP server to the v2 SDK and the 2026-07-28 protocol revision. HTTP serving is now stateless for both modern and legacy clients, with Redis-backed sessions removed.
ctx7@0.5.7
ctx7 setup now writes the API key as a standard Authorization: Bearer header instead of a custom header, fixing a Codex auth failure where the tool fell through to an OAuth credential and refreshed with a dead token. The hosted endpoint accepts both header forms, so existing configs keep working.
@upstash/context7-mcp@3.2.2
Enterprise-Managed Auth (id-jag) access tokens are now validated at the MCP server, enabling MCP clients to authenticate to Context7 through an enterprise IdP such as Okta.
ctx7@0.5.3
GitHub API failures during ctx7 setup now show the HTTP status and error body (e.g. "HTTP 403: API rate limit exceeded") instead of the opaque "GitHub API error". A 403/429 hint suggests gh auth login or setting GITHUB_TOKEN.
@upstash/context7-mcp@3.2.1
Restored Node 18 support by pinning undici to ^6.26.0 and commander to ^13.1.0, resolving a "File is not defined" crash on startup.