surgical-editing-server
Related Servers
Alternatives to surgical-editing-server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to read, write, edit, search, rename, move, and delete files, perform regex search-and-replace across trees, query and modify JSON documents, and inspect git status and diffs, all through structured tools instead of shell commands. Includes safeguards like dry-run previews, atomic multi-file edits, and protection for denied or sensitive paths.MIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to gather repository context, apply multi-file edits with test-gated verification and automatic rollback, and run batch read-only scripts in fewer round trips.3299 npm50Apache 2.0
- AlicenseNot gradedqualityCmaintenanceSnapshot-based file editing for AI agents. Enables safe file edits by sending only new content against immutable, content-addressed snapshots with 3-way merging and ambiguity protection.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables cooperating AI agents to manage versioned files and JSON key-value state, record tool-call history, and publish changes atomically after dependency validation.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to perform zero-token static audits, simulate refactorings in an ephemeral RAM clone, trace downstream ripple effects, and block unsafe writes with automatic rollback to prevent regressions.42 npmBusiness Source 1.1
- AlicenseCqualityBmaintenanceEnables AI agents to list, read, inspect, write, and precisely edit files and to regex-search a workspace, with every path confined to a sandboxed root directory. Token-saving output such as line-range reads and match locations without line content keeps context use low while guarded writes and ambiguous edits prevent accidental data loss.6MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlapping purpose. Its description clearly frames it as an exact-match, atomic replacement editor.
A single snake_case verb_noun-style name (surgical_replace) is internally consistent by definition and matches the server's stated purpose.
One tool is thin for a general editing server, but the tool is deliberately broad (multi-file, multi-snippet, atomic, dry-run) so it earns its place. Still, a single operation is borderline for practical agent workflows.
Replacement plus dry-run diff covers the core edit loop, but there is no way to read files, create new files, append/insert at a location, or undo within this server. Agents must pair it with a separate read/inspect capability, leaving notable gaps.