Context7
What it does
Section titled “What it does”Context7 gives Speedwave up-to-date documentation for the libraries and frameworks your project uses, instead of relying on what it already knows. It works out of the box with no sign-in, so it’s one of the few integrations you can use without any setup. If you hit its rate limit often, adding a free Context7 API key raises that ceiling.
What it consists of
Section titled “What it consists of”Speedwave runs Context7 as its own worker container, calling https://context7.com/api/v2 on your behalf. The worker needs no credentials to function. If you add an API key, it’s mounted read-only at /tokens/api_key, under ~/.speedwave/tokens/<project>/context7/api_key on the host. Without that file, the worker starts in anonymous mode and logs that it’s doing so.
How it works
Section titled “How it works”Claude uses two tools, in order. resolveLibraryId takes a library name like “react” or “spring boot” plus your question, and returns a ranked list of Context7-compatible library IDs. queryDocs then takes that ID and the question and returns documentation snippets as plain text, capped by a tokens budget (5,000 by default, and Speedwave clamps whatever Claude requests to between 500 and 15,000). Both tool descriptions tell Claude to resolve the ID first unless it already knows it.
Anonymous mode applies a per-IP rate limit, roughly 200 requests a day. An API key (prefix ctx7sk_) raises that limit and is otherwise optional. When a call fails, Context7 returns a specific reason: an invalid key names the expected ctx7sk_ prefix, an unknown library ID says to call resolveLibraryId first, and a rate limit error reports your quota tier and when it resets, with different upgrade guidance depending on whether you have a key. Server errors (5xx) are retried automatically with backoff before Claude ever sees them.
What Speedwave can do
Section titled “What Speedwave can do”Context7 exposes two tools, both read-only: neither writes to your project or to Context7 itself.
| Tool | What it does |
|---|---|
resolveLibraryId | Looks up a library name (like “react” or “spring boot”) plus your question, and returns a ranked list of matching Context7 library IDs. |
queryDocs | Fetches documentation snippets for a known library ID, answering a specific question, capped by a token budget. |
Set it up
Section titled “Set it up”- Turn on Context7 for your project. No sign-in is needed, so it’s ready to use immediately.
- Optionally, get a free API key from context7.com/dashboard for a higher rate limit, and add it in the integration’s settings.
See Connect an integration for the general steps to enable any integration.
Security boundaries
Section titled “Security boundaries”The Context7 worker holds no other service’s credentials, and in anonymous mode it holds no credentials at all. Each documentation lookup sends your query text and the library name to Context7’s API. Nothing else about your project reaches Context7. Context7 may retain and use your queries for benchmarking and offers no DPA or SLA; see Data and privacy for details, and how credentials are handled for how the optional API key stays isolated to this worker.