# Make → 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/make.md

[Make](https://www.make.com/) scenarios and Make AI Agents can call makesPDF
through Make's **MCP Client** app, which connects to our hosted MCP server. Every
makesPDF MCP tool becomes something a scenario can run: render markdown,
render a template, validate, list templates. There is no makesPDF app to install
in Make.

## Connect

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

1. In a scenario, add the **MCP Client** app and pick **Call a tool**.
2. Under **Connection**, click **Create a connection**.
3. In **MCP Server**, choose **+ New MCP Server**.
4. Set **URL** to `https://makespdf.com/api/v1/mcp`.
5. Paste your API key into **API Key / Access token** as it is, with no
   `Bearer ` prefix, and save.

**Don't pick Make in the MCP Server list.** That entry is Make's own MCP
server; it asks for an "Environment URL" and fails with a `405` if you give
it the makesPDF URL.

## Render a PDF

In **Call a tool**, choose a tool and map its arguments:

| 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` |

Make keeps the tool's JSON result; the PDF embedded in the response is not
exposed in Make. The result carries
`pageCount`, `creditsDeducted`, `artifactId` and a `downloadUrl`; you will find
them under **Parsed Result**.

## Get the file

`downloadUrl` is a signed link that needs no API key, so any module that fetches
a URL can download the PDF:

1. Add the **HTTP** app's **Get a file** module after **Call a tool**.
2. Map **URL** to **Parsed Result → downloadUrl**.
3. Send the file on: upload it to Google Drive, Dropbox or OneDrive, or attach
   it to an email.

The link expires 15 minutes after the render, which is plenty inside one
scenario run. To fetch an older render, call `get_render_download_url` with its
`artifactId` for a fresh link (free).

## With AI

The MCP Client's **Execute an action with AI** module, and Make AI Agents, use
the same connection: give the AI the makesPDF tools and describe the document,
for example "Write a one-page summary of this ticket as a PDF". The AI picks
the tool and fills in the arguments; the PDF still arrives as a `downloadUrl`.

## 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. Make's
own operation and AI-token charges are separate. The full tool reference is on
the [MCP page](https://makespdf.com/docs/mcp).
