PDFMakerAPI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PDFMAKERAPI_BASE_URL | No | Point the tool at a different API (e.g. http://localhost:3001 for local dev). | https://api.pdfmakerapi.com |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_documentA | Create a professional, shareable PDF document — invoices, receipts, certificates, reports, resumes, letters, and more. Returns a link that opens the document in the PDFMakerAPI editor, where the user can preview it, edit any field, and download the PDF. Design a THOROUGH, realistic document (don't leave it sparse) that exactly follows this model, then pass it as DOCUMENT MODEL (PDFMakerAPI) Document:
Variable: { id, name (snake_case, used as {{name}}), label (human), type: "text"|"date"|"number"|"currency", defaultValue?: string } Node (every node has: id, name, width: "full"|"1/2"|"1/3"|"1/4"|"2/3"|"3/4"|"auto", order: number, align?: "left"|"center"|"right", style?: NodeStyle):
NodeStyle: { backgroundColor?: hex, backgroundMode?: "none"|"solid"|"gradient", gradientTo?: hex, textColor?: hex, padding?: "none"|"sm"|"md"|"lg"|"xl", borderRadius?: "none"|"sm"|"md"|"lg", fullBleed?: boolean } VARIABLES — how data is inserted
RULES
After the tool returns a url, share it with the user and tell them they can open it to preview, edit any field, and download the PDF. |
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 1 tool
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined and distinct.
A single tool has no naming inconsistencies. The name 'create_document' is descriptive and follows a common verb_noun pattern.
The single tool is appropriate for a focused server that creates PDF documents. However, it might be considered slightly thin as it combines creation and editing via a returned URL.
The tool covers document creation comprehensively, but lacks supporting tools for managing documents (e.g., listing, updating, deleting). This leaves agents with no way to perform other lifecycle operations.