s3-md-pdf-converter-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | HTTP server host | localhost |
| MCP_PORT | No | HTTP server port | 3000 |
| CHROME_ARGS | No | Additional Chrome arguments | --no-sandbox |
| CHROME_PATH | No | Path to Chrome/Chromium executable | |
| PDF_QUALITY | No | PDF quality (1-100) | 100 |
| PDF_TIMEOUT | No | PDF generation timeout (ms) | 30000 |
| MCP_CORS_ORIGIN | No | CORS allowed origins | * |
| MCP_SESSION_TIMEOUT | No | Session timeout (ms) | 3600000 |
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_pdfC | Convert a markdown file to PDF |
| convert_s3_markdown_to_pdfB | Convert a markdown file from S3 bucket to PDF using bucket and key parameters |
| markdown_content_to_pdfC | Convert markdown content directly to PDF |
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 3 tools
The three tools differ by input source: file, S3 object, and content string. However, the generic 'convert_markdown_to_pdf' could be misread as covering S3 or content, though the explicit S3 and content tools reduce ambiguity.
The first two tools follow a convert_X_to_pdf pattern, but the third breaks convention by starting with 'markdown_content' instead of a verb. This mixed style is readable but not fully consistent.
With three input modes (file, S3, content), each tool serves a distinct purpose and justifies its existence. This is an appropriate scope for a specialized markdown-to-PDF converter.
The server covers the core conversion needs for local files, S3 objects, and raw content. Minor gaps like URL-based conversion or batch processing are absent but not critical for the core purpose.