ResxMcp

ResxMcp is a lightweight MCP server that enables safe read/write/modify operations on .resx localization files. It exposes a small set of tools (resx.read, resx.write, resx.setEntry, resx.removeEntry) that can be invoked by any MCP client via JSON-RPC over stdio. This makes it easy to integrate into AI-assisted workflows, editors, or automation pipelines that support the MCP protocol. You can read a .resx file to inspect keys and values, atomically write updates (with optional backup), and add, update, or remove resource entries. The server is designed to be simple, deterministic, and diff-friendly, which helps with versioning and localization pipelines. It works with Gemini CLI, Claude Desktop, Cursor IDE, and any MCP-compatible client.

Prerequisites:

• .NET 8.0 runtime (for building from source) or a prebuilt single-file executable for Windows
• Git

Installation steps:

1. Clone the repository:

git clone https://github.com/miaofalianhua/ResxMcp.git
cd ResxMcp

2. Build and publish (if you need to generate a local publish folder):

dotnet publish -c Release -r win-x64 -p:PublishSingleFile=true -o ./publish

3. If you prefer using a prebuilt executable, use the published ResxMcp.exe directly from the publish folder created above, or download/use your packaged build as needed.
4. Register with Gemini CLI (example from the README):

gemini mcp add resx-tool "./publish/ResxMcp.exe"

5. Verify installation:

gemini @resx-tool tools/list

You should see tools such as:

• resx.read
• resx.write
• resx.setEntry
• resx.removeEntry

Tips and notes:

• ResxMcp communicates over stdio using JSON-RPC, so it can be integrated into automation pipelines or AI-assisted tooling that speaks MCP.
• Use resx.read to fetch file contents as UTF-8 text, resx.write for atomic replacements (you can enable backup with a backup flag), and resx.setEntry/resx.removeEntry to manage keys.
• For distribution as a Gemini extension, the project includes gemini-extension.json to wrap it for one-command installation when available in the registry.
• If you encounter issues with installation or tool discovery, ensure the ResxMcp executable has execute permissions on your platform and that any required dependencies are present (e.g., .NET runtime for non-published builds).
• Backups (.bak) are optional with resx.write; consider enabling them to guard against accidental data loss during automated edits.