md-to-pdf-with-mermaid-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUPPETEER_EXECUTABLE_PATH | No | Path to an existing browser executable for Puppeteer to use, useful in environments where automatic Chromium download is restricted. |
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 |
|---|---|
| convert_markdown_to_pdfA | 마크다운 파일(.md)을 PDF(.pdf)로 변환합니다. 마크다운 내부에 Mermaid 다이어그램이 포함되어 있어도 렌더링됩니다. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined and distinct by default.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'convert_markdown_to_pdf' follows a clear verb_noun pattern, but consistency cannot be assessed across multiple tools.
A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete surface. For a markdown-to-PDF conversion server, additional tools (e.g., for configuration, validation, or batch processing) would enhance coherence.
The tool covers the core conversion task well, including Mermaid diagram support. However, there are notable gaps, such as lack of tools for input validation, output customization (e.g., page settings), or handling multiple files, which could limit agent workflows.