Skip to main content

Context7

Look up current, version-specific library and framework documentation through the Context7 MCP server.

Connect it with: MCP. Context7's own documentation: https://context7.com/docs/howto/api-keys.

What agents can do​

Connect Context7 so the agents working your tasks can reach it. With it connected, they can:

  • Resolve a library name to its Context7 ID and read its current documentation before writing code against it.
  • Check the API of the exact library version a project pins instead of relying on model memory.
  • Pull short, focused code examples for a framework topic a task names.

Before you start​

  • A Context7 account; a team account lets one key serve the whole organization.
  • An Org Owner or Admin adds the key as an organization secret, then links it on each project's MCP tab.
  • A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.

Connect with Context7​

Jaah connects to Context7 with an access token, not with a sign-in button.

Connect with an API key​

Find each value first:

  • API key: Sign in at https://context7.com/dashboard, create an API key and copy it - Context7 shows it once. A key on the organization's Context7 team lets every linked project share its plan.

Then add it to Jaah:

  1. In Jaah, open Secrets, select New, and pick the Context7 card.
  2. Name the secret and choose who can use it.
  3. Fill in API key.
  4. Select Save. Jaah tests the secret straight away (see Test the connection).

Jaah encrypts what you type and never shows it again — not to you, and not to an admin.

Use your own OAuth app​

Not used: Jaah connects to Context7 with an access token, not through an OAuth app.

Test the connection​

Select Test on the secret. Jaah calls Context7's API once (GET https://context7.com/api/v1/search?query=react) with the stored values, and shows whether Context7 accepted it, or which value Context7 refused and the status it answered. Jaah also tests automatically when you save or reconnect.

The last result and its time stay on the secret's page, so you can see whether it still works without testing again.

Who can use it​

Every secret has an owner, and the owner decides who can use it:

  • Personal — only your own tasks can use it. This is the default.
  • Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
  • Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.

More on owners and access: How secrets work.

Use it in an agent session​

An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:

  • org/<name> for an organization secret,
  • projects/<project>/<name> for one attached to a project,
  • me/<name> for your personal one.

A key connection hands the agent its fields: api_key.

Tell the agent in your task description which secret to use, for example “use the Context7 secret org/context7”.

Context7 also runs an MCP server, which gives agents ready-made Context7 tools instead of raw API calls. A project's agents get those tools only once you link the secret to the project:

  1. Open the project and its MCP tab.
  2. Select Link, pick the Context7 secret, and confirm.
  3. New tasks on the project start with the Context7 tools. Tasks already running keep the tools they started with.

Jaah connects agents to the server through a local bridge, so the token never appears in the agent's configuration or its transcript. A Google Antigravity session in the terminal runtime runs without these tools; on ACP it gets them.

Manage, rotate or disconnect​

Everything is on the secret's page under Secrets:

  • Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Context7 once the test passes. Steps: Replace or delete a secret.
  • Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Context7's side too, revoke the token at Context7.

Limitations​

  • Context7 counts every tool call against the key's plan: the Free plan allows 1,000 calls a month, then calls fail until the next month or an upgrade.
  • Only public libraries Context7 has indexed are covered, plus private repositories added to the Context7 team.
  • Agents get Context7 only in the projects the secret is linked to.
  • Agents can do only what the connected Context7 account allows.

Troubleshooting​

Test says Context7 rejected the API key (401)

The key was deleted or mistyped, or does not start with ctx7sk-. Create a new key at https://context7.com/dashboard and select Replace.

Agents' Context7 calls start failing mid-month

The key's plan ran out of calls. Check usage at https://context7.com/dashboard and upgrade the plan or wait for the monthly reset.

New tasks on the project have no Context7 tools

Link the secret on the project's MCP tab, then start a new task. Tasks already running keep the tools they started with, and an agent marked Not supported on that tab cannot load MCP servers.

Still stuck? Select Test and read the result: it names the value Context7 refused and the status it answered.

FAQ​

Why is the key required when Context7 works without one?

Without a key Context7 serves calls anonymously under a shared, tight rate limit. The key ties every call to your organization's plan and limits.

What does Test do?

It runs one Context7 library search with the key and checks Context7 accepts it. It changes nothing in your Context7 account.

Can Jaah or an admin see the key or token?

No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.

Can I connect more than one Context7 account?

Yes. Add one secret per account, each with its own name, and tell the agent which one to use.