ThePDFMaker MCP. Turn structured data into perfect PDFs, automatically.

Listen up. ThePDFMaker connects your AI client straight to an enterprise document automation API. You're handling the entire lifecycle of professional documents—think invoices, reports, or certificates—by mapping structured JSON data into high-fidelity PDFs using templates you pull from Google Docs or MS Word. You manage everything through simple conversation with your agent.

To start generating files, you first need a template ID and the specific data payload. The generate_pdf tool takes that structured data and a chosen template to spit out a finished PDF file. If you're not sure which templates exist, run list_pdf_templates; this shows every custom design currently saved in your account.

When you pick one of those templates, you gotta confirm the placeholders are right. You use the get_template_details tool to pull specific metadata about any template, letting you verify exactly which data fields it expects.

Need to clean house? You can run delete_pdf_template to permanently remove an old or unused design from the system's library.

Tracking everything is crucial. After you kick off a document job using generate_pdf, you don't know when it'll be ready, so you call get_pdf_status. This tells you if the PDF job is running or finished and gives you that direct download link once it’s done. You can also check your account health by running get_api_status to make sure the server connection's active and working correctly.

For money, always run get_credit_balance before a big batch—it shows your remaining API usage credits for document generation.

For accountability, you can check two other history logs. You use list_recent_pdfs to see a history of the last generated documents; this includes metadata like who the client was or what date it was made. And if you need general user data, running get_user_profile pulls your account details.

Setting up automation is where this thing shines. You can use list_webhooks to display all the automated triggers you've set up so far. If you want a document process to run automatically when some other system signals it, you call create_webhook to set up that new notification trigger for your workflow.

To keep track of what assets you’re using—like logos or background images—run list_asset_files to see all the image or document files uploaded to the system.

It's also worth noting how much data is hanging around. You can use get_user_profile to retrieve general account information and user details for your connected profile, which helps keep everything organized when running reports.