MCP File Tools
Let your coding agent read and write legacy-encoded text files (CP1251, KOI8-R, ISO-8859) with auto-detection instead of corrupting imports on Windows or Eastern European datasets.
Overview
MCP File Tools is a MCP server for the Build phase that auto-detects and processes non-UTF-8 text encodings so agents can read and write legacy files safely.
What is this MCP server?
- Auto-detect and handle non-UTF-8 encodings including CP1251, CP1252, KOI8-R, and ISO-8859 family
- MCP File Tools distributed as versioned mcpb binaries for Windows amd64/arm64 and Linux amd64
- stdio transport for local agent registration without a hosted API key
- Targets agent workflows that ingest CSV, logs, or config from regional Windows exports
- Release-tracked builds with published fileSha256 per platform package
- Server version 1.5.9
- stdio mcpb packages for Windows amd64, Windows arm64, and Linux amd64 with published SHA256 hashes
Community signal: 14 GitHub stars.
What problem does it solve?
Coding agents default to UTF-8 and trash CP1251, KOI8-R, and ISO-8859 files, which blocks solo builders from automating fixes on real regional or legacy datasets.
Who is it for?
Builders automating data cleanup or code edits on Windows-originated or Cyrillic-encoded files through Claude Code or Cursor.
Skip if: Projects that are UTF-8 end-to-end with no legacy imports, or teams that prefer a one-off Python script instead of MCP tooling.
What do I get? / Deliverables
After registration, your agent can open and transform correctly decoded text in legacy encodings without manual iconv steps in every prompt.
- Correctly decoded text from legacy-encoded source files
- Agent-safe write paths that preserve intended charset semantics
- Repeatable encoding detection without custom per-project scripts
Recommended MCP Servers
Journey fit
File encoding fixes appear while agents touch real repos and data files during implementation, which maps to Build even when debugging user-reported garbled text later in Operate. Agent-tooling is the right shelf because the server extends what Claude Code and Cursor can safely do to local files beyond naive UTF-8 assumptions.
How it compares
Local file-encoding MCP utility, not a cloud database or document collaboration server.
Common Questions / FAQ
Who is MCP File Tools for?
Developers and solo builders whose agents must handle CP1251, KOI8-R, ISO-8859, and similar encodings on local files during automation.
When should I use MCP File Tools?
Use it during Build when ingesting legacy CSVs, configs, or logs where charset auto-detection is required before transforms or commits.
How do I add MCP File Tools to my agent?
Download the mcpb binary for your OS from the v1.5.9 GitHub release, point your MCP stdio config at the executable, and reload the agent.