# Windmill → PDF with makesPDF

> For AI agents: a documentation index is available at https://makespdf.com/llms.txt — every docs page also has a markdown twin (append .md to the page URL), including this one: https://makespdf.com/docs/integrations/windmill.md

[Windmill](https://www.windmill.dev/) AI agent steps can use tools from MCP servers, so a flow can call makesPDF through our hosted MCP server. Every makesPDF MCP tool is available to the agent. Windmill supports only HTTP streamable MCP servers, which is what makesPDF is.

## Connect

You need a makesPDF [API key](https://makespdf.com/settings/api-keys?ref=windmill), and an AI provider resource for the agent itself.

1. Create an MCP resource in Windmill with a **Name** (any identifier) and the **URL** `https://makespdf.com/api/v1/mcp`.
2. Add the key as **Headers**: `Authorization` with the value `Bearer <makesPDF API key>`. Windmill's docs don't say whether its **Auth token** field adds the `Bearer ` prefix, so the header is the unambiguous choice.
3. In a flow, add an **AI Agent** step and add the MCP resource to it as a tool. The agent discovers the server's tools by itself.
4. To limit the agent, use the MCP tool's filtering settings, **Only include specified tools** or **Exclude specified tools**.

## Render a PDF

The agent chooses the tool from its prompt (`user_message` and `system_prompt`), so describe the document and which tool to use. It can call:

| Tool | Arguments | What it does |
| --- | --- | --- |
| `render_markdown` | `markdown`, optional `options` | Markdown → PDF (1 credit per 10 pages) |
| `render_template` | `templateId`, `data` | A stored or library template filled with your data |
| `validate_markdown` | `markdown` | Free accessibility check before you render |
| `list_templates` | optional `q`, `category`, `tags` | Find a library template such as `invoice-classic` |

## Get the file

Render results carry `pageCount`, `creditsDeducted`, `artifactId` and a `downloadUrl`. To hand the link to later steps, give the agent an `output_schema` with a `downloadUrl` field. The link is signed and needs no API key, so any step that downloads a URL can fetch the PDF. The link expires 15 minutes after the render. To fetch an older render, call `get_render_download_url` with its `artifactId` for a fresh link (free).

## Billing and limits

Renders bill your makesPDF credits exactly like the API: 1 credit per 10 pages on success, nothing on failure. Validation and listing tools are free. On the Free and Hobbyist plans, unless the account holds Growth credits, each page carries a small makespdf.com link. Windmill's own usage and your AI provider's token charges are separate. The full tool reference is on the [MCP page](https://makespdf.com/docs/mcp).
