A
licenseA
qualityA
maintenanceEnables creating PDF documents (invoices, certificates, reports, etc.) from natural language descriptions, returning a shareable link to preview and edit the document.
1
129
MIT
MintPDF
Server Details
Turn HTML or Markdown into a clean, styled PDF and get a download link.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- TrendTweekers/mintpdf
- GitHub Stars
- 0
- Server Listing
- mintpdf
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4/5.0
Tool DescriptionsA
Average 3.8/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation5/5
generate_pdf clearly takes HTML/Markdown input while pdf_from_url takes a URL. There is no overlap between sourcing content from raw text versus a web page, so an agent can unambiguously select the right tool.
Naming Consistency4/5
Names are descriptive and follow a predictable format for the most part. generate_pdf uses verb_noun, while pdf_from_url swaps the order to noun_preposition_noun, creating a minor inconsistency but no confusion.
Tool Count5/5
Two tools perfectly cover the two primary ways to generate a PDF: from provided content or from a public URL. The scope is tight and every tool earns its place.
Completeness4/5
The server covers the two core PDF generation workflows adequately. Minor gaps exist around customization options like page margins or metadata, but these are not essential for basic generation and can be worked around.
Available Tools
2 toolsgenerate_pdfGenerate a PDF from HTML or MarkdownAInspect
Renders HTML or Markdown into a PDF and returns a download URL (valid for 1 hour). Provide exactly one of html or markdown. Markdown gets a clean default stylesheet, so it is the fastest way to produce a good-looking document.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| html | No | Full HTML document or fragment to render | |
| format | No | Paper size, default A4 | |
| margin | No | Page margin on all sides, e.g. "18mm" | |
| markdown | No | Markdown content to render with the default stylesheet | |
| landscape | No | Landscape orientation, default false | |
| footerText | No | Small footer text on every page | |
| headerText | No | Small header text on every page | |
| pageNumbers | No | Show page numbers in the footer |
Tool Definition Quality
A3.7/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the 1-hour URL expiry and the default Markdown stylesheet, but does not cover error conditions (e.g., providing both inputs), size limits, or asynchronous behavior, leaving notable gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the primary action and output. It provides actionable guidance on input selection without any redundant or filler content.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 8 parameters and no output schema, the description covers the core behavior (input, output, expiry) and parameters are fully documented in the schema. It omits details about error handling, but overall the description is sufficiently complete for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% for all 8 parameters, so baseline is 3. The description adds value by explicitly stating the mutual exclusivity of html and markdown, a constraint not captured in the schema, and clarifies the Markdown styling advantage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose4/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool renders HTML or Markdown into a PDF and returns a download URL, specifying the exact input types and output. It does not explicitly distinguish from the sibling pdf_from_url, so it misses the 'distinguishes from siblings' criterion for a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives usage context by requiring exactly one of html or markdown and recommending Markdown for quick styling, but it does not mention when to use this tool instead of pdf_from_url or provide any exclusion criteria for alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
pdf_from_urlGenerate a PDF from a public URLAInspect
Loads a public web page and renders it to PDF. Returns a download URL valid for 1 hour. Only public http/https URLs are allowed.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | Public http(s) URL of the page to render | |
| format | No | Paper size, default A4 | |
| margin | No | Page margin on all sides, e.g. "18mm" | |
| landscape | No | Landscape orientation, default false | |
| footerText | No | Small footer text on every page | |
| headerText | No | Small header text on every page | |
| pageNumbers | No | Show page numbers in the footer |
Tool Definition Quality
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full transparency burden. It usefully discloses that a download URL valid for 1 hour is returned and that only public URLs are allowed. However, it omits failure modes, rate limits, or handling of inaccessible URLs, leaving notable behavioral gaps.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, consisting of three short sentences that front-load the core action before adding output and constraint details. Every sentence contributes essential information without redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 7 parameters and no output schema, the description covers the essential output (download URL with validity) and a key constraint (public URLs). It does not explain error handling or default parameter behaviors, but these are partly covered by the schema, making it fairly complete for a tool of this complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All 7 parameters have descriptions in the schema (100% coverage), so the description adds no additional semantic value to the parameters. The mention of public http/https URLs mirrors the schema's url description, and no extra meaning is provided for formatting options like margin or landscape.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it loads a public web page and renders it to PDF, specifying a specific verb and resource. It distinguishes itself from the generic sibling generate_pdf by emphasizing URL input, leaving no ambiguity about the tool's function.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for public URL-based PDF generation and explicitly restricts to public http/https URLs, providing a when-not scenario. However, it does not explicitly mention the alternative sibling tool or define broader usage contexts, leaving differentiation to the reader rather than stating it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- AlicenseAqualityCmaintenanceGenerate professional PDFs from Claude, Cursor, and other AI tools. Create invoices, contracts, reports, and certificates from templates or inline HTML markup.7431MIT
- Flicense-qualityDmaintenanceConverts Markdown files and raw content into professionally styled PDFs with full support for Mermaid diagrams and syntax highlighting. It offers customizable page formats, margins, and modern typography for high-quality document generation.11
- Alicense-qualityDmaintenanceGenerates PDF documents from HTML or Markdown content with customizable page size, margins, and orientation, supporting pay-per-call payments via x402.MIT
Try in Browser
Your Connectors
Sign in to create a connector for this server.