Skip to main content
Glama
Sign In
deenesjakoruzh
ChangeThisFile MCP Server

ChangeThisFile MCP Server

by aadilr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ChangeThisFile MCP Server

Nutzen Sie die sieben Datei-Tools von ChangeThisFile über jeden MCP-Client: Konvertierung über 1.000+ unterstützte Routen, Dokumentübersetzung, Tabellenextraktion, Komprimierung auf exakte Größe, Routing in natürlicher Sprache und Job-Statusprüfungen.

Unterstützt von ChangeThisFile.com. Discovery- und kostenpflichtige Vorschau-Jobs sind öffentlich. Die allgemeine convert_file-Funktion akzeptiert jetzt einen verifizierten Entwicklerschlüssel und teilt dessen Kontingent mit der REST-API-Nutzung. Anonyme Konvertierung bleibt während des Kompatibilitätsfensters für Konnektoren verfügbar; die Authentifizierung wird nicht vor dem 27. August 2026 erzwungen und erst nachdem die Konnektorunterstützung verifiziert wurde.

Tools

Tool

Beschreibung

convert_file

Konvertiert eine Datei. Übergeben Sie eine öffentlich zugängliche source_url oder base64_content (max. ~5 MB) sowie ein target_format (z. B. pdf, mp3, json). Das Quellformat wird automatisch aus der URL/Dateinamen erkannt, oder Sie übergeben source_format explizit. Gibt eine 1 Stunde gültige Download-URL zurück.

list_conversions

Listet alle unterstützten Konvertierungsrouten auf, optional gefiltert nach source_format (z. B. docx → sehen Sie jedes Format, in das Sie DOCX konvertieren können).

translate_file

Übersetzt ein Dokument unter Beibehaltung des Layouts. Gibt eine kostenlose Vorschau und einen einmaligen Checkout-Link für die vollständige Ausgabe zurück.

extract_tables

Extrahiert Tabellen aus PDFs oder Bildern in Excel. Gibt eine kostenlose Vorschau und einen einmaligen Checkout-Link für die vollständige Ausgabe zurück.

compress_file

Komprimiert eine PDF-, Bild- oder Videodatei auf eine exakte Maximalgröße. Kostenlos mit einem Tageslimit.

do_file_job

Leitet eine Dateianweisung in natürlicher Sprache an Konvertierung, Übersetzung, Extraktion oder Komprimierung weiter.

check_job

Prüft einen eingereichten Job und ruft dessen Vorschau, Checkout-Link oder Download-URL ab.

Related MCP server: UFC-MCP

Option 1 — Remote-Endpunkt (empfohlen, keine Installation)

Der Server wird unter https://changethisfile.com/mcp mit streamable HTTP transport (MCP-Spezifikation 2025-03-26) gehostet. Wenn Ihr Client Remote-MCP-Server unterstützt, richten Sie ihn direkt auf den Endpunkt. Clients, die benutzerdefinierte Header unterstützen, können Authorization: Bearer ctf_sk_... senden, um das authentifizierte Entwickler-Metering zu nutzen.

{
  "mcpServers": {
    "changethisfile": {
      "type": "streamable-http",
      "url": "https://changethisfile.com/mcp"
    }
  }
}

Claude Code:

claude mcp add --transport http changethisfile https://changethisfile.com/mcp

Option 2 — Lokaler Stdio-Server (dieses Paket)

Für Clients, die nur stdio sprechen, überbrückt dieses Paket stdio ↔ den gehosteten Endpunkt:

{
  "mcpServers": {
    "changethisfile": {
      "command": "npx",
      "args": ["-y", "github:aadilr/changethisfile-mcp"],
      "env": {
        "CTF_API_KEY": "ctf_sk_your_key_here"
      }
    }
  }
}

CTF_API_KEY ist optional: Ohne sie erhalten Sie 25 kostenlose Konvertierungen pro Monat und Netzwerk; danach fragt convert_file nach einem Schlüssel. Holen Sie sich einen verifizierten kostenlosen Schlüssel über das ChangeThisFile-Dashboard (oder POST https://changethisfile.com/v1/keys/free mit {"email":"you@example.com"} und klicken Sie die Verifizierungs-E-Mail an); dessen 25 monatlichen Konvertierungen werden zwischen MCP und REST geteilt. Bezahlte Pläne beginnen bei 29 $/Monat.

Oder klonen und direkt ausführen:

git clone https://github.com/aadilr/changethisfile-mcp.git
cd changethisfile-mcp
npm install
node index.js

Option 3 — Agent Skill / Claude Code-Plugin

Dieses Repository dient zugleich als Agent Skill und Claude Code-Plugin.

Jeder Agent mit Skill-Unterstützung (Claude Code, Codex CLI, Cursor, Gemini CLI, Copilot und weitere):

npx skills add aadilr/changethisfile-mcp

Claude Code-Plugin (bündelt den MCP-Server + den Skill):

/plugin marketplace add aadilr/changethisfile-mcp
/plugin install changethisfile@changethisfile

Der file-conversion-Skill bevorzugt bei Verbindung die MCP-Tools und greift andernfalls auf ein gebündeltes Skript (skills/file-conversion/scripts/convert.sh) zurück, das über einfaches HTTPS mit dem gehosteten Endpunkt kommuniziert – kein MCP-Client erforderlich.

Option 4 — Docker

docker build -t changethisfile-mcp .
docker run -i --rm -e CTF_API_KEY changethisfile-mcp

Schnelltest

curl -X POST https://changethisfile.com/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Unterstützte Formate

Kategorie

Beispiele

Bild

JPG, PNG, WebP, GIF, BMP, AVIF, ICO, SVG, TIFF, HEIC, PSD, RAW

Video

MP4, WebM, MKV, AVI, MOV, 3GP, FLV, WMV

Audio

MP3, WAV, FLAC, AAC, OGG, M4A, OPUS

Dokument

PDF, DOCX, DOC, ODT, RTF, TXT, HTML, MD, PPT, PPTX

Daten

JSON, CSV, TSV, YAML, XML, TOML, XLSX, XLS

Schriftart

TTF, OTF, WOFF, WOFF2

E-Book

EPUB, MOBI, AZW3, FB2, CBR, CBZ

Archiv

ZIP, RAR, 7Z, TAR, TAR.GZ, TAR.BZ2, TAR.XZ

Nutzen Sie list_conversions für die vollständige Routentabelle.

Umgebungsvariablen

Variable

Standard

Zweck

CTF_API_KEY

nicht gesetzt

Optionaler verifizierter Entwicklerschlüssel, der als Bearer-Token weitergeleitet wird; der Wert wird nie protokolliert

CTF_MCP_URL

https://changethisfile.com/mcp

Überschreibt den vorgelagerten Endpunkt

CHANGETHISFILE_MCP_URL

nicht gesetzt

Legacy-Alias für CTF_MCP_URL

Datenschutz & Limits

  • Discovery- und kostenpflichtige Vorschau-Jobs erfordern kein Konto. Die allgemeine Konvertierung ist im Kompatibilitätsmodus vorübergehend anonym; ein verifizierter Schlüssel ermöglicht jetzt gemeinsames Entwickler-Metering.

  • Dateien werden serverseitig verarbeitet und innerhalb von 24 Stunden automatisch gelöscht; Download-URLs verfallen nach 1 Stunde.

  • MCP-Eingaben sind auf 25 MB begrenzt. Authentifiziertes convert_file nutzt das gemeinsame API/MCP-Ratenlimit und Monatskontingent des Entwicklerkontos; andere aufwändige Tools behalten Missbrauchslimits pro Konto oder pro IP bei.

Lizenz

MIT

Available Tools

2 tools
convert_fileConvert FileAInspect

Convert a file from one format to another. Pass EITHER a publicly accessible URL (source_url) OR base64-encoded file contents (base64_content + source_format) — exactly one is required. Returns a temporary download URL (valid 1 hour; file deleted within 24 hours).

NameRequiredDescriptionDefault
source_urlNoPublicly accessible URL of the file to convert (preferred for large files)
base64_contentNoBase64-encoded file content (for small files; max ~5MB)
source_formatNoSource format extension (e.g. "docx", "mp4"). Auto-detected from URL if omitted.
target_formatYesTarget format extension (e.g. "json", "mp3", "pdf"). Required.
filenameNoOptional filename hint for auto-detection (e.g. "document.docx")

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses key behavioral details: returns a temporary download URL (valid 1 hour) and that the file is deleted within 24 hours. These details are beyond what annotations provide (readOnlyHint=false, destructiveHint=false) and give the agent important lifecycle information. No contradiction with annotations exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise at 3 sentences, each serving a distinct purpose: stating the core action, specifying parameter rules, and detailing the return behavior. No extraneous information is included, making it easy for an agent to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description adequately explains the return format (temporary URL with expiry) and data retention. It covers all input modalities and constraints. The presence of sibling tool name provides context. The description is complete for a conversion tool of moderate complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already describes all 5 parameters (100% coverage), setting baseline at 3. The description adds semantic value by explaining the mutual exclusivity of source_url and base64_content, specifying the ~5MB limit for base64, and noting that source_format can be auto-detected. This enhances the agent's understanding beyond the schema's per-parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description begins with a clear verb-resource pair: 'Convert a file from one format to another.' This immediately identifies the tool's core function. It also distinguishes itself from the sibling tool 'list_conversions' by focusing on performing the conversion rather than listing available formats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly states the two mutually exclusive input methods (url vs base64) and clarifies that exactly one is required. It provides guidance on when to prefer each (URL for large files, base64 for small files) and mentions auto-detection of source format. However, it does not explicitly state when not to use this tool or compare it to alternatives beyond the sibling.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_conversionsList Supported ConversionsA
Read-only
Inspect

List all supported conversion routes. Optionally filter by source format to see what you can convert FROM a specific format.

NameRequiredDescriptionDefault
source_formatNoFilter by source format (e.g. "docx" returns all DOCX target options)

TDQS

A4.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare 'readOnlyHint: true' and 'openWorldHint: false'. The description adds that the tool lists 'all' conversions, implying completeness within a bounded set, but does not provide significant behavioral context beyond what annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences long, front-loaded with the core purpose, and contains no extraneous information. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one optional parameter, no output schema), the description sufficiently conveys its functionality and the filtering option. Annotations complement the behavioral profile, making the definition complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema description coverage, the baseline is 3. The description adds value by providing an example ('e.g., "docx" returns all DOCX target options'), which helps the agent understand the filtering behavior beyond the schema statement.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'List all supported conversion routes,' using a specific verb and resource. It distinguishes the tool from sibling tools like 'convert_file' and 'compress_file' by focusing on listing rather than performing actions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly indicates when to use the tool (to see available conversions) and suggests filtering by source format. However, it does not explicitly state when not to use it or mention alternatives like 'convert_file' for performing conversions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updatesv1.0.0
    • First observedconvert_file
    • First observedlist_conversions
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.3/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one performs file conversions, the other lists supported conversion routes. No overlap exists.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern (convert_file, list_conversions) using snake_case, making naming predictable.

Tool Count3/5

With only 2 tools, the server feels minimal for a file conversion service. While covering the core functionality, the low count suggests a thin surface.

Completeness3/5

The server covers basic conversion and format discovery, but lacks features like conversion history, batch processing, or progress tracking, leaving notable gaps.

Maintenance

ActivityMaintained
ResponsivenessLimited data

Resources

Related MCP Connectors

Related MCP Servers