# Retool → 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/retool.md

[Retool](https://retool.com/) connects to a remote MCP server as a **resource**,
then gives its tools to an agent, to the app building agent, or to a function in
an app. For makesPDF, create an **MCP Server** resource with **Bearer Token**
authentication.

## Connect

You need a makesPDF [API key](https://makespdf.com/settings/api-keys?ref=retool)
and edit permission on resources in your Retool organization.

1. In Retool, open **Resources** and click **Create new** → **Resource**. Search
   for **MCP** and pick the **MCP Server** tile.
2. Give the resource a **name** and **description** that say what it connects to;
   Retool shows the description to the people using the resource.
3. Set **Server URL** to `https://makespdf.com/api/v1/mcp`. Retool talks only to
   remote servers over HTTP or HTTPS, and negotiates the MCP protocol version
   with the server itself.
4. Set **Authentication** to **Bearer Token** and paste your API key as the
   token. Retool sends it as an `Authorization: Bearer` header, so the key goes
   in without a prefix.
5. Click **Test connection**. A success message means Retool reached the server
   and listed its tools; **View in console** opens the Debug Tools console with
   the request and response if it did not.
6. Click **Create resource** to save it.

**Don't use Automatic authentication.** Retool's **Automatic** option registers an
OAuth client with the server when the server supports registration, and makesPDF
does not offer that registration. Choose **Bearer Token** instead.

## Use the tools

Add the resource as a tool on an agent so it can retrieve and call the server's
tools, or call a tool from a function in an app: Retool exposes one typed method
per tool on the resource and returns the result as `data`. With a bearer token
the credential is shared, so there is no per-user connection step.

| Tool | Arguments | What it does |
| --- | --- | --- |
| `render_markdown` | `markdown`, optional `options` | Markdown → PDF (1 credit per 10 pages) |
| `render_template` | `templateId`, optional `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` |

The result carries `pageCount`, `creditsDeducted`, `artifactId` and a
`downloadUrl`.

## Get the file

`downloadUrl` is a signed link that needs no API key, so a query, a workflow or a
browser tab in Retool can fetch the PDF without any credential of its own.

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. Retool's own plan is billed separately. The
full tool reference is on the [MCP page](https://makespdf.com/docs/mcp).
