FileToPDF.dev MCP server for AI agents and assistants

Securely connect your AI agents and chatbots (Claude, ChatGPT, Cursor, etc) with FileToPDF.dev MCP or direct API to convert files, render HTML, transform Markdown, and automate PDF generation through natural language.

FileToPDF.dev logoFileToPDF.dev
Api Key

FileToPDF.dev is an API for converting files, HTML, and Markdown into PDF documents. It helps you generate clean PDFs without building or managing a conversion stack.

4 Tools

Try FileToPDF.dev now

Type what you want done — sign in and watch it run live in the Tool Router playground.

TOOL ROUTER PLAYGROUND
FileToPDF.dev
Try asking
TOOLS

Supported Tools

Every FileToPDF.dev action and event your agent gets out of the box.

Convert File URL to PDF

Convert a file at a public HTTPS URL to PDF, consuming one conversion credit and returning a downloadable PDF.

Convert HTML to PDF

Render an HTML string as a PDF, consuming one conversion credit and returning a downloadable PDF.

Convert Markdown to PDF

Render a GitHub-Flavored Markdown string as a PDF.

Get Account Status

Return the connected FileToPDF workspace plan, subscription status, and remaining conversion credits without consuming a credit.

SETUP GUIDE

Connect FileToPDF.dev MCP Tool with your Agent

1

Install Composio

typescript
npm install @composio/core ai @ai-sdk/mcp @ai-sdk/openai
Install the Composio SDK and your agent framework
2

Create a session with MCP enabled

typescript
import { Composio } from "@composio/core";

const composio = new Composio();
const { mcp } = await composio.create("your-user-id", {
  toolkits: ["filetopdf"],
  mcp: true,
});
Create a session scoped to FileToPDF.dev and read its MCP URL and headers
3

Connect your agent to the MCP server

typescript
import { createMCPClient } from "@ai-sdk/mcp";
import { openai } from "@ai-sdk/openai";
import { generateText, stepCountIs } from "ai";

const client = await createMCPClient({
  transport: { type: "http", url: mcp.url, headers: mcp.headers },
});

const { text } = await generateText({
  model: openai("gpt-5.6-sol"),
  tools: await client.tools(),
  prompt: "Convert this HTML into a PDF named invoice-1024.pdf: <h1>Invoice 1024</h1><p>Total: $249</p>",
  stopWhen: stepCountIs(10),
});

console.log(text);
await client.close();
Pass the session's MCP URL and headers to your agent and run a FileToPDF.dev request
SETUP GUIDE

Connect FileToPDF.dev API Tool with your Agent

1

Install Composio

typescript
npm install @composio/core @composio/openai openai
Install the Composio SDK, the OpenAI provider, and the OpenAI SDK
2

Create a Composio session

typescript
import OpenAI from "openai";
import { Composio } from "@composio/core";
import { OpenAIResponsesProvider } from "@composio/openai";

const composio = new Composio({ provider: new OpenAIResponsesProvider() });
const client = new OpenAI();

const session = await composio.create("your-user-id", { toolkits: ["filetopdf"] });
const tools = await session.tools();
Initialize Composio with the OpenAI Responses provider and create a session scoped to FileToPDF.dev
3

Run FileToPDF.dev tools with your agent

typescript
let response = await client.responses.create({
  model: "gpt-5.6-sol",
  tools,
  input: [{ role: "user", content: "Convert this HTML into a PDF named invoice-1024.pdf: <h1>Invoice 1024</h1><p>Total: $249</p>" }],
});

while (response.output.some((o) => o.type === "function_call")) {
  const outputs = await composio.provider.handleToolCalls(session, response.output);
  response = await client.responses.create({
    model: "gpt-5.6-sol",
    tools,
    previous_response_id: response.id,
    input: outputs,
  });
}

console.log(response.output_text);
Send a request, execute the FileToPDF.dev tool calls through the session, and print the final answer

Why Use Composio?

AI Native FileToPDF.dev Integration

  • Supports both FileToPDF.dev MCP and direct API based integrations
  • Structured, LLM-friendly schemas for reliable PDF conversion
  • Rich coverage for converting files, HTML, and Markdown into PDFs

Managed Auth

  • Secure API key handling so you don't hard-code FileToPDF.dev credentials
  • Use auth_configs.create() to configure FileToPDF.dev auth once
  • Use connected_accounts.link() to connect each user or environment cleanly

Agent Optimized Design

  • Tools are tuned for agents that need to create PDFs from documents, HTML, or Markdown
  • Comprehensive execution logs so you always know which PDF conversion ran, when, and on whose behalf

Enterprise Grade Security

  • Fine-grained RBAC so you control which agents and users can access FileToPDF.dev
  • Scoped, least privilege access for PDF conversion workflows
  • Full audit trail of agent actions to support review and compliance
FAQ

Frequently asked questions

Yes, FileToPDF.dev requires you to configure your own API key credentials. Once set up, Composio handles secure credential storage and API request handling for you.

Yes! Composio's Tool Router enables agents to use multiple toolkits. Learn more.

Yes. Composio is SOC 2 Type II compliant and is built to keep your FileToPDF.dev connection and credentials secure. OAuth tokens and API keys are encrypted, and sensitive customer data is protected at rest and in transit.

Composio also undergoes independent security testing and continuously monitors its systems for security threats. You can review the latest reports and policies in the Composio Trust Center.

Composio maintains and updates all toolkit integrations automatically, so your agents always work with the latest API versions.

Create the key in your FileToPDF.dev account settings, then paste it once on Composio's connection page. Composio stores it encrypted and uses it only for the FileToPDF.dev actions your agent runs. Nobody else in your workspace can read it, and you can revoke it inside FileToPDF.dev at any time.

When you connect a FileToPDF.dev account through Composio, every action runs under that account, so anything the agent creates, sends, or changes shows up in FileToPDF.dev as done by you. Keep an approval step in your prompt for actions with side effects, such as sending or deleting, and have the agent draft first.

Whatever the credentials you connect allow inside FileToPDF.dev. If FileToPDF.dev lets you scope a key to specific permissions, create a scoped one so the agent can only do what you intend. You can revoke the key inside FileToPDF.dev at any time.

Yes. Composio supports multiple connected accounts for the same app, and that works in Claude, ChatGPT, or any other assistant you connect through Composio. Give each FileToPDF.dev connection a name such as work or personal, and the assistant uses the one you mention in the request. Each account keeps its own credentials and nothing is merged.

The connection stops working the moment FileToPDF.dev rejects the old key. Create a new key in FileToPDF.dev and reconnect the account from the Composio dashboard or by asking your agent to reconnect FileToPDF.dev. Nothing else changes.

Composio's free Hobby plan includes 100,000 tool calls per month with no credit card, which covers most personal FileToPDF.dev use. Paid plans add higher limits and team features. Your FileToPDF.dev plan and its API limits still apply as usual.

Built-in connectors usually give one AI access to a limited set of apps. Many people use Composio because it lets their AI connect to more apps than it normally supports, or connect to multiple accounts for the same app (e.g. connect Claude to multiple FileToPDF.dev accounts).

With Composio, you connect FileToPDF.dev once and then use it across different AI assistants without setting it up separately in each one. Connect your apps to Composio once, then connect Composio to whichever AI you use, whether that's Claude, ChatGPT, Hermes, or your own custom assistant.

Start with FileToPDF.dev.It takes 30 seconds.

Managed auth, hosted MCP servers, and every FileToPDF.dev tool your agent needs.Free to start.

Start building