Context7 MCP

Live

API KEY

DEVELOPER TOOLS

Developer Tools

Up-to-date library documentation, version-specific code examples, and API references your coding agent needs live in Context7. Context7 MCP gives your agent per-user API key access to live documentation scoped to the authorizing developer account.

  • Acts as the user: Doc access stays tied to the Context7 account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Context7 MCP
agent · Acme Q3
Run
What's the correct way to use React 19 useTransition with async functions?
S
context7_get_library_docs
78ms
Coding agent
In React 19, useTransition now accepts async functions directly. You can pass an async callback and React will automatically handle the pending state. Example: const [isPending, startTransition] = useTransition(); startTransition(async () => { await save(data); });
Source: Context7 — React 19 docs, /hooks/use-transition
context7mcp
1
14:52
Message Claude...

Tools your agent reaches for on Context7 MCP, scoped per user.

CALL ANY TOOL
Fetch version-specific library docs, code examples, and API references from Context7. Every call scoped to the authorizing developer account.
context7mcp_query_docs
Query docs
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 explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query. Do not call this tool more than 3 times per question.
Parameters
Name
Type
Required
Description
libraryId
string
Required
Exact Context7-compatible library ID (e.g., '/mongodb/docs', '/vercel/next.js', '/supabase/supabase', '/vercel/next.js/v14.3.0-canary.87') retrieved from 'resolve-library-id' or directly from user query in the format '/org/project' or '/org/project/version'.
query
string
Required
What to look up in the library's documentation, scoped to a single concept. Be specific and include relevant details, but keep each query to one topic: if the user's question spans multiple distinct concepts, make a separate call per concept instead of combining them, unless the question is about how the concepts interact. Good: 'How to set up authentication with JWT in Express.js' or 'React useEffect cleanup function examples'. Bad (too vague): 'auth' or 'hooks'. Bad (too broad): 'routing and auth and caching in Next.js'. The query is sent to the Context7 API for processing. Do not include any sensitive or confidential information such as API keys, passwords, credentials, personal data, or proprietary code in your query.
schema_version
string
Optional
Optional schema version to use for tool execution
tool_version
string
Optional
Optional tool version to use for tool execution
context7mcp_resolve_library_id
Resolve library id
Build your Agent
Drop the toolkit in, point it at the user, and your coding agent can fetch current library docs without touching an API key.
Python · LlamaIndex
// Scalekit AgentKit — framework-agnostic
import { ScalekitClient } from "@scalekit/sdk";

const client = new ScalekitClient();
const token = await client.connections.getToken("context7mcp", userId);
const mcp = new MCPClient({ token });
// OpenAI SDK
import OpenAI from "openai";
import { ScalekitClient } from "@scalekit/sdk";

const sk = new ScalekitClient();
const token = await sk.connections.getToken("context7mcp", userId);
const client = new OpenAI();
const resp = await client.responses.create({ tools: [{ type: "mcp", server_url: mcpUrl, headers: { Authorization: `Bearer ${token}` } }] });
// Anthropic SDK
import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit/sdk";

const sk = new ScalekitClient();
const token = await sk.connections.getToken("context7mcp", userId);
const client = new Anthropic();
const resp = await client.beta.messages.create({ mcp_servers: [{ url: mcpUrl, authorization_token: token }] });
// Google GenAI SDK
import { GoogleGenAI } from "@google/genai";
import { ScalekitClient } from "@scalekit/sdk";

const sk = new ScalekitClient();
const token = await sk.connections.getToken("context7mcp", userId);
const ai = new GoogleGenAI();
const resp = await ai.models.generateContent({ tools: [{ mcpServers: [{ serverUrl: mcpUrl, httpOptions: { headers: { Authorization: `Bearer ${token}` } } }] }] });
Try these prompts
Paste any prompt into your coding agent to start pulling live library documentation from Context7.
"What changed in Next.js 15 App Router compared to 14? Show me the migration guide from Context7."
"Fetch the latest Prisma docs for creating a relation between two models with cascade delete."
"What's the correct TypeScript signature for a React 19 Server Action that handles form submission?"
"Pull the Tailwind CSS v4 docs for the new CSS-first configuration system."
"Show me how to set up Drizzle ORM with a PostgreSQL connection pool using the latest docs."
SEE HOW AUTH WORKS
Developers authorize Context7 once. Their API key stays vaulted, every doc query is checked, and every action is logged.
1
Authorize
Your user connects
Context7 MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Context7 MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Context7 MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Context7 MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other developer tools and search connectors.
Engineering Teams
DevOps assistant agent
Polls GitHub for failing checks and stale PRs, opens Linear issues for the ones that need work, and posts a daily digest to Slack. It acts as the engineer, not a shared service account.
Engineering Teams
Engineering standup agent
Pulls commits from GitHub and GitLab, tracks issue movement in Jira, and posts a per-engineer standup brief to Slack. Each engineer's activity is read on their own delegated OAuth.
Engineering Teams
Auto release notes agent
Reads merged GitHub PRs, groups them into structured release notes, publishes the page to Notion, and announces the release in Slack. Every call runs on the engineer's own delegated OAuth.
Engineering Teams
Slack triage
Polls Slack for new messages, classifies bugs and support requests with a LangGraph router, files GitHub issues or Zendesk tickets, and confirms in the thread.
Test other agents
Same per-user auth pattern across other developer tools and search connectors.
ENGINEERING
DevOps assistant agent
Poll GitHub for failing checks and stale pull requests, open Linear issues for the ones that need work, and digest to Slack.
ENGINEERING
Auto-release notes agent
Group merged GitHub PRs into structured release notes, publish the page to Notion, and announce the release in Slack.
ENGINEERING
Engineering standup agent
Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.
ENGINEERING
Slack triage agent
Classify new Slack messages as bugs or support requests, file the GitHub issue or Zendesk ticket, and reply in the thread.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Without Scalekit
With Scalekit
API key management
Hardcoded in env vars
Vaulted, per-user
Credential storage
Plaintext in config files
AES-256, per-user
Per-user scoping
Shared team key
Scoped to authorizing user
Audit trail
None
90-day log, per call
Revocation
Delete and redeploy
One API call
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does my agent need a Context7 API key?
No. Each developer authorizes via their Context7 account. Scalekit vaults the resulting key and injects it per call. Your agent code never handles credentials.
What happens if a user revokes access?
The key is invalidated immediately. Subsequent calls return an auth error and no docs are returned. The audit log records the revocation event.
Can I use this in a multi-tenant dev tool?
Yes. Keys are isolated per developer account. Each call resolves the key scoped to the user making the request, never a shared team credential.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace context7mcp
Cursor Code REPL
# ~/.cursor/mcp.json
{
"mcpServers": {
"context7mcp": {
"url": "https://mcp.scalekit.com/context7mcp",
"headers": { "Authorization": "Bearer <token>" }
}
}
}
Codex Code REPL
# ~/codex-mcp.json
{
"mcpServers": {
"context7mcp": {
"url": "https://mcp.scalekit.com/context7mcp",
"headers": { "Authorization": "Bearer <token>" }
}
}
}
Copilot Code REPL
# .vscode/mcp.json
{
"servers": {
"context7mcp": {
"type": "http",
"url": "https://mcp.scalekit.com/context7mcp",
"headers": { "Authorization": "Bearer <token>" }
}
}
}