Multi Edit MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| multi_editA | Perform multiple find-and-replace operations on a single file atomically. All edits succeed or none apply. |
| multi_edit_filesA | Perform coordinated edits across multiple files atomically. All file edits succeed or none apply. |
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 are clearly differentiated by scope: multi_edit targets a single file while multi_edit_files targets multiple files. Although the names are similar, the descriptions explicitly clarify the difference, leaving little room for confusion.
Both tools follow a consistent snake_case pattern with the shared prefix 'multi_edit', and the suffix 'files' for the multi-file variant. The naming is predictable and clearly related.
With only two tools, the server feels thin for a general-purpose editor, but it is well-scoped for its specific purpose of atomic multi-edits. The count is borderline but acceptable given the narrow domain.
The server fully covers its stated purpose: atomic editing on a single file and across multiple files. No obvious operations are missing for the domain it targets.