Integration

FileToPDF integration

FileToPDF.dev converts content to PDF: render an HTML string in headless Chromium (JavaScript runs first), turn GitHub Flavored Markdown into a styled PDF, or convert an uploaded or linked file (Word, Excel, PowerPoint, images, EPUB, Visio, iWork and 130+ formats). Each conversion returns the PDF as a stored file and uses 1 credit; check the plan and remaining credits for free. Layout, PDF/A, PDF/UA and password options need the Pro or Scale plan (or the free trial). The multipart variants of the HTML and Markdown routes (bundles of local assets, header and footer templates) are not exposed. Authentication is an API key sent in the x-api-key header.

Connect FileToPDF How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in FileToPDF.Built from the 4 FileToPDF tools below, on the connection you add once.

What you can do with FileToPDF

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Pdf, 3 operations

convert_file_to_pdfConvert file to pdfPOSTUses 1 conversion credit. Converts a file (Word, Excel, PowerPoint, image, EPUB and 130+ formats) to PDF from an upload (files) or a public URL (url); returns the PDF in file.
convert_html_to_pdfConvert html to pdfPOSTUses 1 conversion credit. Renders an HTML string (JavaScript runs first) to PDF in headless Chromium; returns the PDF as a stored file in file. Layout options need the Pro or Scale plan.
convert_markdown_to_pdfConvert markdown to pdfPOSTUses 1 conversion credit. Converts GitHub Flavored Markdown (tables, task lists, highlighted code) to a styled PDF; returns it as a stored file in file. Layout options need the Pro or Scale plan.

Account, 1 operation

get_accountGet accountGETChecks the API key and reads the workspace plan and remaining conversion credits. Free: never uses a credit.

Use FileToPDF from Claude Code, Cursor or Codex

Connect FileToPDF in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its FileToPDF operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect FileToPDF

Create your workspace
Sign up free. Nothing to install.
Connect FileToPDF once
Add your FileToPDF connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.