Convert files, HTML, and Markdown to PDF via the FileToPDF API. Bring your own API key. Connect the official FileToPDF MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http filetopdf https://api.filetopdf.dev/mcpRun in your terminal, then restart Claude Code.
FileToPDF · https://api.filetopdf.dev/mcp
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “get_account”: Check the FileToPDF API key and return the plan, remaining conversion credits, and subscription status. Free — costs no credits. Use this to.”
“Use “convert_file”: Convert a file fetched from a public URL into a PDF. Auto-detects the engine from the extension: Office docs (DOCX, XLSX, PPTX, ODT, RTF, TX.”
“Use “convert_html”: Render a raw HTML string to a PDF using Chromium, with optional CSS and layout options. Costs 1 credit on success. Returns the PDF as an emb.”
“Use “convert_markdown”: Render a raw Markdown string to a PDF, with optional CSS and layout options. A sensible default stylesheet is applied when no CSS is given.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how FileToPDF holds up.
Operated by FileToPDF (filetopdf.dev) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If FileToPDF adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose FileToPDF in the gate directory. No sign-in needed.
FileToPDF's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
get_account — Check the FileToPDF API key and return the plan, remaining conversion credits, and subscription status. Free — costs no credits. Use this to
convert_file — Convert a file fetched from a public URL into a PDF. Auto-detects the engine from the extension: Office docs (DOCX, XLSX, PPTX, ODT, RTF, TX
convert_html — Render a raw HTML string to a PDF using Chromium, with optional CSS and layout options. Costs 1 credit on success. Returns the PDF as an emb
convert_markdown — Render a raw Markdown string to a PDF, with optional CSS and layout options. A sensible default stylesheet is applied when no CSS is given.
https://api.filetopdf.dev/mcpYes — FileToPDF operates its own remote MCP server at api.filetopdf.dev. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick FileToPDF in the directory. No account or sign-in is needed. From then on, FileToPDF's tools are available in every client you've connected to gate.
No. FileToPDF runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect FileToPDF in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up FileToPDF in: Claude · Claude Code · ChatGPT · Cursor · VS Code