Search Docs MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERPER_API_KEY | Yes | The Serper API key for web search functionality. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_docsA | |
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 confusion or overlap between tools.
With a single tool, naming consistency is not a concern; the name 'get_docs' clearly indicates its purpose.
A single tool for searching docs is very minimal; it may be appropriate if the scope is strictly limited, but typically expects additional tools for browsing or managing documentation.
The tool only supports searching docs by query and library; missing capabilities like listing supported libraries, retrieving full documents, or filtering results, which limits its utility.