Summary
The editor surface a model already knows, for clients that do not ship one.
Everything runs through one tool with a command argument, which keeps the definition cost to a single entry while still covering view, create, replace and insert. Because it mirrors text_editor_20241022, the calling conventions are ones a model has already seen rather than a new dialect to learn. The persistent state across calls is what makes a multi-step edit practical — the file is not reopened from scratch each time.
What it is
A single-tool file editor where the command argument selects the operation, described by its author as identical to Claude's built-in text_editor_20241022 tool.
What you get
- Viewing a file scoped by view_range, so a large file is read as a slice rather than whole
- File creation from file_text at a given path
- In-place replacement of old_str with new_str
- Insertion of text at a chosen insert_line
- State that persists across command calls, so a sequence of edits stays in one session
Requirements
Nothing — no account, no key. The paths you pass must be reachable on the machine the server runs on.
Setup effort
One command — npx -y mcp-server-text-editor