Skip to main content
Glama
3737123Dush

Context7 MCP

by 3737123Dush
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: 'resolve-library-id' resolves package names to library IDs, while 'get-library-docs' fetches documentation using those IDs. There is no overlap in functionality, and the descriptions explicitly define their roles and interdependencies, making it impossible to confuse them.

Naming Consistency5/5

Both tools follow a consistent verb-noun pattern with kebab-case (e.g., 'get-library-docs', 'resolve-library-id'), using clear action verbs ('get', 'resolve') paired with specific nouns. This consistency makes the tool set predictable and easy to understand at a glance.

Tool Count3/5

With only two tools, the server feels thin for its apparent domain of library documentation retrieval. While the tools cover core functions (resolving IDs and fetching docs), typical documentation servers might include additional operations like searching, listing libraries, or managing versions, suggesting a borderline under-scoped surface.

Completeness4/5

The tool set covers the essential workflow for fetching library documentation: resolving IDs and retrieving docs. However, there are minor gaps, such as no tools for searching libraries directly, listing available libraries, or handling documentation updates, which agents might need to work around but don't break core functionality.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources