pdf-it
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHROME_PATH | No | Path to a custom Chrome executable (if Chrome is not in standard location) |
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 | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_pdfA | Convert markdown into a designed PDF (cover page, auto TOC, page-numbered footer). Use this for any "save/export/print/share as PDF", "make a report", "turn this into a PDF", or /pdf request — do NOT fall back to Chrome headless, cupsfilter, wkhtmltopdf, pandoc, or LaTeX. Templates: research-report (cover + TOC, default) or plain (no cover, no TOC). |
| list_templatesA | List all available PDF templates with their descriptions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| research_report | Generate a designed PDF research report on a topic. Researches the topic, structures the findings as markdown, and generates a research-report PDF with cover, TOC, and page numbers. |
| quick_note | Save the current conversation or content as a quick PDF note using the plain template (no cover, no TOC). |
| pdf_outline | Draft a structured outline for a research report before generating the full PDF. Useful for long-form documents where alignment on structure matters before research begins. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Research Report Template | Specification for the research-report template: cover page, auto-generated TOC, body hierarchy, page-numbered footer. |
| Plain Template | Specification for the plain template: dense body, no cover, no TOC. Best for short notes. |
| pdf-it Style Guide | Typography, color palette, and layout rules pdf-it follows. Useful when an agent decides how to structure markdown for best PDF output. |
| Markdown Cheatsheet for pdf-it | Quick reference of which markdown elements pdf-it supports and how each renders. Use this when an agent is unsure whether a feature will render correctly. |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: generating PDFs and listing templates, with no overlap.
Both tools follow a consistent verb_noun snake_case pattern (generate_pdf, list_templates), making them predictable.
With only two tools, the server covers the essential PDF generation function but feels minimal for a broader toolkit.
The set covers generate and list, but lacks template management (create, update, delete) and advanced options, leaving moderate gaps.