MCP server for reading/writing legacy-encoded files (CP1251, Windows-1251, etc.)
Most developer tooling work still happens through a UI a human drives. MCP File Tools MCP server moves it into the conversation instead. MCP server for reading/writing legacy-encoded files (CP1251, Windows-1251, etc.).
MCP server for file operations on text that isn't UTF-8. It detects the encoding from the file's bytes rather than its extension, hands the model UTF-8, and writes back in the original encoding — BOM and CRLF/LF intact, still byte-compatible with whatever legacy tool owns the file.
The server publishes 4 tools. What each one is for:
Encoding — aware across the whole tool set** — not just read and write: edit_file, grep_text_files and search_files decode the same waySandboxed — every path, including symlink and junction targets, is resolved and checked against the directories you allowedUpdate — The server checks for updates automatically and notifies you through tool responses when a newer version is available; the notice carries the stepsDebugging — MCP Inspector gives a web UI for calling tools and inspecting responses (needs Node.js 18+):Configuration is passed through the environment: MCP_DEFAULT_ENCODING. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP File Tools's toolset — Encoding, Sandboxed, Update and 1 more — is a fair guide to whether it matches your workflow. It is maintained by dimitar-grigorov; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Encoding | aware across the whole tool set** — not just read and write: edit_file, grep_text_files and search_files decode the same way |
| Sandboxed | every path, including symlink and junction targets, is resolved and checked against the directories you allowed |
| Update | The server checks for updates automatically and notifies you through tool responses when a newer version is available; the notice carries the steps for your install. Plugin installs update through [Updating the plugin](# |
| Debugging | [MCP Inspector](https://github.com/modelcontextprotocol/inspector) gives a web UI for calling tools and inspecting responses (needs Node.js 18+): |
macOS / Linux:
```json
{
"mcpServers": {
"file-tools": {
"command": "/Users/YOUR_NAME/.local/bin/mcp-file-tools",
"args": ["/Users/YOUR_NAME/Projects", "/Users/YOUR_NAME/Documents"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| MCP_DEFAULT_ENCODING | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.