MCP Docs Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_API_KEY | No | Your Groq API key, used by the example client (optional for running the server alone). | |
| SERPER_API_KEY | Yes | Your Serper API key, used to search documentation via the web. |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_docsD | – |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlapping purposes. The single tool is trivially distinct.
The only tool name 'get_docs' follows a clear verb_noun convention. Consistency is trivially maintained with a single tool.
A single tool feels thin for a documentation server, but it is at the low end of borderline. The count is not egregious but likely insufficient for a full-featured docs experience.
The tool name suggests retrieving documentation, but there is no listing, searching, or other navigation capability. This creates significant gaps for a docs server, and the lack of a description makes the surface even more unclear.