live-docs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIVE_DOCS_MCP_TTL_MS | No | Override the disk cache TTL in milliseconds. Defaults to 24 hours. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_libraryC | Find a documented library by name. |
| search_docsC | Search a library's documentation by topic. |
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 2 tools
search_library targets finding a library by name, while search_docs targets searching within a library's documentation by topic. The two tools have clearly distinct purposes and are complementary rather than overlapping.
Both tool names follow the same search_<noun> snake_case pattern. The naming is predictable and clearly indicates action and target.
Two tools is on the low end for a documentation-focused server, but each tool covers a distinct step in the lookup workflow. It feels minimal yet coherent.
The surface is limited to search operations; there is no way to list libraries, retrieve full documentation content, or navigate doc structure. Agents may be able to find relevant topics but cannot fetch the actual documentation content.