mintpdf
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MINTPDF_API_KEY | No | Optional MintPDF API key. Raises the monthly render limit. Free key at https://mintpdf.dev | |
| MINTPDF_BASE_URL | No | Point at a self-hosted MintPDF instance instead of the hosted one. | https://mintpdf.dev |
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 |
|---|---|
| generate_pdfA | Renders HTML or Markdown into a PDF and returns a download URL valid for one hour. Provide exactly one of |
| pdf_from_urlA | Loads a public web page and renders it to PDF, returning a download URL valid for one hour. Only public http/https addresses are allowed. |
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 accepts a different input source—local HTML/Markdown versus a public URL—so there is no overlap in usage. An agent can easily choose based on whether the content is available directly or needs to be fetched from the web.
Both tool names are clear and descriptive, but 'generate_pdf' uses a verb-first pattern while 'pdf_from_url' leads with a noun, creating a slight inconsistency. The naming is still readable and understandable, so the deviation is minor.
With only two tools, the server feels minimal for its purpose. It covers the two most common PDF generation scenarios but lacks additional options, making it borderline in terms of scope.
The server covers the essential workflows for PDF generation: creating from direct content or from a live URL. Missing features like advanced styling or batch processing are minor and not critical for the primary use case.