Statly Docs MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Statly Docs MCP Server show me JavaScript code example for capturing errors"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Statly Docs MCP Server
Model Context Protocol server for Statly documentation. Enables AI agents to search and retrieve Statly SDK and API documentation.
Installation
npm install statly-docs-mcpUsage with Claude Desktop
Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"statly-docs": {
"command": "npx",
"args": ["statly-docs-mcp"]
}
}
}Usage with Claude Code
claude mcp add statly-docs -- npx statly-docs-mcpAvailable Tools
search_docs
Search Statly documentation for a topic.
query: "express integration"get_sdk_reference
Get SDK API reference for a specific language.
language: "javascript" | "python" | "go"get_code_example
Get a code example for a specific use case.
language: "javascript" | "python" | "go"
topic: "installation" | "init" | "capture_error" | "user_context" | "breadcrumbs"get_api_reference
Get REST API reference information.
Resources
The server provides access to the llms.txt documentation:
uri: statly://docs/llms.txtDevelopment
pnpm install
pnpm build
pnpm startAvailable Tools
4 toolsget_api_referenceC
Get REST API reference information
Inputs: no named parameters.
get_code_exampleB
Get a code example for a specific use case
Inputs: language (required), topic (required).
get_sdk_referenceB
Get SDK API reference for a specific language
Inputs: language (required).
search_docsC
Search Statly documentation for a topic
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Access and search Branch's official API documentation directly within any AI agent or client.
Tailor Platform for AI assistants: search, list and read the platform documentation.
Find, write, publish and check pages and API references in your DeveloperHub docs from an AI client
Versioned documentation registry and semantic search for AI tools and coding assistants.