
Mcp Multi Edit
io.github.eaisdevelopmentPublished by GitHub account eaisdevelopmentv0.2.7Updated Oct 24, 2026
Atomic multi-file find-and-replace by Essential AI Solutions (essentialai.uk)
Overview
A local MCP server that lets an assistant batch multiple find-and-replace edits across one or many files in a single atomic tool call.
- What you can do
- Apply several find-and-replace edits to a single file in one ordered, atomic call, with optional replace-all, dry-run preview and .bak backup by default. Coordinate edits across multiple files so that if any file fails, all previously changed files are rolled back. Preview changes with dry-run before committing, and receive structured error codes with recovery hints and conflict warnings when a search string matches several locations.
- When to use it
- Useful when renaming variables, migrating logging calls, or refactoring across several files, where the built-in single-edit tool would need many separate calls. It reduces tool calls and context tokens for bulk edits.
- Requirements
- Runs locally over stdio via npx from the npm package @essentialai/mcp-multi-edit. Needs Node.js 20 or later and Claude Code or Claude Desktop. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Mcp Multi Edit in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Multi Edit MCP Server
[npm version] [license] [tests] [coverage]
An MCP server that gives Claude the ability to perform multiple find-and-replace operations in a single tool call with guaranteed atomicity -- all edits succeed or none apply.
Built by Essential AI Solutions for Claude Code and Claude Desktop.
Why Multi Edit?
Claude's built-in Edit tool handles one find-and-replace per call. When renaming a variable across a file or refactoring multiple files, that means dozens of individual tool calls -- each consuming context tokens and adding latency.
Multi Edit batches them into a single call:
Benchmarks run on realistic scenarios (bulk rename, logging migration, cross-file refactor). See benchmarks/results/BENCHMARK-REPORT.md for full details.
Quick Start
Claude Code
Add .mcp.json to your project root:
Restart Claude Code. Then add the included CLAUDE.md to your project root so Claude automatically prefers multi_edit over the built-in Edit tool:
That's it -- Claude will now use multi_edit whenever it's the right tool for the job.
Display name: Claude Code uses the key name in
mcpServersas the server's display name. You can change the key to any name you prefer.
Alternative: One-liner via CLI:
Note: The CLI only accepts simple names (letters, numbers, hyphens, underscores). For the full branded display name, use the
.mcp.jsonapproach above.
Claude Desktop
Add to your config file (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
Restart Claude Desktop.
Full installation guide: docs/installation.md
Tools
multi_edit -- Single file, multiple edits
Batch multiple find-and-replace operations on one file. Edits apply sequentially and atomically.
multi_edit_files -- Multiple files, one atomic operation
Coordinate edits across multiple files. If any file fails, all files are rolled back automatically.
Full usage guide with examples: docs/usage.md
Features
- Atomic operations -- all edits succeed or none apply, no partial state
- Multi-file rollback -- if any file fails, all previously changed files are restored
- Dry-run preview -- see exactly what would change before committing
- Automatic backups --
.bakfiles created before every edit (disable withbackup: false) - Structured errors -- machine-readable error codes with recovery hints for automatic retry
- Conflict detection -- warns when
old_stringmatches multiple locations - Path validation -- absolute path enforcement, symlink resolution, existence checks
Error Codes
When retryable is true, Claude reads the recovery_hints in the response, adjusts the input, and retries automatically.
Troubleshooting guide: docs/troubleshooting.md
Requirements
- Node.js 20 or later
- Claude Code or Claude Desktop
Development
Project Structure
Documentation
License
PolyForm Noncommercial License 1.0.0
Free for personal and non-commercial use. For commercial licensing, contact [email protected].
Built by Essential AI Solutions
Source: README.md at commit 53fb3e7
Tools
0Version history
1- v0.2.7LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.