Skip to Content
PluginsContext7 — up-to-date docs

Context7 — up-to-date docs

A model knows a library as it was when the model was trained. APIs change: a hook gets a new signature, a config option is renamed, a framework moves to a new router. The Context7 plugin gives a connected agent two tools from Context7 , an open-source project by Upstash: look up a library, then read its current documentation and code examples — for the version the project uses.

How to use it

  1. In the add-card menu choose Plugin…, open Context7 — up-to-date docs in the Plugins tab and press Add to canvas.
  2. Draw an arrow from an agent to the card.

The agent now has two tools:

  • context7_resolve_library_id — finds the library by name (“React”, “Next.js”, “Django”) and lists the matches with their Context7 id (/reactjs/react.dev), how many code examples there are, how trusted the source is and which versions are indexed.
  • context7_query_docs — returns the documentation and examples of one library for one focused question (“useEffect cleanup function”).

Most agents use them on their own when a task touches a library API. You can also ask: “check the Next.js docs first”, or add use context7 to your prompt. Remove the arrow and the tools are gone. No restart for most CLIs, and nothing is installed into your CLI.

It works without an account

Context7’s documentation index is a hosted service, free to use. Without a key it has a lower rate limit; a free API key from the Context7 dashboard  raises it. Paste the key in the card’s Key & cache panel — it is stored encrypted on your computer, never shown again and never written into a file or a command line. One key serves every Context7 card.

The card shows how many requests are left and when the limit resets. When the limit is used up the card says Rate-limited, agents get a clear message instead of an error, and no further requests are sent until the limit resets — answers already in the cache still work.

The cache

Every answer is kept on your computer for 24 hours. When two agents ask the same question, or the same agent asks again, the answer comes from the cache and costs no request. The Key & cache panel shows how many answers are cached and how many lookups they served, and clears the cache.

Auto-docs

Turn on Auto-docs on the card and the agent gets help before each of your prompts:

  • When the prompt names one of the project’s dependencies (from package.json, requirements.txt, pyproject.toml, Cargo.toml or go.mod), the agent gets a one-line note that current docs for it are available — with the version your project declares. No request is sent for this, so the turn starts just as fast. The note comes once per library every half hour.
  • When the prompt says context7 (“use context7”) and names a dependency or a library id (/vercel/next.js), the documentation itself is added to the turn. NeuroSquad waits for it for about a second and a half; if Context7 is slower, the agent gets the note instead, and the answer is cached for the next time.

Auto-docs works with Claude Code, Codex, Qwen Code, OpenCode, Kilo Code, pi, omp and Gemini CLI. Every other agent connected by an arrow still gets the two tools.

WSL and SSH workspaces

Agents in a workspace inside WSL or on an SSH host get the two tools by arrow as usual — the lookups are made by NeuroSquad on this computer. Auto-docs reads the project’s package.json and other manifests from WSL or over the SSH connection.

What the card shows

  • The service state — Ready, Rate-limited, Offline or Error — with requests left and the reset date.
  • Try a lookup: type a library and a question to see what an agent would get.
  • Recent lookups: which library and question, which agent asked, when, and whether it came from the cache.

Library names and questions are sent to Context7’s servers (run by Upstash). Never put secrets, passwords or proprietary code into a question — the tool descriptions tell agents the same. The rest of your project stays on your computer: auto-docs reads the dependency list locally and sends only a library name and the question.

Where it comes from

The two tools are those of Context7’s official MCP server (@upstash/context7-mcp, MIT license), with its descriptions; NeuroSquad calls the same Context7 API directly, so nothing extra is installed or started. The documentation index itself is Context7’s hosted service. If you want documentation lookups that never leave your computer, a self-hosted documentation MCP server can be added from the MCP tab of the catalog instead.

Memory (mem0)Code Graph