# Context7 MCP connector

The Context7 connector brings current documentation for software libraries into Claude, ChatGPT, Cursor and the Elaichi Agent, so anyone can ask how a library works and get an answer drawn from its latest docs, with every lookup logged.

Source: https://elaichi.ai/connectors/context7/

## Facts

| | |
| --- | --- |
| Application | Context7 |
| Category | Application Development |
| AI tools | 2 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Context7 builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | context7.com/contact |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Context7 is connected

- Find the current docs for React Router loaders and show an example.
- How do I set up authentication in Next.js 15?
- Look up the Stripe Node library and explain webhook signing.

## Connect Context7 in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Context7.
2. Optionally set Share with, then press Connect.
3. Approve it in Context7. Context7's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Context7 tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Context7 MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Context7 MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

## Context7 MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Connect Context7 to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Only Read is granted by default, which is not enough to call a Context7 tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Context7 through Elaichi

### Check the current way to call a library

Engineering. Ask how a library handles something today and get an answer from its latest docs instead of a model's memory of an older version. Paste the answer straight into the pull request.

### Write a tutorial against the real docs

Developer Relations. Pull the current docs for a library before drafting a guide or sample, so the steps match what the library actually does right now.

### Answer a customer question about a library

Support. When a ticket asks why a library behaves a certain way, look up the relevant docs and reply with the current guidance rather than guessing.

### Confirm what a library can do before committing

Product. Before promising a feature that depends on a third party library, check its docs to see whether the capability exists and how it is meant to be used.

### Read the docs behind a failing test

QA. When a test breaks after a library upgrade, look up what changed in that library's docs and point the fix at the right place.

### Prepare a proof of concept with fewer surprises

Solutions Engineering. Resolve the exact library a prospect uses and read its docs ahead of a demo, so the setup works the first time in front of them.

## Elaichi vs Zapier MCP vs Composio for Context7

All three can connect Context7 to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Context7 tools | Allow or restrict single Context7 tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Context7 call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Context7 to Claude?

Connect Context7 inside Elaichi first, which takes an OAuth sign-in and nothing else, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude can then read current library docs from Context7 on your behalf.

### Does Context7 work with ChatGPT and Cursor as well as Claude?

Yes. Once Context7 is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Context7 once and every client picks it up.

### What can an AI agent actually do with my Context7 data?

With Context7 connected, an agent can find the right library when you name it and read its current documentation to answer your question, whether that is how to set up authentication in a framework or what a method expects. Short, specific asks such as naming the library and the feature work better than long paragraphs. The connector reads docs; it does not change anything in Context7.

### Does connecting Context7 give the AI everything?

No. An agent working through Context7 only has the access of the person who signed in, and Elaichi can narrow that access further with roles and restrictions. Elaichi never widens what a person could already do in Context7.

### Can my team share one Context7 connection?

Yes. One person connects Context7 in Elaichi and shares the connection with a team, and nobody else ever handles a credential. Each teammate still signs in to Elaichi as themselves, so every Context7 lookup in the audit log is tied to the person who made it.

### Can I stop an agent from deleting or changing things in Context7?

The Context7 connector only reads library docs, so there is nothing for an agent to delete or change. Even so, Elaichi applies restrictions per action, and a restricted action is never shown to the AI client at all, so no prompt can reach it.

### What happens to a Context7 connection when someone leaves?

Offboarding a person in Elaichi ends their access to Context7 through every client at once. A Context7 connection they shared keeps working for everyone else on the team. Disconnecting Context7 once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

### Does the Context7 MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Context7 is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Context7?

Yes. Both let Claude, ChatGPT or Cursor use Context7. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Context7 call.

### How is Elaichi different from Composio for Context7?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Context7: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 2 Context7 tools

Every tool below is callable through https://api.elaichi.ai/mcp once Context7 is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Resolve library ID** (Action). Resolves a package/product name to a Context7-compatible library ID and returns matching libraries. You MUST call this function before 'Query Documentation' tool to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format…
- **Query docs** (Search). Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework. You must call 'Resolve Context7 Library ID' tool first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user…