Docs MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_API_KEY | Yes | Your Groq API key | |
| SERPER_API_KEY | Yes | Your Serper 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
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
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_docsA | Search the latest docs for a given query and library. Supports langchain, openai, llama-index and uv. |
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
Only one tool exists, so there is no potential for confusion between tools.
With a single tool, naming consistency is inherently maintained; the name 'get_docs' follows a clear verb_noun pattern.
One tool is minimal but can be acceptable for a narrowly scoped server dedicated solely to documentation search; however, it feels thin for the claimed support of multiple libraries.
The server covers the primary search operation but lacks tools for listing supported libraries, retrieving specific document content, or handling version-specific queries, which are notable gaps.