FileToPDF MCP Server

Convert files, HTML, and Markdown to PDF via the FileToPDF API. Bring your own API key.

Remote serverstreamable-http

What is the FileToPDF MCP server?

FileToPDF MCP server exists for a simple reason — assistants are far more useful when they can act on FileToPDF directly instead of describing what you should do. Convert files, HTML, and Markdown to PDF via the FileToPDF API. Bring your own API key.

What you get

Each convert tool returns a metadata summary and the PDF as an embedded application/pdf resource (base64), so capable clients can save the file. Set the FILETOPDF_OUTPUT_DIR env var, or pass save_path, to also write the PDF to disk.

What the assistant can call

Once FileToPDF is connected, these are the calls the assistant has available:

  • get_account — Check the API key and show plan + remaining credits. Free, no credits used
  • convert_file — Convert a file from a public URL (DOCX, XLSX, PPTX, images, HTML, MD, PDF…) to PDF
  • convert_html — Render a raw HTML string (with optional CSS + layout options) to a pixel-perfect PDF via Chromium
  • convert_markdown — Render a raw Markdown string (with optional CSS + layout options) to a clean PDF

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need one environment variable: FILETOPDF_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. FileToPDF's toolset — get_account, convert_file, convert_html and 1 more — is a fair guide to whether it matches your workflow. It is maintained by dev.filetopdf; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Before you rely on it

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the filetopdf mcp server does with a few real requests.

Available tools

ToolWhat it does
get_accountCheck the API key and show plan + remaining credits. Free, no credits used.
convert_fileConvert a file from a **public URL** (DOCX, XLSX, PPTX, images, HTML, MD, PDF…) to PDF.
convert_htmlRender a raw **HTML** string (with optional CSS + layout options) to a pixel-perfect PDF via Chromium.
convert_markdownRender a raw **Markdown** string (with optional CSS + layout options) to a clean PDF.

How to install the FileToPDF MCP server

{
  "mcpServers": {
    "filetopdf": {
      "command": "npx",
      "args": ["-y", "filetopdf-mcp"],
      "env": { "FILETOPDF_API_KEY": "sk_live_YOUR_API_KEY" }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
FILETOPDF_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use FileToPDF to get account.
  • Use FileToPDF to convert file.
  • Use FileToPDF to convert html.

Frequently asked questions

It connects FileToPDF to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (get_account, convert_file, convert_html, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with FileToPDF directly.