Upstash

Recently shipped the official Context7 plugin for OpenCode and hardened the hosted MCP server's auth and connection handling.

OpenCode now runs the hosted Context7 MCP server out of the box. Installing @upstash/context7-opencode@0.1.0 registers the hosted server plus the context7-mcp skill. Authentication defaults to OAuth, falling back to CONTEXT7_API_KEY or an apiKey option.

MCP server moved to stateless HTTP. The v4.0.0 migration to the v2 SDK and the 2026-07-28 protocol revision dropped Redis-backed sessions, and 4.0.1 stopped forcing responseMode: "sse"; responses return as plain JSON unless a handler emits progress, closing the connection-pool overflow that returned 503s.

Quiet streams no longer leak connections. A 60s AbortSignal.timeout() bounds both Context7 API calls, and SSE keepalive heartbeats are disabled (keepAliveMs: 0) — hung exchanges get reaped instead of riding the 1200s cap that drove the 2026-08-11 outage.

ctx7 credentials refresh instead of failing. ctl+/-era commands library, docs, and skills suggest no longer fall back silently to anonymous requests when a stored OAuth token expires, and generate refreshes instead of forcing a full re-login. Refreshes preserve the stored refresh_token when the server omits one. ctx7 setup writes Authorization: Bearer <key>; the hosted endpoint accepts both header forms, so existing configs keep working.

Setup reliability improved. ctx7 invokes gh directly (bypassing shell wrappers that triggered Microsoft Defender alerts), and skill install falls back to raw.githubusercontent.com when the git tree API is blocked. Query prompts now steer agents toward library documentation rather than passing the raw task.

Version bumps: @upstash/context7-mcp@4.0.2, ctx7@0.5.8, @upstash/context7-mcp@3.2.5 (undici 7, Node ≥ 20.18.1), @upstash/context7-pi@0.1.2, ctx7@0.5.7, ctx7@0.5.6, @upstash/context7-tools-ai-sdk@0.2.5, and @upstash/context7-mcp@4.0.1/4.0.0.