Context7 is a documentation service that gives AI coding agents up-to-date, version-specific documentation and code examples for libraries and frameworks.
Agen.co connects to Context7 through Context7's own hosted MCP server as an Official connector. Each user signs in with their own Context7 account, so there is no app to register and no credentials to copy.
Prerequisites
Prerequisites
- A Context7 account for each person whose agents will use the connector.
Context7 registers Agen.co automatically, so there is no client ID or secret to copy and no callback URL to register.
In the Agen.co portal, go to Connectors → My connectors and click Add connector.
In the Select connector drawer, search for
Context7and select it. The Add Context7 panel opens.Fill in the field:
Field Required Description Instance Slug Yes Namespaces this instance — it prefixes each imported tool as slug__tool, so several instances of the same MCP can coexist. Prefilled withcontext7. Use lowercase kebab-case. You can change it later from the connector's settings.Click Connect. Context7 opens in a new tab, and the panel shows Waiting for authorization — complete it in the opened tab…
Sign in to your Context7 account and approve access.
Back in Agen.co, the panel switches to Select the tools to import from Context7. Every tool is toggled on; turn off any you don't want to import, then click Add.
The connector is created and its tools imported only when you click Add. If you close the panel before that, nothing is saved, even if the Context7 tab reported success.
The Context7 MCP server serves two tools (checked 2026-10-06):
| Tool | What it does |
|---|---|
| resolve-library-id | Resolves a library or product name to a Context7 library ID and returns the matching libraries |
| query-docs | Retrieves up-to-date documentation and code examples for a library, using a library ID from resolve-library-id |
Context7 is read-only: agents can look up documentation but cannot change anything in Context7 or in your systems. Agents call resolve-library-id first to get a library ID, unless the prompt already names one in the form /org/project.
Enabling the Context7 connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.