Skip to main content
Glama
renCosta2025

Context7 MCP

by renCosta2025
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CONTEXT7_API_KEYNoYour Context7 API key for authentication. Get yours by creating an account at context7.com/dashboard

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
resolve-library-idA

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

You MUST call this function before 'get-library-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)

  • Trust score (consider libraries with scores of 7-10 more authoritative)

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.

get-library-docsA

Fetches up-to-date documentation for a library. 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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct and non-overlapping purposes: 'resolve-library-id' handles name resolution to obtain a compatible library ID, while 'get-library-docs' fetches documentation using that ID. Their descriptions explicitly define their roles and interdependency, leaving no ambiguity about when to use each tool.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with kebab-case formatting ('resolve-library-id' and 'get-library-docs'), using clear action verbs ('resolve' and 'get') paired with descriptive nouns. This consistency makes the tool set predictable and easy to understand.

Tool Count2/5

With only 2 tools, the server feels under-scoped for its apparent domain of library documentation retrieval. While the tools cover core resolution and fetching, typical documentation systems might include additional operations like searching, listing libraries, or managing documentation versions, making this set feel incomplete for robust agent workflows.

Completeness2/5

The tool set is severely incomplete for a documentation server, lacking essential operations such as searching for libraries, listing available libraries, or handling documentation updates. It forces a rigid two-step process without alternatives, creating potential dead ends if users need broader exploration or management capabilities.

Resources