mdgen-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MDGEN_TOKEN | Yes | Your mdgen personal access token | |
| MDGEN_API_URL | No | mdgen API base URL | https://api.mdgen.app |
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 |
|---|---|
| list_documentsA | List the current user's saved mdgen documents (id, title, mode, updatedAt). |
| read_documentA | Get the full Markdown and metadata of a document by id. |
| create_documentA | Create a new mdgen document. Returns the created document id. |
| update_documentA | Update a document by id. Only the provided fields change; others are preserved. |
| delete_documentB | Delete a document by id. |
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 5 tools
Each tool targets a distinct operation (list, read, create, update, delete) on documents, with no overlap. An agent can clearly select the appropriate tool based on the desired action.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., list_documents, create_document). The naming is predictable and uniform.
With exactly 5 tools, the set is well-scoped for a document management service, covering the essential operations without unnecessary bloat.
The tool set provides full CRUD lifecycle coverage for documents: list, read, create, update, and delete. No obvious gaps exist for the stated domain.