# Activepieces → 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/activepieces.md

[Activepieces](https://www.activepieces.com/) agents can use tools from a remote MCP server, so the **Run Agent** step can call makesPDF through our hosted MCP server. Every makesPDF MCP tool is available to the agent.

## Connect

You need a makesPDF [API key](https://makespdf.com/settings/api-keys?ref=activepieces).

1. In a flow, add or open a **Run Agent** step.
2. In **Agent Tools**, click **Add** and choose the MCP option.
3. Set **MCP Name**, for example `makespdf`, and **Server URL** to `https://makespdf.com/api/v1/mcp`.
4. Set **Protocol** to **Streamable HTTP**.
5. Set **Authentication Type** to **Access Token** and paste your API key as the token, with no `Bearer ` prefix. Activepieces sends it as `Authorization: Bearer <token>`.
6. Click **Validate Server**, then save it so its tools appear in the step's tool list.

Don't choose **Api Key**: it sends the key without `Bearer `, and makesPDF rejects it. With **Headers**, add `Authorization` with the value `Bearer <key>`.

Labels are from Activepieces' source as of November 2026; check them against your version.

## Or run one tool as a flow step

To call a single tool without an agent, add the **MCP Client** piece and use its **Call Tool** action. In the connection, set **Server URL** to `https://makespdf.com/api/v1/mcp`, **Transport** to **Streamable HTTP** and **Authentication** to **Bearer Token**, then paste your API key as the token (no `Bearer ` prefix; the piece adds it).

## Render a PDF

The agent chooses the tool from your prompt, so describe the document, for example "Write a one-page summary of this ticket as a PDF". 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` |

Each render result carries `pageCount`, `creditsDeducted`, `artifactId` and a `downloadUrl`.

## Get the file

`downloadUrl` is a signed link that 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. Activepieces's own charges are separate. The full tool reference is on the [MCP page](https://makespdf.com/docs/mcp).
