context7-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| XBY_APIKEY | Yes | 你的实际apikey (Your actual API key) |
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
| Name | Description |
|---|---|
| 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:
Response Format:
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. Use mode='code' (default) for API references and code examples, or mode='info' for conceptual guides, narrative information, and architectural questions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: 'resolve-library-id' handles library identification and matching, while 'get-library-docs' retrieves documentation for a specific library. There is no overlap in functionality, and the descriptions explicitly define their separate roles in the workflow.
Both tools follow a consistent verb-object naming pattern with hyphens ('resolve-library-id', 'get-library-docs'), which is clear and readable. The minor deviation is that 'resolve' and 'get' are different verbs, but this reflects their distinct actions appropriately within the domain.
With only 2 tools, the server feels thin for its apparent domain of library documentation retrieval. A more complete surface might include tools for browsing libraries, searching documentation, or managing queries, but the current set is minimal and may limit agent capabilities.
The tool surface is severely incomplete for library documentation workflows. While it covers resolution and fetching, it lacks tools for operations like searching across libraries, listing available libraries, or handling documentation updates, which are common needs in this domain.