Skip to content

Context7

by upstash · remote · local (mcpb, npm) · no sign-in to list tools · v4.4.4 · published by GitHub user upstash

Up-to-date docs for AI agents

Read only

2 tools: 2 only read.

Scanned Oct 21, 2026

3 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http context7 https://mcp.context7.com/mcp

Findings

Matches of fixed checks, with the text they matched.

3 info
  • The input schema at properties.query.description mentions "credentials".

    Matched text

    inputSchema.properties.query.description: "...nformation such as API keys, passwords, credentials, personal data, or proprietary code in..."

    What this check looks for
  • The description is 2,006 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...on. If you cannot find what you need after 3 calls, use the best result you have."

    What this check looks for
  • The input schema at properties.query.description mentions "credentials".

    Matched text

    inputSchema.properties.query.description: "...nformation such as API keys, passwords, credentials, personal data, or proprietary code in..."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

2 tools

Only reads 2Claude Code: allow
  • query-docsRetrieves and queries up-to-date documentation and code examples from Context7 for any programming library or framework.1 finding

    Why it is in this group

    • The name "query-docs" says "query": a word for reading.

    Findings

    • Info

      The input schema at properties.query.description mentions "credentials".

      Matched text

      inputSchema.properties.query.description: "...nformation such as API keys, passwords, credentials, personal data, or proprietary code in..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: true
  • resolve-library-idResolves a package/product name to a Context7-compatible library ID and returns matching libraries.2 findings

    Why it is in this group

    • The name "resolve-library-id" says "resolve": a word for reading.

    Findings

    • Info

      The input schema at properties.query.description mentions "credentials".

      Matched text

      inputSchema.properties.query.description: "...nformation such as API keys, passwords, credentials, personal data, or proprietary code in..."

      What this check looks for
    • Info

      The description is 2,006 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...on. If you cannot find what you need after 3 calls, use the best result you have."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 4.4.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http context7 https://mcp.context7.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__context7__resolve-library-id",
      "mcp__context7__query-docs"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as context7. Review it before you use it.