ConvertLABSCO SUMMARY
Format conversion without the browser tab that asks for your email.
Validating against the live OpenAPI spec is the detail that matters: conversion options change per format pair, and a hardcoded parameter list is how these integrations quietly go stale. Local mode keeps the file handling on your machine even though the conversion happens at ConvertAPI.
What it is
An MCP server for ConvertAPI's file conversion service, available as a hosted endpoint at mcp.convertapi.io or as a local .NET build that reads and writes files on your machine.
What you get
- Conversion between more than 200 formats: documents, images, spreadsheets, presentations
- Parameters validated against ConvertAPI's live OpenAPI specification rather than a list frozen at build time
- Full parameter coverage, including PageSize, PageOrientation, Quality and StoreFile
- A local mode that takes an input path and writes results to an output directory you choose
- A hosted endpoint for the case where you would rather not run anything
Requirements
The hosted endpoint at https://mcp.convertapi.io needs nothing installed; you sign in with your ConvertAPI account the first time a client connects. Running it yourself needs the .NET 9.0 SDK, dotnet build, and two values in the environment: your ConvertAPI token and the ConvertAPI base URL it should call.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
Turning a pile of documents into PDFs
Point at the files and name the target format, rather than opening each one to export it.
Getting a spreadsheet out of a PDF someone emailed
Convert straight to XLSX and keep the result in a directory you nominate.
Producing images from document pages
Render pages to JPG or PNG for a slide, a thumbnail or a review.
Controlling how the output is laid out
Set page size, orientation and quality on the conversion instead of fixing it afterwards.
2 tools
Listed in project docs. Your client may show a different list.
InformationBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- A ConvertAPI account (the hosted endpoint signs you in over OAuth)
- For the self-hosted .NET route: .NET 9.0 SDK and CONVERTAPI_TOKEN
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
https://mcp.convertapi.ioMCP Clients
Claude Desktop — self-hosted .NET
Clone and build the server
Needs the .NET 9.0 SDK. The config runs dotnet with --no-build, so build once first.
git clone https://github.com/ConvertAPI/convertapi-mcp
cd convertapi-mcp
dotnet buildAdd this to your client's MCP settings
<YOUR_PATH_TO_CA_MCP_LOCAL> is the full path of the CA.MCP.Local folder in your clone, so the path ends in CA.MCP.Local\CA.MCP.Local.csproj. Put your ConvertAPI token in CONVERTAPI_TOKEN.
{
"mcpServers": {
"convertapi": {
"command": "dotnet",
"args": [
"run",
"--project",
"<YOUR_PATH_TO_CA_MCP_LOCAL>\\CA.MCP.Local.csproj",
"--no-build"
],
"env": {
"CONVERTAPI_TOKEN": "<YOUR_CONVERTAPI_TOKEN>",
"CONVERTAPI_BASE_URI": "https://v2.convertapi.com"
}
}
}
}Cline
Clone and build the server
Needs the .NET 9.0 SDK. The config runs dotnet with --no-build, so build once first.
git clone https://github.com/ConvertAPI/convertapi-mcp
cd convertapi-mcp
dotnet buildAdd this to your client's MCP settings
<YOUR_PATH_TO_CA_MCP> is the full path of the CA.MCP.Local folder in your clone. Put your ConvertAPI token in CONVERTAPI_TOKEN.
{
"mcpServers": {
"convertapi": {
"command": "dotnet",
"args": [
"run",
"--project",
"<YOUR_PATH_TO_CA_MCP>",
"--no-build"
],
"env": {
"CONVERTAPI_TOKEN": "<YOUR_CONVERTAPI_TOKEN>",
"CONVERTAPI_BASE_URI": "https://v2.convertapi.com"
}
}
}
}Claude Code
/plugin marketplace add ConvertAPI/convertapi-mcp
/plugin install convertapi@convertapiSign in to ConvertAPI when Claude Code asks; the plugin connects to https://mcp.convertapi.io over OAuth.