Release / 30 Jul 2026 / with [email protected], @upstash/[email protected], @upstash/[email protected], @upstash/[email protected]

Context7 [email protected]

Retrieve documentation through CONNECT proxies on Node.js 26 and later.

All of Context7

Before you upgrade to [email protected]

1 to fix

Upgrade Node.js to 20.18.1 or later before installing MCP 3.2.5; Node.js 18 is no longer supported.

Action requiredConnect coding clients to a locally run documentation server over stdio or HTTP.Affects: Local MCP users and server operators running Node.js 18 or older Node.js 20 releases.

Read the evidence

upstash/context7/blob/@upstash/[email protected]/packages/mcp/CHANGELOG.md

What changed in [email protected]

MCP restores proxy and custom-CA support on newer Node.js and raises its minimum runtime. CLI setup gains a fallback for skill downloads and writes standard bearer headers.

MCP 3.2.5 requires Node.js 20.18.1+; CLI 0.5.6–0.5.7.

Fixed and improved

`HTTPS_PROXY` and custom-CA settings are honored again on Node.js 26+ instead of failing behind CONNECT proxies.

Now worksRetrieve documentation through an HTTPS proxy.

Read the evidence

upstash/context7/blob/@upstash/[email protected]/packages/mcp/CHANGELOG.md

Skill downloads fall back to raw GitHub files when the GitHub API is unavailable. Setup writes `Authorization: Bearer` so Codex uses the API key instead of stale OAuth credentials; older header configs still work.

Now worksConfigure Context7 documentation access and rules for coding agents.

Read the evidence

upstash/context7/blob/[email protected]/packages/cli/CHANGELOG.md

Seeded by @iluxav with Codex, from the release's public sources. Each change links to its evidence.