Skip to main content
Glama
deenesjakoruzh
aadilr

ChangeThisFile MCP Server

by aadilr
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

ChangeThisFile MCP Server

Usa las siete herramientas de archivo de ChangeThisFile desde cualquier cliente MCP: conversión entre más de 1.000 rutas admitidas, traducción de documentos, extracción de tablas, compresión de tamaño exacto, enrutamiento en lenguaje natural y comprobación de estado de trabajos.

Desarrollado por ChangeThisFile.com. Los trabajos de descubrimiento y de vista previa de pago son públicos. La conversión general convert_file acepta ahora una clave de desarrollador verificada y comparte su cuota con el uso de la API REST. La conversión anónima sigue disponible durante la ventana de compatibilidad del conector; la autenticación no se aplicará antes del 27 de agosto de 2026, y solo después de que se verifique el soporte del conector.

Herramientas

Herramienta

Descripción

convert_file

Convierte un archivo. Pasa un source_url de acceso público o base64_content (máx. ~5MB), además de un target_format (p. ej. pdf, mp3, json). El formato de origen se detecta automáticamente desde la URL/nombre de archivo, o pasa source_format explícitamente. Devuelve una URL de descarga válida durante 1 hora.

list_conversions

Lista todas las rutas de conversión admitidas, opcionalmente filtradas por source_format (p. ej. docx → ver todos los formatos a los que puedes convertir DOCX).

translate_file

Traduce un documento conservando su diseño. Devuelve una vista previa gratuita y un enlace de pago único para el resultado completo.

extract_tables

Extrae tablas de PDFs o imágenes a Excel. Devuelve una vista previa gratuita y un enlace de pago único para el resultado completo.

compress_file

Comprime un PDF, imagen o vídeo a un tamaño máximo exacto. Gratis con un límite diario.

do_file_job

Enruta una instrucción de archivo en lenguaje natural a conversión, traducción, extracción o compresión.

check_job

Comprueba un trabajo enviado y recupera su vista previa, enlace de pago o URL de descarga.

Related MCP server: Omni File Converter MCP

Opción 1 — Endpoint remoto (recomendado, sin instalación)

El servidor está alojado en https://changethisfile.com/mcp usando transporte HTTP transmisible (especificación MCP 2025-03-26). Si tu cliente admite servidores MCP remotos, apúntalo directamente al endpoint. Los clientes que admiten cabeceras personalizadas pueden enviar Authorization: Bearer ctf_sk_... para usar la medición de desarrollador autenticada.

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

Claude Code:

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

Opción 2 — Servidor stdio local (este paquete)

Para clientes que solo hablan stdio, este paquete conecta stdio ↔ el endpoint alojado:

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

CTF_API_KEY es opcional: sin ella obtienes 25 conversiones gratuitas al mes por red; después de eso, convert_file pide una clave. Obtén una clave gratuita verificada desde el panel de ChangeThisFile (o POST https://changethisfile.com/v1/keys/free con {"email":"you@example.com"} y haz clic en el correo de verificación); sus 25 conversiones mensuales se comparten entre MCP y REST. Los planes de pago comienzan en $29/mes.

O clona y ejecuta directamente:

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

Opción 3 — Agent Skill / complemento de Claude Code

Este repositorio funciona también como Agent Skill y complemento de Claude Code.

Cualquier agente con capacidad de skills (Claude Code, Codex CLI, Cursor, Gemini CLI, Copilot y más):

npx skills add aadilr/changethisfile-mcp

Complemento de Claude Code (incluye el servidor MCP + la skill):

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

La skill file-conversion prefiere las herramientas MCP cuando está conectada y, de lo contrario, recurre a un script incluido (skills/file-conversion/scripts/convert.sh) que se comunica con el endpoint alojado a través de HTTPS simple — no se requiere cliente MCP.

Opción 4 — Docker

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

Prueba rápida

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

Formatos admitidos

Categoría

Ejemplos

Imagen

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

Vídeo

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

Audio

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

Documento

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

Datos

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

Fuente

TTF, OTF, WOFF, WOFF2

Libro electrónico

EPUB, MOBI, AZW3, FB2, CBR, CBZ

Archivo

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

Usa list_conversions para la tabla completa de rutas.

Variables de entorno

Variable

Predeterminado

Propósito

CTF_API_KEY

sin definir

Clave de desarrollador verificada opcional enviada como token de portador; el valor nunca se registra

CTF_MCP_URL

https://changethisfile.com/mcp

Sobrescribe el endpoint remoto

CHANGETHISFILE_MCP_URL

sin definir

Alias heredado para CTF_MCP_URL

Privacidad y límites

  • Los trabajos de descubrimiento y de vista previa de pago no requieren cuenta. La conversión general es temporalmente anónima en modo de compatibilidad; una clave verificada habilita la medición de desarrollador compartida ahora.

  • Los archivos se procesan en el servidor y se eliminan automáticamente en 24 horas; las URL de descarga caducan después de 1 hora.

  • Las entradas MCP están limitadas a 25 MB. convert_file autenticado usa la tasa compartida de API/MCP y la cuota mensual de la cuenta de desarrollador; otras herramientas costosas conservan límites de abuso por cuenta o por IP.

Licencia

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).

ParametersJSON Schema
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.

ParametersJSON Schema
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?

Annotations already declare readOnlyHint=true, so the description need not restate safety. The description adds the filtering behavior, which is useful but not extensive behavioral context.

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?

Two sentences efficiently communicate the purpose and optional filter, with zero unnecessary words. Front-loaded with the main action.

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?

For a simple tool with one optional parameter and no output schema, the description fully covers what the agent needs to know: what it lists and how to filter.

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?

Schema coverage is 100% with the parameter already described, but the description adds meaning by explaining the filter effect and providing an example ('docx' returns all DOCX target options), enhancing understandability.

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 the verb 'list' and resource 'supported conversion routes', and implicitly distinguishes from sibling 'convert_file' by indicating this tool provides options for conversion rather than performing the conversion.

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?

It specifies when to use the tool (to list conversion routes, optionally filtered by source format) and gives a concrete example. However, it does not explicitly state when not to use it or mention 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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.0
    • First observedconvert_file
    • First observedlist_conversions
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.3/5.0
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
ResponsivenessUnresponsive

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aadilr/changethisfile-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server