stdio-context7
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTEXT7_API_KEY | No | Optional API key for Context7 to get higher rate limits. This can be set as an environment variable, or passed as the --api-key CLI argument when running the server. | |
| INACTIVITY_TIMEOUT_MS | No | Optional idle timeout in milliseconds. If set, the server will exit after being idle for this duration. If not set, the server does not time out. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| resolve-library-idB | Resolves a general library name into a Context7-compatible library ID. |
| get-library-docsB | Fetches documentation for a library using a Context7-compatible library ID. |
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 completely distinct purposes: one resolves a library name into an ID, the other fetches docs using that ID. There is no overlap or ambiguity between them.
Both tools follow the same verb_noun pattern with snake_case (resolve-library-id, get-library-docs). Naming is consistent and predictable.
With only 2 tools, the server feels thin for a general-purpose documentation service, especially as it may need more discovery tools. However, for a focused workflow (resolve then fetch), this count is borderline acceptable.
The core workflow of resolving a library ID and fetching its docs is covered without dead ends. A minor gap is lack of searching or listing libraries, but the stated purpose is fetch docs, so the surface is nearly complete.