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).

Dify → PDF with makesPDF

Dify apps, workflows and agents can call makesPDF through Dify’s MCP client. Add the hosted server under Integrations → Tools → MCP, and every makesPDF tool — render markdown, render a template, validate, list templates — is imported as a tool your app can call. There is no makesPDF plugin to install.

Connect

You need a makesPDF API key.

  1. In Dify, open Integrations → Tools and select the MCP tab.
  2. Add an MCP server and fill in a name, the server URL https://makespdf.com/api/v1/mcp, and a unique server identifier.
  3. Leave the Dynamic Client Registration toggle off. makesPDF has no registration endpoint, so Dify cannot register an OAuth client automatically; the header below is the supported path.
  4. Under Advanced options → Custom headers, add one header: Authorization with the value Bearer <your key>. Custom headers are what Dify’s docs describe for a server that authenticates with a static token rather than OAuth.
  5. Save the server. Dify connects and imports the server’s tools.
Streamable HTTP only. makesPDF’s MCP endpoint speaks Streamable HTTP, so there is no SSE endpoint to configure. Dify’s docs also warn that apps reference a server by its identifier: change the identifier later and the server’s tools stop working in the apps that used the old one, and an exported app needs a server with the same identifier in the importing workspace.

Render a PDF

Dify imports each makesPDF tool with its description, so in an Agent node or an Agent app the model picks the tool that matches the request. In a workflow the Tool node runs the tool you choose, with the arguments you fill in.

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 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; in Dify that is the HTTP Request node, and the tool’s JSON result in the run carries the field.

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