MCP server

The ConvertMePls MCP server is a standalone Model Context Protocol server that lets AI agents (Claude, and any MCP client) convert files. It is a thin bridge to the ConvertMePls API — all conversion happens server-side, so the MCP needs no engine, codecs or native binaries. Just Node.

#Run

npx @convertmepls/mcp

Configuration (environment):

| Var | Default | Notes | | --- | --- | --- | | CONVERTMEPLS_API_BASE | https://api.convertmepls.com | Point at your own self-hosted API | | CONVERTMEPLS_API_KEY | — | Your API key (from the dashboard) |

#Add to Claude

claude_desktop_config.json (or the Claude Code MCP config):

{
  "mcpServers": {
    "convertmepls": {
      "command": "npx",
      "args": ["-y", "@convertmepls/mcp"],
      "env": { "CONVERTMEPLS_API_KEY": "gck_live_…" }
    }
  }
}

#Tools

| Tool | Description | | --- | --- | | list_formats | Every supported format, grouped by category, plus the pair count. | | list_targets | The formats a given source can convert to ({ source: "mp4" }). | | convert_file | Convert a local file via the API. { input_path, target, output_path?, source?, options? } → uploads, converts server-side, writes the result to disk and returns its path. |

#Example

You: Convert ~/Desktop/clip.mov to an mp4 and extract the audio as mp3.

The agent calls convert_file twice — once with target: "mp4" and once with target: "mp3" — and reports the output paths. options accepts quality, width, height, crf and bitrate.

#Self-hosting

The server is open and standalone — clone it, point it at your own ConvertMePls API with CONVERTMEPLS_API_BASE, and run npm start. See the package README for details.