MCP FAQ
What is the Convert Fleet MCP server?
It is a remote Model Context Protocol (MCP) server that lets any MCP-compatible AI agent or automation platform run Convert Fleet conversions — convert, compress, FFmpeg and PDF tools — using your existing Convert Fleet API key.
How do I convert a file from Claude via MCP?
Add the Convert Fleet MCP server to your Claude config with npx mcp-remote pointing at https://convertfleet.com/api/mcp and your Bearer flt_ key, then ask Claude to convert a file by URL. Claude calls the convert_file tool and returns a short-lived download link.
What is the MCP endpoint URL and how do I authenticate?
The endpoint is https://convertfleet.com/api/mcp. Authenticate with the header Authorization: Bearer flt_... using an API key from your dashboard.
Does it keep my files?
No. Files are processed in memory and the converted result is held only behind a short-lived signed download URL (about 10 minutes) and then purged. Convert Fleet keeps zero retention.
Do MCP conversions use my credits?
Yes — conversions, compression, FFmpeg and PDF operations consume the same per-account credits as the REST API. list_supported_formats and account_status are free.
Which clients and platforms are supported?
Claude, Cursor, Hermes and OpenClaw as AI agents, plus n8n, Zapier and Make as automation platforms — any MCP client that speaks Streamable HTTP.