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.
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.
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.
Workflow runs now support multiple labels via string | string[] on client.trigger and context.invoke, with log, DLQ, and cancel filters accepting arrays to match runs that have any of the given labels. The context.labels: string[] field replaces the deprecated context.label, and workflow run logs now expose a labels field.
ctx7 login now always uses the device-code flow. The localhost-callback path is removed — every install (laptop, SSH, ...ctx7 login and ctx7 setup. Required for headless / remote hos...ctx7 setup now properly supports --antigravity, installing skills to .agent/skills, a GEMINI.md rule section (...X-Context7-Auth-Prompt: 1 response header on `...Metrics per Queue/Flow-Control/Url are requested time to time but not implemented since they are basically expensive.
They are expensive because numb...
We currently provide JS/TS and Golang SDKs that exposes the official trigger() method to start a new workflow run. To support a broader range of use...
Currently, the Logs tab does not show details about the distribution or count of matching logs entries.
This makes it difficult to understand how oft...
For each endpoint that user serve's via Workflow, we can keep separate metrics.
We have the following metrics that we show globally. This could be pe...
Currently, the Logs tab does not show details about the distribution or count of matching logs entries. This makes it difficult to understand how ofte...