A
license-
qualityD
maintenanceEnables PDF and image generation from templates, JSON, HTML, or URLs through the PDF Gen Studio API. Supports rendering, template management, and multiple output formats.
7
1
MIT
PdfBroker.io
by io.pdfbroker
Server Details
Cloud PDF generation from HTML, CSS and XSL-FO, with PDF/A and PDF/UA support.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
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.1/5.0
Tool DescriptionsA
Average 4.4/5 across 2 of 2 tools scored.
Server CoherenceA
Disambiguation4/5
The two tools both convert HTML to PDF, which could cause initial confusion. However, the descriptions clearly differentiate them: one for standards-compliant documents, the other for JavaScript rendering and fillable forms. The 'wk' suffix is somewhat cryptic but explained.
Naming Consistency4/5
Both tools follow an html_to_pdf pattern, with a '_wk' suffix for the second. This is fairly consistent, though the suffix is not intuitively descriptive and could be clearer.
Tool Count4/5
With only two tools, the server is minimal but focused. For a specialized HTML-to-PDF service, this is reasonable, though slightly thin for broader PDF operations.
Completeness3/5
The server covers two major HTML-to-PDF rendering engines, which is good for its narrow scope. However, it lacks other common PDF operations like merging, splitting, or direct URL conversion, leaving notable gaps.
Available Tools
2 toolshtml_to_pdfAInspect
Convert HTML and CSS to a PDF document using the WeasyPrint rendering engine. Supports PDF/A-1b, PDF/A-3b, and PDF/UA compliance standards. Best for professional documents: invoices, reports, certificates, contracts, and accessible documents. Send a complete HTML document including , with , and tags. Returns a temporary download URL for the generated PDF (valid for 30 minutes). Requires a paid PdfBroker.io plan (Starter or above). Defaults reflect EU-first usage: A4 paper, Portrait orientation.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| html | Yes | Complete HTML document string including <html>, <head>, <style>, and <body> tags. Use CSS for styling. WeasyPrint supports CSS Paged Media for headers, footers, and page numbers via @page margin boxes. | |
| paperSize | No | Paper size: 'A4' (default, EU-first, 210x297mm), 'Letter' (8.5x11in), 'A3' (297x420mm), 'Legal' (8.5x14in) | A4 |
| resources | No | Optional embedded resources referenced by relative path in the HTML (images, custom fonts via @font-face, stylesheets, etc.). Keys are relative paths (e.g., 'images/logo.png'), values are base64-encoded file contents. Unused entries are silently ignored. Invalid base64 returns a clear, key-named error before the API call is made. | |
| orientation | No | Page orientation: 'Portrait' (default) or 'Landscape' | Portrait |
| extraArguments | No | Optional extra WeasyPrint engine arguments forwarded verbatim to the engine. Keys are CLI long-form options without '--'. For switch-style flags use an empty-string value — example: {"presentational-hints": ""}. On key collision with structured parameters (conformanceLevel, paperSize, orientation), the user-supplied extra wins. See the docs://pdfbroker/api-reference resource for the supported argument list. | |
| conformanceLevel | No | PDF compliance standard. Values: 'None' (default — no compliance), 'PdfA1b' (archival, maps to pdf/a-1b), 'PdfA3b' (archival with attachments, maps to pdf/a-3b), 'PdfUA1' (accessibility, European Accessibility Act, maps to pdf/ua-1). Use PdfUA1 when the document must be accessible to screen readers. | None |
Tool Definition Quality
A4.1/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the transparency burden. It discloses a temporary download URL with a 30-minute validity, a paid plan requirement, and EU-first defaults (A4, portrait). It also notes support for multiple compliance standards. While it doesn't cover error handling or rate limits, it provides substantial behavioral context for a conversion tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise at four sentences and front-loads the core action. It efficiently covers purpose, supported standards, use cases, input requirements, output behavior, prerequisites, and defaults without excessive fluff. The structure is logical, but the 'Best for' phrase is slightly promotional.
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 no annotations and no output schema, the description explains the return value (temporary URL), engine, compliance options, input requirements, and access prerequisite. It handles the tool's complexity well. The only gap is lack of differentiation from html_to_pdf_wk, which prevents full contextual completeness.
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?
Schema description coverage is 100%, so the baseline is 3. The description adds minor context like EU-first defaults explaining A4/Portrait, but most parameter details are already in the schema. It does not introduce new parameter semantics beyond what the schema already provides.
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 opens with a specific verb and resource: 'Convert HTML and CSS to a PDF document using the WeasyPrint rendering engine.' This clearly states what the tool does and differentiates it from sibling html_to_pdf_wk by naming the engine. It also lists supported compliance standards and typical use cases, reinforcing a distinct purpose.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear usage context by stating it is 'Best for professional documents: invoices, reports, certificates, contracts, and accessible documents' and instructs to 'Send a complete HTML document including <html>, <head> with <style>, and <body> tags.' However, it does not explicitly mention alternatives or when not to use this tool, so it misses the full 'when-not' guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
html_to_pdf_wkAInspect
Convert HTML to PDF using the wkhtmltopdf rendering engine. Supports JavaScript execution and screen-capture style rendering. Good for simple documents, web page snapshots, layouts that rely on JavaScript, and fillable PDF forms (pass 'enable-forms' as an extra argument). Available on all PdfBroker.io plans including the free tier. Does NOT support PDF/A or PDF/UA compliance — use html_to_pdf for compliant documents. Defaults reflect EU-first usage: A4 paper, Portrait orientation.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| html | Yes | HTML content to convert. Can be a full document or a fragment. | |
| paperSize | No | Paper size: 'A4' (default, EU-first), 'Letter', 'A3', 'Legal' | A4 |
| resources | No | Optional embedded resources referenced by relative path in the HTML. Keys are relative paths (e.g., 'images/logo.png'), values are base64-encoded file contents. Unused entries are silently ignored. Invalid base64 returns a clear, key-named error before the API call is made. | |
| orientation | No | Page orientation: 'Portrait' (default) or 'Landscape' | Portrait |
| extraArguments | No | Optional extra wkhtmltopdf engine arguments forwarded verbatim to the engine. Keys are CLI long-form options without '--'. For switch-style flags use an empty-string value — example: {"enable-forms": ""} to make form fields in the rendered PDF interactive. On key collision with structured parameters (paperSize, orientation), the user-supplied extra wins. See the docs://pdfbroker/api-reference resource for the supported argument list. |
Tool Definition Quality
A4.7/5.0
Behavior5/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility. It discloses key behaviors: JavaScript execution, screen-capture rendering, lack of PDF/A/UA support, and how to enable forms via extraArguments. It also mentions EU-first defaults (A4, Portrait), adding useful context beyond the schema.
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 a compact, front-loaded paragraph where every sentence earns its place. It clearly states purpose, capabilities, use cases, limitations, alternatives, and defaults without redundancy, and uses bold for the compliance caveat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness5/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has 5 parameters, no annotations, and no output schema, the description provides substantial context: intended use cases, explicit alternative, compliance limitations, form-filling capability, and defaults. This is sufficient for an agent to select and invoke the tool correctly.
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?
Schema description coverage is 100%, so baseline is 3. The description adds only marginal parameter context beyond the schema, such as tying 'enable-forms' to fillable forms and mentioning EU-first defaults, but the schema already thoroughly documents all parameter semantics.
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?
Specifically states it converts HTML to PDF using the wkhtmltopdf rendering engine, and distinguishes from the sibling html_to_pdf by noting compliance limitations. The verb and resource are clear and the engine adds specificity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines5/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly lists appropriate use cases (simple documents, web snapshots, JavaScript-dependent layouts, fillable forms) and explicitly tells users to use html_to_pdf for PDF/A or PDF/UA compliant documents. This provides direct when-to-use vs alternatives guidance.
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
Dokmatiq DocGenofficial
AlicenseAqualityCmaintenancePDF/DOCX/Excel generation from HTML/Markdown with stationery overlay, ZUGFeRD/XRechnung e-invoicing, digital signing, form filling, and AI receipt OCR with DATEV/SKR03 export.40MIT- 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 HTML files or HTML content to PDF using Puppeteer's browser rendering engine with support for CSS, JavaScript, custom page formats, margins, and header/footer templates.6