MD-PDF 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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_markdown_to_pdfA | Convert Markdown content to PDF with customizable formatting options. Args: working_dir: Absolute path to the working directory for file operations markdown_content: The markdown content to convert to PDF output_filename: Name of the output PDF file relative to working_dir (default: output.pdf) size: Output size - 's' (small/compact), 'm' (medium), 'l' (large/detailed) (default: l) pdf_engine: PDF engine to use - weasyprint or pdflatex (default: weasyprint) Returns: A message indicating success or failure of the conversion |
| convert_markdown_file_to_pdfA | Convert a Markdown file to PDF with customizable formatting options. Args: working_dir: Absolute path to the working directory for file operations markdown_file_path: Path to the markdown file relative to working_dir output_filename: Name of the output PDF file relative to working_dir (if not provided, uses same name as input with .pdf extension) size: Output size - 's' (small/compact), 'm' (medium), 'l' (large/detailed) (default: l) pdf_engine: PDF engine to use - weasyprint or pdflatex (default: weasyprint) Returns: A message indicating success or failure of the conversion |
| convert_pdf_to_markdownB | Convert a PDF file to Markdown format. Args: pdf_file_path: Path to the PDF file to convert output_filename: Name of the output Markdown file (if not provided, uses same name as input with .md extension) Returns: A message indicating success or failure of the conversion |
| extract_text_from_pdfA | Extract text content from a PDF file without conversion to Markdown. Args: working_dir: Absolute path to the working directory for file operations pdf_file_path: Path to the PDF file relative to working_dir page_numbers: Page numbers to extract - "all" for all pages, or comma-separated numbers like "1,3,5" or "1-5" Returns: The extracted text content from the PDF |
| get_pdf_infoC | Get information about a PDF file (number of pages, metadata, etc.). Args: working_dir: Absolute path to the working directory for file operations pdf_file_path: Path to the PDF file relative to working_dir Returns: Information about the PDF file |
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
There is significant overlap between convert_markdown_file_to_pdf and convert_markdown_to_pdf, which differ only in input type (file vs. content) and could easily be confused. The other three tools have distinct purposes (PDF to Markdown conversion, text extraction, and metadata retrieval), but the two Markdown-to-PDF tools create ambiguity.
All tool names follow a consistent verb_noun pattern with clear, descriptive actions (convert, extract, get) and objects (markdown_file_to_pdf, pdf_to_markdown, text_from_pdf, pdf_info). The naming is uniform and predictable throughout the set.
With 5 tools, this server is well-scoped for its PDF/Markdown conversion domain. The count is appropriate, covering key operations without being overly sparse or bloated, and each tool appears to serve a distinct functional role in the workflow.
The toolset provides solid coverage for PDF and Markdown interactions, including conversion in both directions, text extraction, and metadata retrieval. A minor gap exists in lacking tools for editing or manipulating PDFs/Markdown files beyond conversion, but core workflows are well-supported.