Statly Docs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsC | Search Statly documentation for a topic |
| get_sdk_referenceB | Get SDK API reference for a specific language |
| get_code_exampleB | Get a code example for a specific use case |
| get_api_referenceC | Get REST API reference information |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Statly LLMs Documentation | Complete documentation for AI agents in llms.txt format |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: get_api_reference for REST API details, get_code_example for code snippets, get_sdk_reference for language-specific SDKs, and search_docs for general documentation search. There is no overlap or ambiguity between these functions, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with 'get_' or 'search_' prefixes and snake_case formatting. This uniformity (get_api_reference, get_code_example, get_sdk_reference, search_docs) makes the set predictable and easy to navigate, with no deviations in style.
With 4 tools, the count is appropriate for a documentation-focused server, covering key areas like API references, code examples, SDKs, and search. It is slightly lean but reasonable, as each tool serves a distinct and essential function without feeling bloated or incomplete.
The tool set covers the core documentation domain well, including references, examples, and search. A minor gap exists in lacking update or management tools (e.g., for documentation content), but this is acceptable for a read-only documentation server, and agents can still perform typical lookup tasks effectively.