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
171
MIT
MintPDF
Server Details
Turn HTML or Markdown into a clean, styled PDF and get a download link.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- TrendTweekers/mintpdf
- GitHub Stars
- 1
- Server Listing
- mintpdf
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 |
TDQS
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 |
TDQS
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.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
2 tool updates
- First observed
generate_pdf - First observed
pdf_from_url
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
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
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
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 Connectors
Turn HTML or a live URL into polished PDF and Excel files — hosted downloads, async jobs, history.
Turn an HTML template plus JSON into a finished PDF: a quote, invoice, work order or certificate.
Generate images and PDFs from HTML/CSS, live websites, and reusable templates.
1Turn a description into a shareable, editable PDF — invoices, certificates, reports, resumes.
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.7591MIT
- FlicenseNot gradedqualityDmaintenanceConverts 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-
- AlicenseNot gradedqualityDmaintenanceGenerates 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
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A4/5.0
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.