Context7 MCP - Up-to-date Docs For Any Prompt
 
Without Context7
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 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: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 generations.
Getting Started
Requirements
- Node.js >= v18.0.0
- Cursor, Windsurf, Claude Desktop or another MCP Client
Installing via Smithery
To install Context7 MCP Server for Claude Desktop automatically via Smithery:
Install in Cursor
Go to:
Settings -> Cursor Settings -> MCP -> Add new global MCP serverPasting the following configuration into your Cursor
~/.cursor/mcp.json file is the recommended approach. See Cursor MCP docs for more info.Install in Windsurf
Add this to your Windsurf MCP config file. See Windsurf MCP docs for more info.
Install in VSCode
Add this to your VSCode MCP config file. See VSCode MCP docs for more info.
Install in Claude Code
Run this command. See Claude Code MCP docs for more info.
Install in Claude Desktop
Add this to your Claude Desktop
claude_desktop_config.json file. See Claude Desktop MCP docs for more info.Available Tools
resolve-library-id: Resolves a general library name into a Context7-compatible library ID.
get-library-docs: Fetches documentation for a library using a Context7-compatible library ID.
Development
Clone the project and install dependencies:
Build:
Local Configuration Example
Testing with MCP Inspector
Troubleshooting
ERR_MODULE_NOT_FOUND
If you see this error, try using
bunx instead of npx.This often resolves module resolution issues, especially in environments where
npx does not properly install or resolve packages.Context7 in media
License
MIT
Context7 MCP - Up-to-date Docs For Any Prompt
 
Without Context7
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 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: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 generations.
Getting Started
Requirements
- Node.js >= v18.0.0
- Cursor, Windsurf, Claude Desktop or another MCP Client
Installing via Smithery
To install Context7 MCP Server for Claude Desktop automatically via Smithery:
Install in Cursor
Go to:
Settings -> Cursor Settings -> MCP -> Add new global MCP serverPasting the following configuration into your Cursor
~/.cursor/mcp.json file is the recommended approach. See Cursor MCP docs for more info.Install in Windsurf
Add this to your Windsurf MCP config file. See Windsurf MCP docs for more info.
Install in VSCode
Add this to your VSCode MCP config file. See VSCode MCP docs for more info.
Install in Claude Code
Run this command. See Claude Code MCP docs for more info.
Install in Claude Desktop
Add this to your Claude Desktop
claude_desktop_config.json file. See Claude Desktop MCP docs for more info.Available Tools
resolve-library-id: Resolves a general library name into a Context7-compatible library ID.
get-library-docs: Fetches documentation for a library using a Context7-compatible library ID.
Development
Clone the project and install dependencies:
Build:
Local Configuration Example
Testing with MCP Inspector
Troubleshooting
ERR_MODULE_NOT_FOUND
If you see this error, try using
bunx instead of npx.This often resolves module resolution issues, especially in environments where
npx does not properly install or resolve packages.Context7 in media
License
MIT