MCP Server for Up-to-Date Library Documentation
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SERPER_API_KEY | Yes | Your Serper API key for searching documentation sites |
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 | Search the latest docs for a given query and library. Supports langchain, openai, and llama-index. Args: query: The query to search for (e.g. "Chroma DB") library: The library to search in (e.g. "langchain") Returns: Text from the docs |
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 possibility of confusion or ambiguity between tools.
Single tool named 'get_docs' follows a clear verb_noun pattern, which is consistent within the set of one.
A single tool for a documentation server is borderline. While a search tool could cover the domain, three distinct libraries suggest at least a tool per library or a discovery tool would be more appropriate.
The server only offers a generic search, lacking any way to list supported libraries, get specific doc structures, or navigate. Agents cannot discover the available actions beyond the single query.