DOC-Intelligence-MCP-SERVER
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GROQ_API_KEY | Yes | API key for Groq (get from Groq Console) | |
| SERPER_API_KEY | Yes | API key for Google Serper (get from Serper.dev) |
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 official documentation to answer developer queries. Use this tool whenever the user asks questions about uv, openai, langchain, or llama-index. |
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 risk of ambiguity or overlap.
With a single tool, naming is trivially consistent; the name 'get_docs' clearly conveys its purpose.
One tool for a broad domain (multiple libraries) feels minimal; while it can handle many queries, it offers no specialized operations.
The server covers basic documentation search, but lacks other functionality like listing sources or performing updates, which may be needed for comprehensive querying.