Context7 MCP server by Upstash that pulls up-to-date, version-specific library documentation and code examples directly into Claude's context so answers match the libraries you actually use.
Makes outbound network requests to the Context7 service to resolve libraries and fetch documentation., Returned documentation and code snippets are third-party content; review examples before running them in your project.
Privacy notes
The library names and documentation topics you query are sent to the Context7 service to return matching docs., Avoid placing secrets or private identifiers in the library queries passed to the server.
Author
Upstash
Submitted by
glorydavid03023
Claim status
unclaimed
Last verified
2026-06-02
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
78
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Complete
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
Registry metadata indicates a reviewed listing.
Done
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Context7 keeps Claude's answers aligned with the libraries you actually depend on. When you ask for help with a framework or package, the server resolves the library and pulls current, version-specific documentation and code examples straight into the prompt context. That reduces the common failure mode where a model answers from an outdated training snapshot and produces APIs that no longer exist. Add a short instruction like "use context7" to a prompt and Claude can ground its response in fresh docs.
Features
Fetches up-to-date, version-specific documentation for popular libraries on demand.
Resolves a free-form library name to a canonical documentation source before fetching.
Returns focused documentation and code examples scoped to the topic you ask about.
Reduces outdated or hallucinated APIs by grounding answers in current docs.
Runs as a standard stdio MCP server that installs into Claude Code and Claude Desktop with one command.
Works without an account; an optional API key raises rate limits.
Use Cases
Get accurate, current usage for a library instead of relying on the model's training cutoff.
Pull version-specific code examples while implementing a feature.
Confirm the correct API surface for a fast-moving framework before writing code.
Reduce time spent cross-checking official docs in a separate browser tab.
Ground refactors and migrations in the documentation for the target version.
Installation
Claude Code
Make sure Node.js 18+ is installed (verify with npx --version).
Run: claude mcp add context7 -- npx -y @upstash/context7-mcp
Verify the server is registered: claude mcp list
Add "use context7" to a coding prompt to confirm docs are pulled in.
Claude Desktop
Open your Claude Desktop configuration file.
Add the Context7 server to the mcpServers section using the configuration below.
Restart Claude Desktop.
Confirm the server appears and ask a library question with "use context7".
Append a short instruction so Claude pulls fresh documentation.
"Show me how to define a route with the latest version of my web framework. use context7"
Resolve a specific library version
Ask for version-scoped guidance to avoid outdated APIs.
"Give me the current recommended client setup for this database library, version-specific. use context7"
Pull focused code examples
Request examples for a single topic rather than a broad overview.
"Fetch up-to-date examples for handling file uploads in this framework. use context7"
Security
The server makes outbound network requests to the Context7 service; only the library names and topics you query are sent to resolve and fetch documentation.
Returned documentation and code examples are third-party content, so review any snippet before running it in your environment.
Do not embed secrets, tokens, or private identifiers in the library queries you pass to the server.
If you configure an optional API key for higher rate limits, store it as an environment variable rather than committing it to source control.
Troubleshooting
npx cannot resolve the package
Verify Node.js 18+ and npx are installed (npx --version). Networks that block the npm registry will prevent npx -y @upstash/context7-mcp from resolving.
Documentation requests time out or return nothing
Confirm the machine has internet access to the Context7 service. Transient rate limiting can also cause empty responses; retry, and consider configuring an API key for higher limits.
Server not listed in Claude Code
Re-run claude mcp add context7 -- npx -y @upstash/context7-mcp, then claude mcp list. Confirm it was added to the scope (project versus user) you are running in.
Claude does not use Context7 automatically
Add an explicit instruction such as "use context7" to the prompt. The server provides documentation tools, but the model decides when to call them, so a nudge helps in ambiguous requests.
Show that Context7 MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/context7-mcp-server)
How it compares
Context7 MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
Context7 MCP server by Upstash that pulls up-to-date, version-specific library documentation and code examples directly into Claude's context so answers match the libraries you actually use.
Index any documentation — websites, GitHub repos, npm/PyPI packages, local files — and give Claude always-current, version-specific answers with the open-source Grounded Docs MCP server. An offline-first alternative to Context7, Nia, and Ref.Tools.
Official AWS Labs MCP server that lets AI assistants read, search, and get recommendations across AWS documentation, returning pages as clean markdown with no AWS account or credentials required.
Official AWS Labs fully-managed remote MCP server providing up-to-date AWS documentation, code samples, agent skills, API and CloudFormation regional availability, and CDK/Amplify/Strands guidance over a hosted HTTP endpoint.
✓Makes outbound network requests to the Context7 service to resolve libraries and fetch documentation.
Returned documentation and code snippets are third-party content; review examples before running them in your project.
✓The server stores its index locally, but MCP tool arguments and returned search/fetch results can be visible to your MCP client and model provider transcript.
The `scrape_documentation` and `fetch_url` tools can fetch URLs, GitHub repos, packages, or local paths — only index sources you are authorized to access and constrain local paths and network targets.
✓The server is read-only: it fetches and searches public AWS documentation and does not call AWS service APIs or modify any AWS resources.
It requires no AWS account or credentials; do not add AWS access keys for this server.
`AWS_DOCUMENTATION_PARTITION` selects the docs partition (`aws` global, or `aws-cn` for China); the available tools differ between partitions.
✓This is a fully managed remote server hosted by AWS; it serves public AWS knowledge and requires no AWS account or credentials, so do not add AWS access keys for it.
Because it is a remote server, your queries are sent to the AWS-hosted endpoint; only connect clients you trust to route requests there.
Generative output about AWS APIs and resources can still be wrong; verify guidance against the official AWS documentation it links.
Privacy notes
✓The library names and documentation topics you query are sent to the Context7 service to return matching docs.
Avoid placing secrets or private identifiers in the library queries passed to the server.
✓Indexed documentation, local file contents, URLs, search queries, extracted text, and search results may be exposed to Claude or another MCP client when tools are invoked.
Scraped content (HTML, Markdown, PDF, Office documents, source code) is stored in a local SQLite database on your machine; avoid indexing secrets, private repositories, internal URLs, or sensitive folders unless you intend them to be available through MCP results.
✓Documentation URLs and search terms you ask about are sent to the official AWS documentation search/read endpoints to retrieve content.
The server fetches public documentation pages over HTTPS and returns them as markdown; no private account data is read.
✓Your documentation queries and search terms are sent over HTTPS to the AWS-hosted knowledge endpoint to retrieve content.
The server returns public AWS documentation, code samples, and availability data; it does not read any private account data.
Prerequisites
Node.js 18+ and npx available (verify with: npx --version)
Claude Code or Claude Desktop with MCP support
Internet access so the server can reach the Context7 documentation service
Optional Context7 API key for higher rate limits; the server also works without one
Node.js 22+ with `npx` available.
Start the server with `npx @arabold/docs-mcp-server@latest` before connecting — it listens at http://localhost:6280.
An MCP client such as Claude Code or Claude Desktop.
Python 3.10 or newer installed.
`uv` / `uvx` installed (Astral) to run the published Python package.
An MCP client that supports stdio servers (Claude Code, Claude Desktop, Cursor, Kiro, or VS Code).
Outbound HTTPS access so the server can fetch and search AWS documentation.
An MCP client that supports remote HTTP MCP servers (or `uvx`/`fastmcp` to proxy the endpoint to stdio for clients that don't).
Outbound HTTPS access to the hosted endpoint `https://knowledge-mcp.global.api.aws`.
Install
claude mcp add context7 -- npx -y @upstash/context7-mcp
claude mcp add --transport http docs-mcp http://localhost:6280/sse
uvx awslabs.aws-documentation-mcp-server@latest
uvx fastmcp run https://knowledge-mcp.global.api.aws