FileToPDF.dev
Convert files, HTML, and Markdown into PDF documents through the FileToPDF.dev API.
Verdict
Common use cases
- Turn Markdown meeting notes into PDFs
- Archive HTML email threads as documents
- Convert shared Google Docs links to PDFs
- Generate client proposals from draft text
- Snapshot web pages for compliance records
Integration
- Vendor
- FileToPDF.dev
- Category
- docs
- Auth
- API_KEY
- Tools
- 4
- Composio slug
filetopdf
Tools
- Convert File URL to PDF
Convert a file at a public HTTPS URL to PDF, consuming one conversion credit and returning a downloadable PDF. The URL path must end with a supported file extension. Check GET_ACCOUNT_STATUS for remaining credits.
- Convert HTML to PDF
Render an HTML string as a PDF, consuming one conversion credit and returning a downloadable PDF. Check GET_ACCOUNT_STATUS for remaining credits.
- Convert Markdown to PDF
Render a GitHub-Flavored Markdown string as a PDF. A successful conversion consumes one conversion credit and returns a downloadable PDF. Check GET_ACCOUNT_STATUS for remaining credits.
- Get Account Status
Return the connected FileToPDF workspace plan, subscription status, and remaining conversion credits without consuming a credit.
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select FileToPDF.dev from the catalog. 3. Visit filetopdf.dev/dashboard to generate an API key (requires a FileToPDF account with an active plan). 4. Paste the API key into Switchy's connection dialog and click 'Connect'. 5. Switchy confirms the connection by fetching your account status and displaying your remaining conversion credits. 6. Inside any Project, type '@FileToPDF.dev check my account status' to verify the integration works. 7. To convert content, @mention FileToPDF.dev with a public file URL, HTML snippet, or Markdown block — the MCP returns a downloadable PDF link within seconds. 8. Monitor your credit balance regularly; conversions fail silently when credits run out.
What teammates see: by default, memories from FileToPDF.dev are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Check Credit Balance
@FileToPDF.dev show my current account status and remaining conversion credits
Markdown Report to PDF
@FileToPDF.dev convert this Markdown to PDF: # Q1 Progress Report ## Highlights - Shipped v2.0 ahead of schedule - Onboarded 12 enterprise customers ## Next Quarter Focus on API stability and documentation.
Web Page Snapshot
@FileToPDF.dev convert this URL to PDF: https://example.com/product-roadmap and return the download link
HTML Email Archive
@FileToPDF.dev convert this HTML to PDF: <html><body><h1>Contract Amendment</h1><p>Effective January 1, the monthly fee increases to $5,000.</p></body></html>
Batch File Conversion
@FileToPDF.dev convert these three URLs to PDFs and show remaining credits after: https://example.com/doc1.docx, https://example.com/sheet2.xlsx, https://example.com/slide3.pptx
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@FileToPDF.dev check my account status and tell me how many conversions I have left this month
Your FileToPDF.dev account is on the Pro plan with an active subscription. You have 847 conversion credits remaining this billing cycle, which renews on March 15th. Your plan includes 1,000 credits per month. This check did not consume a credit.
GET_ACCOUNT_STATUS is the only tool that doesn't consume a conversion credit, making it safe to call before batch operations. Use this to verify you have sufficient credits before queuing multiple conversions in a workflow.
@FileToPDF.dev convert this markdown spec to PDF: # API v2.1 Release Notes ## Breaking Changes - Deprecated `/v1/auth` endpoint - New required `api_version` header ## New Features - Webhook retry logic - Rate limit headers in all responses
Markdown converted successfully. The PDF is now available at https://filetopdf.dev/downloads/abc123def456.pdf (link expires in 24 hours). This conversion consumed 1 credit, leaving you with 846 credits remaining. The PDF rendered with GitHub-Flavored Markdown styling, including proper heading hierarchy and list formatting.
CONVERT_MARKDOWN_TO_PDF is ideal for generating formatted documentation from inline text. Each conversion consumes one credit regardless of content length. The MCP accepts the markdown string directly—no external hosting required—but output PDFs expire after 24 hours.
@FileToPDF.dev I need to archive this spreadsheet as a PDF for compliance: https://docs.example.com/q3-financials.xlsx
File converted successfully. The PDF is available at https://filetopdf.dev/downloads/xyz789ghi012.pdf (expires in 24 hours). This conversion consumed 1 credit. The original Excel file was 2.3 MB; the resulting PDF is 18 pages preserving all worksheets and formatting. You have 845 credits remaining.
CONVERT_FILE_URL_TO_PDF requires a publicly accessible HTTPS URL ending in a supported extension (.xlsx, .docx, .pptx, etc.). The source file must be reachable without authentication. If your file is behind auth or in cloud storage, generate a temporary public link first.
Use-case deep-dives
When FileToPDF wins for legal doc handoffs
A 6-person legal ops team reviews vendor contracts in Google Docs, then archives signed versions as PDFs in their DMS. FileToPDF's URL-to-PDF tool lets the AI pull the final doc link from Slack or email, convert it, and drop the PDF into the archive folder—no manual export step. The markdown-to-PDF tool also works for generating cover sheets from template strings. This setup makes sense if you're converting fewer than 500 docs a month (check the credit limit on your plan). If you're batch-processing thousands of historical files, a self-hosted Pandoc workflow is cheaper. For teams closing 20-50 contracts monthly, FileToPDF removes the export bottleneck without adding infrastructure.
When this MCP fits support handoff cadences
A 3-person support team maintains a Notion knowledge base and sends quarterly PDF snapshots to enterprise customers who want offline docs. FileToPDF's HTML-to-PDF tool lets the AI scrape the Notion export HTML and render it as a styled PDF on demand. The account-status tool prevents the AI from burning credits on test runs. This works if your KB is under 200 pages and updates quarterly—FileToPDF's credit model favors infrequent, high-value conversions. If you're generating PDFs daily or your KB is 1000+ pages, a headless Chrome setup with better caching is more economical. For low-frequency, customer-facing deliverables, FileToPDF keeps the workflow simple without maintaining a PDF pipeline.
When FileToPDF handles eng team artifacts
A 5-person engineering team writes sprint retros in markdown files in their repo, then shares PDFs with stakeholders who don't use GitHub. FileToPDF's markdown-to-PDF tool lets the AI convert the retro file directly from the repo content without a local build step. The GitHub-Flavored Markdown support preserves tables and code blocks. This makes sense if you're generating 10-20 PDFs per sprint and your retros are under 10 pages each. If your team writes 50-page post-mortems with custom CSS, a local Pandoc template gives you more control. For standard sprint cadences where the PDF is a stakeholder courtesy, FileToPDF removes the toolchain dependency and keeps the AI workflow self-contained.
Frequently asked
What does the FileToPDF.dev MCP do in Switchy?
It converts files, HTML, and Markdown into PDFs directly from your AI workflows. The MCP calls FileToPDF.dev's API to render documents — you can convert a public file URL, raw HTML, or GitHub-Flavored Markdown. Each conversion consumes one credit from your FileToPDF.dev account. Useful when you need to generate reports, export formatted content, or archive web pages as PDFs without leaving Switchy.
Do I need a FileToPDF.dev account to use this MCP?
Yes. You need a FileToPDF.dev account and an API key. The MCP authenticates with that key and draws from your account's conversion credit balance. You can check your remaining credits using the Get Account Status tool before running conversions. No OAuth flow — just paste your API key into Switchy's connection settings and you're live.
Can this MCP convert files stored in Google Drive or Dropbox?
Not directly. The Convert File URL to PDF tool requires a public HTTPS URL that ends with a supported file extension. If your file is in Drive or Dropbox, you'll need to generate a public share link first. For private files, export the content as HTML or Markdown and use the HTML-to-PDF or Markdown-to-PDF tools instead.
How does this compare to using FileToPDF.dev's API directly?
The MCP wraps the API so your AI can call it in natural language — no code required. You get the same conversion quality and credit usage, but you skip writing HTTP requests and parsing responses. If you're already building custom integrations, the raw API gives you more control. For AI-driven workflows in Switchy, the MCP is faster and cleaner.
Who on the team should connect the FileToPDF.dev MCP?
Whoever owns your FileToPDF.dev account and has the API key. Conversions count against that account's credit balance, so connect it under the person or team inbox responsible for document generation. If multiple people need PDF conversion, share the Switchy workspace — the MCP connection is workspace-wide, not per-user.