makesPDF

For AI agents: a documentation index is available at /llms.txt — every docs page also has a markdown twin (append .md to the page URL).

Flowise → PDF with makesPDF

Flowise agents and chatflows reach makesPDF through Flowise’s Custom MCP: add the hosted server as a tool on an Agent node and its tools sit alongside the built-in ones. Flowise’s docs describe Custom MCP as the way to connect any MCP server of your choice, and there is no OAuth for it, so the connection is the URL plus a header.

Connect

You need a makesPDF API key.

  1. Add an Agent node to a chatflow and, on it, add a new Custom MCP tool.
  2. Choose the streamable HTTP option and set the URL to https://makespdf.com/api/v1/mcp. For a remote server, streamable HTTP needs only the URL and the headers the server asks for.
  3. Add the header Authorization with the value Bearer <your key> to the MCP server config.
  4. Optionally keep the key out of the config: create a Flowise variable and reference it in the config as {{$vars.makespdfKey}}. Flowise resolves variables written with double curly braces and the $vars. prefix.
  5. Refresh Available Actions. Flowise pulls the server’s actions and the agent can call them.
Stdio is for local installs only. Flowise’s docs say to use stdio only when Flowise itself runs locally, because it installs the MCP server package with npx. makesPDF is a remote server, so there is nothing to install and streamable HTTP is the path.

Render a PDF

The agent picks the action from its description, so “write me a PDF of this week’s orders” is enough. A Custom MCP tool also runs outside an agent, but then its arguments must be filled in explicitly, because no model is choosing them.

ToolArgumentsWhat it does
render_markdownmarkdown, optional optionsMarkdown → PDF (1 credit per 10 pages)
render_templatetemplateId, optional dataA stored or library template filled with your data
validate_markdownmarkdownFree accessibility check before you render
list_templatesoptional q, category, tagsFind a library template such as invoice-classic

The action 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 can fetch a URL can download the PDF. Flowise returns the tool’s output in the agent’s response and in the run’s log, and downloadUrl is a field of that JSON.

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. Flowise’s own hosting and model charges are separate. The full tool reference is on the MCP page.