ChangeThisFile MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CHANGETHISFILE_MCP_URL | No | Override the upstream endpoint | https://changethisfile.com/mcp |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| convert_fileA | 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). |
| list_conversionsA | List all supported conversion routes. Optionally filter by source format to see what you can convert FROM a specific format. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one performs file conversions, the other lists supported conversion routes. No overlap exists.
Both tools follow a consistent verb_noun pattern (convert_file, list_conversions) using snake_case, making naming predictable.
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.
The server covers basic conversion and format discovery, but lacks features like conversion history, batch processing, or progress tracking, leaving notable gaps.