Skip to content

Context7 MCP connector

The Context7 connector brings current documentation for software libraries into Claude, ChatGPT, Cursor, Microsoft Copilot 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.

  • Connects over OAuth
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Find the current docs for React Router loaders and show an example.

Working in Context7 with Elaichi

  • Query docs
  • Resolve library ID
Ask anything…
Governance / Audit log Last 24 hours
Context7 Resolve library ID Emily Carter · ChatGPT · 9:41 AM Done
Context7 Query docs Emily Carter · ChatGPT · 9:41 AM Done
Context7 Query docs Megan Brooks · Claude · 9:38 AM Done
Context7 Query docs Ryan Hayes · Cursor · 9:35 AM Done

How to connect Context7 to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Context7 MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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 Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

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

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Context7 MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

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

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

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

Context7 MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

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

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

Context7 MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

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

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Context7 to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

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

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

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

What teams do with Context7 through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Context7 is logged.

  • Engineering

    Check the current way to call a library

    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.

  • Developer Relations

    Write a tutorial against the real docs

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

  • Support

    Answer a customer question about a library

    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.

  • Product

    Confirm what a library can do before committing

    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.

  • QA

    Read the docs behind a failing test

    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.

  • Solutions Engineering

    Prepare a proof of concept with fewer surprises

    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.

Try asking

  • “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.”

See all 2 Context7 tools →

What connecting Context7 gets you

6 screens from Elaichi, each doing one job for your Context7 account.

Elaichi Agent

Ask Elaichi to work across your apps.

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.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about any library, get current docs back.

Type a question in plain language and read answers drawn from up-to-date Context7 documentation.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

One endpoint brings Context7 to every client.

Claude, ChatGPT, Cursor and Microsoft Copilot read Context7 docs through one governed endpoint, no SDK or shared key.

ElaichiTools
Tool Action Description
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…

Tool catalog

2 tools cover Context7 with no code.

Resolve any library and query its docs, with nothing to build or maintain.

ElaichiToolboxes
Name Source template Tools Created

Engineering toolbox

Context7 · library docs and code examples

Context7 starter 18 Mar 4, 2026

Developer Relations toolbox

Context7 · tutorials and sample apps

— 9 Mar 2, 2026

Support toolbox

Context7 · customer questions about libraries

— 24 Feb 27, 2026

Product toolbox

Context7 · library capabilities and limits

Context7 starter 6 Feb 19, 2026

QA toolbox

Context7 · upgrade changes and test fixes

— 31 Jan 30, 2026

Solutions Engineering toolbox

Context7 · proofs of concept and demos

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Context7 toolbox.

Scope a toolbox to Engineering, Support or Developer Relations and hand each team what it needs.

ElaichiConnections
Connection Scope Status Access
CO

Context7 (Platform)

Connected by Emily Carter

Personal • Active 1 team · 6 members
CO

Context7 (Frontend)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
CO

Context7 (Mobile)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
CO

Context7 (Developer Relations)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
CO

Context7 (Support)

Connected by Ryan Hayes

Personal • Active Not shared
CO

Context7 (Solutions)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Share one Context7 connection, keep the credential private.

One person connects, teams and members work through it, and nobody else sees a secret.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Context7 Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Context7 Libraries Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Context7 Libraries List Toolbox

Audit log

Every Context7 lookup is on the record.

See who searched which library, when, and what came back, in an append-only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.

Context7 digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch libraries

    Context7

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Context7

    Queued

Workflows

A schedule starts the work, a person approves.

Fetch Context7 docs for your libraries, group changes, draft a digest, approve, post it back.

Context7 health

Refreshed 4 minutes ago · every 15 minutes · from the libraries collection

Live

Libraries

1,284 ↓ 12%

Docs

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Libraries created

Last 14 days

By team

Share of activity

Platform 34%

Frontend 27%

Mobile 21%

Developer Relations 18%

Collections and dashboards

Context7 usage numbers arrive without anyone asking.

Four metrics, a 14 day chart, a team breakdown, computed on a schedule with no model.

Why connect Context7's MCP server through Elaichi

Context7 builds and runs this MCP server. Elaichi sits in front of it, so Context7's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Context7's server directly, outside Elaichi, get none of this.

  • One address for every AI client

    Claude, ChatGPT, Cursor and Microsoft Copilot reach Context7's tools at the same Elaichi address as every other connected app. Nobody adds Context7's server to each client one by one.

  • Each person signs in as themselves

    Each person signs in to Elaichi as themselves. Members connect with their own Context7 sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.

  • Rules checked before a call leaves

    Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Context7's server. By default, a tool Context7 does not mark read-only or non-destructive counts as destructive, and over MCP it still runs under the "Use your connected apps" consent.

  • One audit log for every app

    Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.

  • Tool issues go to Context7

    Context7 builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Context7 team.

    context7.com/contact

Why run a vendor's MCP server through Elaichi →

For IT and engineering

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.

Elaichi compared with Zapier MCP and Composio for Context7, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. 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 Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Context7 tools for your AI agents

2 tools are ready to call through Elaichi's MCP endpoint the moment you connect Context7, governed by the same roles, restrictions, and audit log as everything else in Elaichi. Context7 builds and runs these tools.

Questions, answered

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, Microsoft Copilot, 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 still appears in Elaichi's tool search, flagged as restricted, but the AI client cannot run it, whatever the prompt says.

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, Microsoft Copilot 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, Microsoft Copilot, 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.

Put Context7 in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot