FileToPDF MCP server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FILETOPDF_API_KEY | Yes | Your FileToPDF API key. Get a free trial key at https://filetopdf.dev | |
| FILETOPDF_OUTPUT_DIR | No | Optional directory path to save the PDF files to disk. If not set, PDF is only returned as base64 resource. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountA | Check the FileToPDF API key and return the plan, remaining conversion credits, and subscription status. Free — costs no credits. Use this to verify the connection works. |
| convert_fileA | 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, TXT, CSV…), images (PNG, JPG, WebP…), HTML, Markdown, or an existing PDF (passthrough). Costs 1 credit on success. Returns the PDF as an embedded resource. |
| convert_htmlA | 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 embedded resource. |
| convert_markdownA | 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. Costs 1 credit on success. Returns the PDF as an embedded resource. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each conversion tool targets a distinct input type (URL-based files, raw HTML, raw Markdown), and get_account is separate. No overlap.
All tool names follow a consistent verb_noun pattern (convert_file, convert_html, convert_markdown, get_account).
Four tools is appropriate for a focused PDF conversion server, covering the main conversion methods and account info.
The tool surface covers all major conversion paths (URL-based auto-detection, raw HTML, raw Markdown) and account verification, with no obvious gaps.