Skip to main content
Glama
upstash

Context7 MCP

by upstash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Context7 MCP

Related Servers

  • Documentation Search MCP

    gemini2026
    A
    license
    C
    quality
    C
    maintenance
    A Model Context Protocol server that enables intelligent searching across documentation for 30+ programming libraries and frameworks, fetching relevant information from official sources.
    23
    8
    MIT

  • ScriptDocs MCP Server

    Timwal78
    A
    license
    A
    quality
    B
    maintenance
    A Model Context Protocol server that provides AI coding agents with real, live, source-cited documentation for npm, PyPI, and Cargo packages, including READMEs, metadata, vulnerability checks, and package search.
    5
    77 npm
    MIT

  • docs-mcp-server

    arabold
    A
    license
    Not graded
    quality
    A
    maintenance
    A Model Context Protocol (MCP) server that scrapes, indexes, and searches documentation for third-party software libraries and packages, supporting versioning and hybrid search.
    1,446 npm
    1,788
    MIT

  • Context7 MCP

    3737123Dush
    A
    license
    A
    quality
    D
    maintenance
    Provides LLMs with up-to-date, version-specific documentation and code examples directly from library sources, eliminating outdated training data and hallucinated APIs by fetching current documentation at prompt time.
    2
    485,755 npm
    MIT

  • Library Docs MCP Server

    vikramdse
    F
    license
    B
    quality
    D
    maintenance
    An MCP server that fetches real-time documentation for popular libraries like Langchain, Llama-Index, MCP, and OpenAI, allowing LLMs to access updated library information beyond their knowledge cut-off dates.
    1
    3
    -
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.6/5.0

Scored across 2 tools

Disambiguation5/5

Each tool has a distinct and complementary purpose: one resolves library names to IDs, the other queries documentation using that ID. There is no overlap.

Naming Consistency5/5

Both tools follow the same verb_noun pattern with snake_case: 'resolve-library-id' and 'query-docs'. Consistent and predictable.

Tool Count4/5

With only two tools, the surface is minimal but still covers the core workflow for querying documentation. It is slightly thin but appropriate for a focused server.

Completeness4/5

The two tools form a complete workflow: resolve then query. No obvious gaps for the stated purpose, though additional tools like list_libraries could enhance completeness.

Maintenance

ActivityActive
ResponsivenessResponsive

Resources