mcp-html2pdfconverter
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HTML2PDF_API_KEY | Yes | Your HTML2PDF Converter API key. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_pdf_jobA | Submit a webpage URL or HTML to be converted to a PDF asynchronously. This will return a Job ID. You MUST then use the check_pdf_status tool to poll the status and download the PDF. |
| check_pdf_statusA | Check the status of a pending PDF conversion job. If it is completed, this will download the PDF and return the file path. |
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
submit_pdf_job and check_pdf_status have clearly distinct roles: one creates a job, the other retrieves its result. No overlap in functionality.
Both tools follow the same verb_noun pattern with snake_case (submit_pdf_job, check_pdf_status), making their relationship and intent immediately clear.
With only two tools, the server is minimal but covers the core conversion workflow. It feels slightly thin but is functional for a simple service.
The tool set covers the full job lifecycle: submit a conversion job and poll for the result. No obvious gaps for the stated HTML-to-PDF conversion purpose.