Upstash

Context7 ships a new sign-in flow that agents can't ignore, and Workflow runs gain multi-label filtering.

Context7 MCP sign-in now presents a real dialog instead of text. When an anonymous client hits the per-IP threshold, the server fires an MCP elicitation/create request — delivering the npx ctx7 setup command in a client-rendered dialog rather than appending it into tool results, where some agents treat it as untrusted instructions. Clients that don't advertise the elicitation capability see no nudge.

Context7 query-docs now asks for one concept per query. Callers are told to make a separate query for each distinct topic (unless the question is about how concepts interact), which avoids diluted, shallow results. Applied consistently across the MCP server, CLI, pi, and AI SDK tools.

GitHub API errors during ctx7 setup now show the actual problem. A failing skill download surfaces the HTTP status and GitHub error body — HTTP 403: API rate limit exceeded instead of the opaque "GitHub API error". Failed skill entries show a red ✖ with error detail on its own line.

Context7 SDK no longer crashes on non-JSON error bodies. HttpClient.request() catches failed res.json() calls, so HTML 502s and plain-text 429s surface as a typed Context7Error instead of a raw SyntaxError.

Workflow runs gained multi-label support. The label field on client.trigger and context.invoke now accepts string | string[], log and DLQ filters accept arrays with OR semantics, and context.labels replaces the deprecated context.label.