Skip to main content
mcpSource-backed

Context7 MCP Server for Claude

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.

by Upstash · submitted by glorydavid03023·added 2026-06-02·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/upstash/context7, https://context7.com
Safety notes
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.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

2 minutes

Adoption plan

Balanced adoption plan

Current risk score 16/100. Use staged verification before broader rollout.

Risk 16

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    Listing has review metadata.

    Done
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Required evidence gates are covered (5/6 signals complete).

Risk 15

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Present

Review metadata is present.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required evidence gates are covered for this preset.

Decision timeline

Decision timeline · balanced

5/6 steps complete with no blocking gaps for this preset.

Risk 14

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is available.

Done

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

No required blockers for this timeline preset.

Prerequisite readiness

Prerequisite readiness

4 prerequisites to line up before setup. Have accounts and credentials ready first.

0/4 ready
Account & credentials1Install & runtime1Network & hosting1General12 minutes

Safety & privacy surface

Safety & privacy surface

2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens, network access, third-party handling.

3 areas
  • SafetyNetwork accessMakes outbound network requests to the Context7 service to resolve libraries and fetch documentation.
  • SafetyThird-party handlingReturned documentation and code snippets are third-party content; review examples before running them in your project.
  • PrivacyThird-party handlingThe library names and documentation topics you query are sent to the Context7 service to return matching docs.
  • PrivacyCredentials & tokensAvoid placing secrets or private identifiers in the library queries passed to the server.

Safety notes

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

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

Schema details

Install type
cli
Troubleshooting
Yes
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
2 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "context7": {
    "command": "npx",
    "args": ["-y", "@upstash/context7-mcp"]
  }
}

About this resource

Content

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

  1. Make sure Node.js 18+ is installed (verify with npx --version).
  2. Run: claude mcp add context7 -- npx -y @upstash/context7-mcp
  3. Verify the server is registered: claude mcp list
  4. Add "use context7" to a coding prompt to confirm docs are pulled in.

Claude Desktop

  1. Open your Claude Desktop configuration file.
  2. Add the Context7 server to the mcpServers section using the configuration below.
  3. Restart Claude Desktop.
  4. Confirm the server appears and ask a library question with "use context7".

Configuration

{
  "context7": {
    "command": "npx",
    "args": ["-y", "@upstash/context7-mcp"]
  }
}

Examples

Ground an answer in current docs

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.

Source citations

Add this badge to your README

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.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/context7-mcp-server.svg)](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).

Field

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.

Open dossier

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.

Open dossier

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.

Open dossier

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.

Open dossier
Next steps
Trust
Review statusReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewedReviewedMaintainer reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersglorydavid03023jaso0n0818jaso0n0818
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandAWS Labs logoAWS LabsAWS Labs logoAWS Labs
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorUpstasharaboldAWS LabsAWS Labs
Added2026-06-022026-06-182026-06-202026-06-21
Platforms
Harness
Source repo
Safety notesMakes 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 notesThe 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
Config
{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/context7-mcp"
      ],
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "docs-mcp-server": {
      "type": "sse",
      "url": "http://localhost:6280/sse"
    }
  }
}
{
  "mcpServers": {
    "awslabs.aws-documentation-mcp-server": {
      "command": "uvx",
      "args": ["awslabs.aws-documentation-mcp-server@latest"],
      "env": {
        "FASTMCP_LOG_LEVEL": "ERROR",
        "AWS_DOCUMENTATION_PARTITION": "aws"
      },
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "aws-knowledge-mcp-server": {
      "url": "https://knowledge-mcp.global.api.aws",
      "type": "http"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.