Skip to main content
Glama

Context7 MCP: documentación de código actualizada para cualquier solicitud

Sitio web insignia de herrería

中文文档 한국어 문서 Documentación en español Documentación en francés Documentación en portugués (Brasil) Documentación en italiano Documentación en indonesio Documentación en alemán Documentación en ruso Türkçe Doküman Documentación árabe

❌ Sin contexto7

Los LLM se basan en información obsoleta o genérica sobre las bibliotecas que utilizas. Obtienes:

  • ❌ Los ejemplos de código están desactualizados y se basan en datos de entrenamiento de hace un año.

  • ❌ Las API alucinadas ni siquiera existen

  • ❌ Respuestas genéricas para versiones antiguas de paquetes

Related MCP server: docs-mcp-server

✅ Con Context7

Context7 MCP extrae documentación y ejemplos de código actualizados y específicos de la versión directamente desde la fuente y los coloca directamente en su indicador.

Agregue use context7 a su mensaje en Cursor:

Create a basic Next.js project with app router. use context7
Create a script to delete the rows where the city is "" given PostgreSQL credentials. use context7

Context7 obtiene ejemplos de código y documentación actualizados directamente en el contexto de su LLM.

  • 1️⃣ Escribe tu mensaje de forma natural

  • 2️⃣ Indica al LLM que use context7

  • 3️⃣ Obtenga respuestas de código funcional

Sin cambios de pestañas, sin API alucinantes que no existen, sin generaciones de código obsoleto.

🛠️ Primeros pasos

Requisitos

  • Node.js >= v18.0.0

  • Cursor, Windsurf, Claude Desktop u otro cliente MCP

Instalación mediante herrería

Para instalar Context7 MCP Server para Claude Desktop automáticamente a través de Smithery :

npx -y @smithery/cli install @upstash/context7-mcp --client claude

Instalar en Cursor

Vaya a: Settings -> Cursor Settings -> MCP -> Add new global MCP server

Se recomienda pegar la siguiente configuración en el archivo Cursor ~/.cursor/mcp.json . También puede instalarlo en un proyecto específico creando .cursor/mcp.json en la carpeta de su proyecto. Consulte la documentación de Cursor MCP para obtener más información.

{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": ["-y", "@upstash/context7-mcp"]
    }
  }
}
{
  "mcpServers": {
    "context7": {
      "command": "bunx",
      "args": ["-y", "@upstash/context7-mcp"]
    }
  }
}
{
  "mcpServers": {
    "context7": {
      "command": "deno",
      "args": ["run", "--allow-env", "--allow-net", "npm:@upstash/context7-mcp"]
    }
  }
}

Instalar en Windsurf

Añade esto a tu archivo de configuración de Windsurf MCP. Consulta la documentación de Windsurf MCP para más información.

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

Instalar en VS Code

Añade esto a tu archivo de configuración MCP de VS Code. Consulta la documentación de MCP de VS Code para más información.

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

Instalar en Zed

Se puede instalar mediante Extensiones de Zed o añadirlo a tu settings.json de Zed. Consulta la documentación del Servidor de Contexto de Zed para obtener más información.

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

Instalar en Claude Code

Ejecute este comando. Consulte la documentación de Claude Code MCP para obtener más información.

claude mcp add context7 -- npx -y @upstash/context7-mcp

Instalar en Claude Desktop

Añade esto al archivo claude_desktop_config.json de Claude Desktop. Consulta la documentación de MCP de Claude Desktop para obtener más información.

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

Instalar en BoltAI

Abra la página "Configuración" de la aplicación, navegue hasta "Complementos" e ingrese el siguiente JSON:

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

Una vez guardado, introduzca en el chat get-library-docs seguido de su ID de documentación de Context7 (p. ej., get-library-docs /nuxt/ui ). Encontrará más información en el sitio de documentación de BoltAI . Para BoltAI en iOS, consulte esta guía .

Usando Docker

Si prefiere ejecutar el servidor MCP en un contenedor Docker:

  1. Construya la imagen de Docker:

    Primero, crea un Dockerfile en la raíz del proyecto (o donde prefieras):

    FROM node:18-alpine
    
    WORKDIR /app
    
    # Install the latest version globally
    RUN npm install -g @upstash/context7-mcp
    
    # Expose default port if needed (optional, depends on MCP client interaction)
    # EXPOSE 3000
    
    # Default command to run the server
    CMD ["context7-mcp"]

    Luego, crea la imagen usando una etiqueta (p. ej., context7-mcp ). Asegúrate de que Docker Desktop (o el demonio de Docker) esté ejecutándose. Ejecuta el siguiente comando en el mismo directorio donde guardaste el Dockerfile :

    docker build -t context7-mcp .
  2. Configurar su cliente MCP:

    Actualice la configuración de su cliente MCP para usar el comando Docker.

    Ejemplo para cline_mcp_settings.json:

    {
      "mcpServers": {
        "Сontext7": {
        "autoApprove": [],
        "disabled": false,
        "timeout": 60,
          "command": "docker",
          "args": ["run", "-i", "--rm", "context7-mcp"],
          "transportType": "stdio"
        }
      }
    }

    Nota: Esta es una configuración de ejemplo. Consulte los ejemplos específicos de su cliente MCP (como Cursor, VS Code, etc.) que aparecen anteriormente en este archivo README para adaptar la estructura (p. ej., mcpServers vs. servers ). Además, asegúrese de que el nombre de la imagen en args coincida con la etiqueta utilizada durante el comando docker build .

Instalar en Windows

La configuración en Windows es ligeramente diferente a la de Linux o macOS ( en el ejemplo se usa Cline ). El mismo principio se aplica a otros editores; consulte la configuración de command y args .

{
  "mcpServers": {
    "github.com/upstash/context7-mcp": {
      "command": "cmd",
      "args": [
        "/c",
        "npx",
        "-y",
        "@upstash/context7-mcp"
      ],
      "disabled": false,
      "autoApprove": []
    }
  }
}

Variables de entorno

  • DEFAULT_MINIMUM_TOKENS : Establece el recuento mínimo de tokens para la recuperación de documentación (predeterminado: 10000).

Ejemplos:

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

Herramientas disponibles

  • resolve-library-id : resuelve un nombre de biblioteca general en un ID de biblioteca compatible con Context7.

    • libraryName (obligatorio)

  • get-library-docs : obtiene la documentación de una biblioteca utilizando un ID de biblioteca compatible con Context7.

    • context7CompatibleLibraryID (obligatorio)

    • topic (opcional): centra la documentación en un tema específico (por ejemplo, "enrutamiento", "ganchos")

    • tokens (opcional, valor predeterminado: 10 000): Número máximo de tokens a devolver. Los valores inferiores al valor DEFAULT_MINIMUM_TOKENS configurado o al valor predeterminado de 10 000 se incrementan automáticamente a ese valor.

Desarrollo

Clonar el proyecto e instalar las dependencias:

bun i

Construir:

bun run build

Ejemplo de configuración local

{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": ["tsx", "/path/to/folder/context7-mcp/src/index.ts"]
    }
  }
}

Pruebas con MCP Inspector

npx -y @modelcontextprotocol/inspector npx @upstash/context7-mcp

Solución de problemas

ERR_MÓDULO_NO_ENCONTRADO

Si ve este error, intente utilizar bunx en lugar de npx .

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

A menudo, esto resuelve problemas de resolución de módulos, especialmente en entornos donde npx no instala o resuelve los paquetes correctamente.

Problemas de resolución del ESM

Si encuentra un error como: Error: Cannot find module 'uriTemplate.js' intente ejecutar con el indicador --experimental-vm-modules :

{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": [
        "-y",
        "--node-options=--experimental-vm-modules",
        "@upstash/context7-mcp"
      ]
    }
  }
}

Problemas con TLS/certificados

Utilice el indicador --experimental-fetch con npx para evitar problemas relacionados con TLS:

{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": [
        "-y",
        "--node-options=--experimental-fetch",
        "@upstash/context7-mcp"
      ]
    }
  }
}

Errores del cliente MCP

  1. Intente agregar @latest al nombre del paquete.

  2. Intente utilizar bunx como alternativa.

  3. Intente utilizar deno como alternativa.

  4. Asegúrate de estar usando Node v18 o superior para tener soporte de búsqueda nativo con npx .

Descargo de responsabilidad

Los proyectos de Context7 son aportaciones de la comunidad y, si bien nos esforzamos por mantener una alta calidad, no podemos garantizar la precisión, integridad ni seguridad de toda la documentación de la biblioteca. Los proyectos listados en Context7 son desarrollados y mantenidos por sus respectivos propietarios, no por Context7. Si encuentra contenido sospechoso, inapropiado o potencialmente dañino, utilice el botón "Reportar" en la página del proyecto para notificarnos de inmediato. Nos tomamos muy en serio todos los reportes y revisaremos el contenido marcado con prontitud para mantener la integridad y seguridad de nuestra plataforma. Al usar Context7, usted reconoce que lo hace bajo su propia discreción y riesgo.

Conéctate con nosotros

Manténgase actualizado y únase a nuestra comunidad:

  • 📢 Síguenos en X para conocer las últimas noticias y actualizaciones

  • 🌐 Visita nuestro sitio web

  • 💬 Únete a nuestra comunidad de Discord (si corresponde)

Contexto7 en los medios

Historia de las estrellas

Gráfico de la historia de las estrellas

Licencia

Instituto Tecnológico de Massachusetts (MIT)

Available Tools

2 tools
query-docsQuery DocumentationA
Read-only
Inspect

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

You must call 'resolve-library-id' 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.

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 information you have.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesThe question or task you need help with. Be specific and include relevant details. Good: 'How to set up authentication with JWT in Express.js' or 'React useEffect cleanup function examples'. Bad: 'auth' or 'hooks'. IMPORTANT: Do not include any sensitive or confidential information such as API keys, passwords, credentials, or personal data in your query.
libraryIdYesExact Context7-compatible library ID (e.g., '/mongodb/docs', '/vercel/next.js', '/supabase/supabase', '/vercel/next.js/v14.3.0-canary.87') retrieved from 'resolve-library-id' or directly from user query in the format '/org/project' or '/org/project/version'.

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds behavioral context beyond the readOnlyHint annotation: the 3-call limit, prerequisite step, and warning against sensitive data. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short paragraphs each serving a distinct purpose: purpose, prerequisite, limitation. Front-loaded with the core action, no redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers prerequisite, usage limit, and parameter guidance. Lacks explicit description of output format, but since the tool retrieves documentation and code examples, the output type is reasonably inferable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema provides 100% coverage with detailed descriptions for both parameters. The tool description reinforces the relationship between libraryId and resolve-library-id but adds little semantic meaning beyond what's already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves and queries documentation and code examples from Context7 for any library, distinguishing it from the sibling 'resolve-library-id' tool which is for obtaining library IDs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly instructs to use 'resolve-library-id' first unless user provides library ID, and imposes a 3-call limit per question, providing clear guidance on when and how many times to use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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

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

You MUST call this function before 'query-docs' 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.

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.

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesThe user's original question or task. This is used to rank library results by relevance to what the user is trying to accomplish. IMPORTANT: Do not include any sensitive or confidential information such as API keys, passwords, credentials, or personal data in your query.
libraryNameYesLibrary name to search for and retrieve a Context7-compatible library ID.

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=true, which is consistent with the tool's purpose. The description adds important behavioral details beyond annotations, such as a 3-call limit per question, handling of ambiguous queries, and a warning not to include sensitive information in the 'query' parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with clear sections, but it is somewhat lengthy. It front-loads the essential purpose and usage note, but the selection process details could be more succinct. Still, it remains clear and organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given there is no output schema, the description adequately explains the response format. It covers edge cases like multiple matches, no matches, and ambiguous queries, providing complete guidance for the agent to handle various scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds value by explaining the role of each parameter: 'libraryName' is the name to search for, and 'query' is the user's original question used for ranking. It also includes a critical warning about sensitive data in 'query', which enhances understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states that the tool resolves a package/product name to a Context7-compatible library ID. It distinguishes itself from the sibling tool 'query-docs' by noting it must be called first, and includes specific details about selection criteria and response format.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly specifies when to call this tool: before 'query-docs' unless the user provides a library ID in a specific format. It also provides a detailed selection process and response format, guiding the agent on how to use the tool correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.8
    • Addedquery-docs
    • Addedresolve-library-id
  2. 2 tool updatesv1.0.6
    • Removedquery-docs
    • Removedresolve-library-id
  3. 3 tool updatesv1.0.1
    • Removedget-library-docs
    • Addedquery-docs
    • Changedresolve-library-id2 fields changed
      • addedInput schema / properties / query
        Added value: +{
        +  "description": "The user's original question or task. This is used to rank library results by relevance to what the user is trying to accomplish. IMPORTANT: Do not include any sensitive or confidential information such as API keys, passwords, credentials, or personal data in your query.",
        +  "type": "string"
        +}
      • changedInput schema / required
        Previous value: -[
        -  "libraryName"
        -]New value: +[
        +  "query",
        +  "libraryName"
        +]
  4. 2 tool updatesv1.0.0
    • First observedget-library-docs
    • First observedresolve-library-id

TDQS

A4.6/5.0
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

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

  • A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…

  • The Cortex MCP server provides read-only access to real-time engineering context from the Cortex developer portal, allowing AI coding assistants to answer natural language questions about your organization's catalog (microservices, libraries, domains, teams, infrastructure), scorecards (engineering standards and best practices), initiatives (goals and deadlines), and Engineering Intelligence metrics. It includes tools for querying documentation, tracking personal entities, and accessing AI-assisted insights across the entire Cortex ecosystem.

  • A Model Context Protocol server for Wix AI tools

  • The AWS Knowledge MCP server is a fully managed remote Model Context Protocol server that provides real-time access to official AWS content in an LLM-compatible format. It offers structured access to AWS documentation, code samples, blog posts, What's New announcements, Well-Architected best practices, and regional availability information for AWS APIs and CloudFormation resources. Key capabilities include searching and reading documentation in markdown format, getting content recommendations, listing AWS regions, and checking regional availability for services and features.

Related MCP Servers

  • 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
    -
  • 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.
    3,262
    1,711
    MIT
  • 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

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/upstash/context7'

If you have feedback or need assistance with the MCP directory API, please join our Discord server