Get up-to-date, version-specific documentation and code examples from official sources directly in…
Context7 MCP Server
The Context7 MCP server provides access to up-to-date, version-specific documentation and code examples from official sources directly in developer workflows. Its README excerpt indicates it is published as @upstash/context7-mcp, with distribution details and licensing information shown via badges.
🛠️ Key Features
Up-to-date, version-specific documentation
Code examples sourced from official sources
🚀 Use Cases
Retrieving documentation for the correct version
Referencing official code examples during development
⚡ Developer Benefits
Direct access to documentation and examples
Works as an installable MCP server package (@upstash/context7-mcp)
⚠️ Limitations
The provided source material does not list specific MCP tools, endpoints, or supported platforms beyond the package details shown in the README excerpt.
LLMs rely on outdated or generic information about the libraries you use. You get:
❌ Code examples are outdated and based on year-old training data
❌ Hallucinated APIs that don't even exist
❌ Generic answers for old package versions
✅ With Context7
Context7 MCP pulls up-to-date, version-specific documentation and code examples straight from the source — and places them directly into your prompt.
Add use context7 to your prompt in Cursor:
txt
Create a Next.js middleware that checks for a valid JWT in cookies and redirects unauthenticated users to `/login`. use context7
txt
Configure a Cloudflare Worker script to cache JSON API responses for five minutes. use context7
Context7 fetches up-to-date code examples and documentation right into your LLM's context.
1️⃣ Write your prompt naturally
2️⃣ Tell the LLM to use context7
3️⃣ Get working code answers
No tab-switching, no hallucinated APIs that don't exist, no outdated code generation.
📚 Adding Projects
Check out our project addition guide to learn how to add (or update) your favorite libraries to Context7.
🛠️ Installation
Requirements
Node.js >= v18.0.0
Cursor, Claude Code, VSCode, Windsurf or another MCP Client
Context7 API Key (Optional for higher rate limits) (Get yours by creating an account at context7.com/dashboard)
WARNING
SSE Protocol Deprecation Notice
The Server-Sent Events (SSE) transport protocol is deprecated and its endpoint will be removed in upcoming releases. Please use HTTP or stdio transport methods instead.
Installing via Smithery
To install Context7 MCP Server for any client automatically via Smithery:
Go to: Settings -> Cursor Settings -> MCP -> Add new global MCP server
Pasting the following configuration into your Cursor ~/.cursor/mcp.json file is the recommended approach. You may also install in a specific project by creating .cursor/mcp.json in your project folder. See Cursor MCP docs for more info.
Since Cursor 1.0, you can click the install button below for instant one-click installation.
Once the MCP server is added, restart your editor. If you receive any errors, check the syntax to make sure closing brackets or commas are not missing.
Install in Roo Code
Add this to your Roo Code MCP configuration file. See Roo Code MCP docs for more info.
If the mcpServers object does not exist, create it.
Install in Claude Desktop
Remote Server Connection
Open Claude Desktop and navigate to Settings > Connectors > Add Custom Connector. Enter the name as Context7 and the remote MCP server URL as https://mcp.context7.com/mcp.
Local Server Connection
Open Claude Desktop developer settings and edit your claude_desktop_config.json file to add the following configuration. See Claude Desktop MCP docs for more info.
On Windows, some users may encounter request timed out errors with the default configuration.
In that case, explicitly configure the MCP server with the full path to Node.js and the installed package:
Use these alternatives to run the local Context7 MCP server with other runtimes. These examples work for any client that supports launching a local MCP server via command + args.
If you prefer to run the MCP server in a Docker container:
Build the Docker Image:
First, create a Dockerfile in the project root (or anywhere you prefer):
Click to see Dockerfile content
Dockerfile
FROM node:18-alpine
WORKDIR /app
# Install the latest version globally
RUN npm install -g @upstash/context7-mcp
# Expose default port if needed (optional, depends on MCP client interaction)
# EXPOSE 3000
# Default command to run the server
CMD ["context7-mcp"]
Then, build the image using a tag (e.g., context7-mcp). Make sure Docker Desktop (or the Docker daemon) is running. Run the following command in the same directory where you saved the Dockerfile:
bash
docker build -t context7-mcp .
Configure Your MCP Client:
Update your MCP client's configuration to use the Docker command.
Note: This is an example configuration. Please refer to the specific examples for your MCP client (like Cursor, VS Code, etc.) earlier in this README to adapt the structure (e.g., mcpServers vs servers). Also, ensure the image name in args matches the tag used during the docker build command.
Install Using the Desktop Extension
Install the context7.mcpb file under the mcpb folder and add it to your client. For more information, please check out MCP bundles docs.
Install in Windows
The configuration on Windows is slightly different compared to Linux or macOS (Cline is used in the example). The same principle applies to other editors; refer to the configuration of command and args.
Add the following configuration to the mcp section of your Copilot Coding Agent configuration file Repository->Settings->Copilot->Coding agent->MCP configuration:
Once saved, enter in the chat get-library-docs followed by your Context7 documentation ID (e.g., get-library-docs /nuxt/ui). More information is available on BoltAI's Documentation site. For BoltAI on iOS, see this guide.
Install in Rovo Dev CLI
Edit your Rovo Dev CLI MCP config by running the command below -
Context7 MCP provides the following tools that LLMs can use:
resolve-library-id: Resolves a general library name into a Context7-compatible library ID.
libraryName (required): The name of the library to search for
get-library-docs: Fetches documentation for a library using a Context7-compatible library ID.
context7CompatibleLibraryID (required): Exact Context7-compatible library ID (e.g., /mongodb/docs, /vercel/next.js)
topic (optional): Focus the docs on a specific topic (e.g., "routing", "hooks")
tokens (optional, default 5000): Max number of tokens to return. Values less than 1000 are automatically increased to 1000.
🛟 Tips
Add a Rule
If you don’t want to add use context7 to every prompt, you can define a simple rule in your MCP client's rule section:
For Windsurf, in .windsurfrules file
For Cursor, from Cursor Settings > Rules section
For Claude Code, in CLAUDE.md file
Or the equivalent in your MCP client to auto-invoke Context7 on any code question.
Example Rule
txt
Always use context7 when I need code generation, setup or configuration steps, or
library/API documentation. This means you should automatically use the Context7 MCP
tools to resolve library id and get library docs without me having to explicitly ask.
From then on, you’ll get Context7’s docs in any related conversation without typing anything extra. You can alter the rule to match your use cases.
Use Library Id
If you already know exactly which library you want to use, add its Context7 ID to your prompt. That way, Context7 MCP server can skip the library-matching step and directly continue with retrieving docs.
txt
Implement basic authentication with Supabase. use library /supabase/supabase for API and docs.
The slash syntax tells the MCP tool exactly which library to load docs for.
HTTPS Proxy
If you are behind an HTTP proxy, Context7 uses the standard https_proxy / HTTPS_PROXY environment variables.
💻 Development
Clone the project and install dependencies:
bash
bun i
Build:
bash
bun run build
Run the server:
bash
bun run dist/index.js
CLI Arguments
context7-mcp accepts the following CLI flags:
--transport <stdio|http> – Transport to use (stdio by default). Note that HTTP transport automatically provides both HTTP and SSE endpoints.
--port <number> – Port to listen on when using http transport (default 3000).
--api-key <key> – API key for authentication. You can get your API key by creating an account at context7.com/dashboard.
Example with HTTP transport and port 8080:
bash
bun run dist/index.js --transport http --port 8080
Another example with stdio transport:
bash
bun run dist/index.js --transport stdio --api-key YOUR_API_KEY
Ensure you're using Node.js v18 or higher for native fetch support
⚠️ Disclaimer
Context7 projects are community-contributed and while we strive to maintain high quality, we cannot guarantee the accuracy, completeness, or security of all library documentation. Projects listed in Context7 are developed and maintained by their respective owners, not by Context7. If you encounter any suspicious, inappropriate, or potentially harmful content, please use the "Report" button on the project page to notify us immediately. We take all reports seriously and will review flagged content promptly to maintain the integrity and safety of our platform. By using Context7, you acknowledge that you do so at your own discretion and risk.
