mcp-md-converter
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUPPETEER_EXECUTABLE_PATH | No | Path to a system Chrome/Chromium executable to use instead of Puppeteer's bundled Chromium. Useful for restricted environments. |
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 |
|---|---|
| md_to_pdfA | Render a Markdown file (or raw Markdown text) to a PDF file on disk, using a headless Chromium render. No network or Google account needed. |
| md_to_gdocA | Upload a Markdown file (or raw Markdown text) to Google Drive as a native Google Doc, preserving headings/lists/tables/code formatting. Requires prior one-time auth (run |
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
Each tool targets a distinct output format: PDF via headless Chromium and Google Doc via Drive upload. No overlap in purpose, making selection unambiguous.
Both tool names follow the consistent 'md_to_<format>' pattern, making the naming predictable and clear.
With only two tools, the server feels slightly thin for a general-purpose Markdown converter, but it is still reasonably scoped for the specific PDF and Google Doc workflows.
The server covers two common conversion targets (PDF and Google Doc) with no missing operations within those workflows. Minor gaps exist such as no HTML or DOCX output, but the core purpose is satisfied.