AUTOMATIONSWITCH
VendorDev Tools

Context7

by Upstash

Documentation quality layer that fetches current, version-specific library documentation. Resolves library IDs and returns focused doc sections so your agent works with accurate API references.

8,500·2 tools·Released FEB 2026·MIT
npx @upstash/context7-mcp
Share:

INSTALL THIS SERVER

{ "mcpServers": { "context7": { "command": "npx", "args": ["-y", "@upstash/context7-mcp@latest"] } } }
PrereqClaude Desktop v1.4+ . No auth required

2 TOOLS AVAILABLE

resolve-library-id
Resolve a library name to its Context7 ID
get-library-docs
Fetch current documentation for a library

OUR ASSESSMENT

Strengths
  • Fetches current, version-specific documentation
  • Covers major frameworks and libraries (React, Next.js, Prisma, etc.)
  • Lightweight (2 tools, minimal overhead)
  • No authentication required
Weaknesses
  • Coverage depends on the Context7 index (growing, with selective library coverage)
  • Documentation quality varies by library
Security Notes

Read-only. Fetches public documentation from the Context7 cloud index. No credentials or sensitive data involved.

Best For

Keeping your agent current on library APIs and framework documentation

TECHNICAL DETAILS

Language
typescript
Transport
stdio
Clients
Claude DesktopClaude CodeCursorVS CodeWindsurfCline
License
MIT
GitHub
upstash/context7 · ★ 8,500
npm
@upstash/context7-mcp
Last Release
v1.0.8APR 22, 2026
First Released
FEB 10, 2026

ADOPTION METRICS

// GitHub Stars
8,500
700 this week (+9.0%)

// Reading thisThe fastest-growing MCP by star velocity. Context7 solves a universal problem (stale docs) which drives broad adoption.

// Weekly Downloads
42,800
4,600 this week

// Reading thisDownloads are spread evenly across all client types. The "install once, always current" value proposition drives retention.

// Popularity Rank
#3
Globally · #3 in Dev Tools

// Reading this#3 in Dev Tools. Globally #3 reflects the cross-cutting nature of documentation access.

SOURCES & VERIFICATION

We don't take any single directory's word for it. Before scoring, we cross-reference 2 public MCP sources, install the server ourselves against the clients we cover, and record when we last re-verified.

01
Discovered
PulseMCP
First indexed APR 24, 2026
02
Cross-referenced
2 directories
PulseMCP, Smithery
03
Verified against
Claude Desktop + Cursor + Claude Code
Installed and tested across clients
04
Last re-checked
APR 22, 2026
Weekly re-verification
// How other directories see it

The same server, 2 different lenses. We reconcile these signals into our editorial score, which is why our number sometimes diverges from a directory-aggregate star count.

SourceTheir ratingTheir star countTheir downloadsLast synced
AutomationSwitch This page4editorial8,50042.8K / wkAPR 22, 2026
PulseMCP4.2 community1,50014.6K / wkAPR 21, 2026
Smithery4.3 installs1,50016.2K installsAPR 20, 2026

// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.

// Get in touch

DISCUSS YOUR
MCP REQUIREMENTS.

Evaluating a server, scoping an internal deployment, or working out whether MCP is the right fit at all. Start the conversation and we will point you at the right piece of the ecosystem.

Discuss Your MCP Requirements →