Doccler 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hello_docclerA | Say hello to Doccler and verify the connection is working |
| search_docsB | Search your Doccler documentation by keyword or semantic query |
| create_docB | Create new documentation in Doccler. Use list_spaces first to see available spaces. |
| generate_docB | Analyze code and generate documentation using AI |
| publish_docB | Publish or unpublish a Doccler document |
| list_spacesA | List all available spaces (document categories) in Doccler |
| get_docB | Get the content of a specific Doccler document |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| document_code | Generate comprehensive documentation for code |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| docs://list |
TDQS
Scored across 7 tools
All tools have clear, distinct purposes. The health check, search, CRUD for docs, spaces listing, and publishing are each unique and non-overlapping.
All tool names follow a consistent verb_noun snake_case pattern (e.g., search_docs, create_doc, list_spaces), making them predictable and easy to navigate.
With 7 tools covering health check, search, CRUD, AI generation, and space management, the count is well-scoped for a documentation server without being excessive or sparse.
The tool set covers most core documentation operations but is missing explicit update and delete tools, which are minor but notable gaps that an agent would need to work around.