Skip to main content
Glama

Server Details

Up-to-date docs for AI agents

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
upstash/context7
GitHub Stars
64,930
Server Listing
Context7 MCP
ChatGPT
–
Claude
Context7

TDQS

A4.4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct roles: resolve-library-id maps a package name to a Context7 ID, while query-docs fetches documentation and code examples. The descriptions explicitly define the ordering relationship, leaving no room for misselection.

Naming Consistency5/5

Both names use kebab-case with a verb_noun structure (query-docs, resolve-library-id). The pattern is fully consistent across the set.

Tool Count4/5

Two tools is minimal, but the server's scope is narrow documentation retrieval, and each tool earns its place as a distinct step in the workflow. It is slightly thin rather than padded.

Completeness4/5

The pair covers the core lifecycle: resolve an identifier, then query docs against it. Coverage is functional, with only minor gaps such as standalone library browsing or version listing beyond what resolution returns.

Available Tools

2 tools
query-docsQuery DocumentationA
Read-onlyIdempotent
Inspect

Retrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework.

You must call 'Resolve Context7 Library ID' tool first to obtain the exact Context7-compatible library ID required to use this tool, UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query.

Do not call this tool more than 3 times per question.

If you know the programming language the user is working in, pass it as language so the results match their setup.

Inputs: query (required), libraryId (required), language.

resolve-library-idResolve Context7 Library IDA
Read-onlyIdempotent
Inspect

Resolves a package/product name to a Context7-compatible library ID and returns matching libraries.

You MUST call this function before 'Query Documentation' tool to obtain a valid Context7-compatible library ID UNLESS the user explicitly provides a library ID in the format '/org/project' or '/org/project/version' in their query.

Each result includes:

  • Library ID: Context7-compatible identifier (format: /org/project)

  • Name: Library or package name

  • Description: Short summary

  • Code Snippets: Number of available code examples

  • Source Reputation: Authority indicator (High, Medium, Low, or Unknown)

  • Benchmark Score: Quality indicator (100 is the highest score)

  • Versions: List of versions if available. Use one of those versions if the user provides a version in their query. The format of the version is /org/project/version.

For best results, select libraries based on name match, source reputation, snippet coverage, benchmark score, and relevance to your use case.

Selection Process:

  1. Analyze the query to understand what library/package the user is looking for

  2. Return the most relevant match based on:

  • Name similarity to the query (exact matches prioritized)

  • Description relevance to the query's intent

  • Documentation coverage (prioritize libraries with higher Code Snippet counts)

  • Source reputation (consider libraries with High or Medium reputation more authoritative)

  • Benchmark Score: Quality indicator (100 is the highest score)

Response Format:

  • Return the selected library ID in a clearly marked section

  • Provide a brief explanation for why this library was chosen

  • If multiple good matches exist, acknowledge this but proceed with the most relevant one

  • If no good matches exist, clearly state this and suggest query refinements

For ambiguous queries, request clarification before proceeding with a best-guess match.

IMPORTANT: Do not call this tool more than 3 times per question. If you cannot find what you need after 3 calls, use the best result you have.

Inputs: query (required), libraryName (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to search a daily-refreshed index of official documentation and read whole sections of it, so answers come from current pages with citations. Covers Claude Code, Cursor, Codex and MCP through two tools over MCP or REST.
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides AI assistants with up-to-date documentation for popular libraries and frameworks, enabling them to generate more accurate code using less common or newly released libraries.
      5
      36
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.