Readedit
Related Servers
Alternatives to Readedit
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that reduces token consumption in AI coding assistants by up to 90% via structural reads, PreToolUse hooks, and tp-\* subagents.25687 npm5MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that reduces AI agent token usage by up to 90% through intelligent context compression. Enables efficient code exploration, multi-file refactoring, and debugging by providing tools for smart reading, searching, and managing code context.4MIT
- AlicenseAqualityAmaintenanceMCP server that keeps language server sessions warm and routes multiple languages through one process. Agents get persistent cross-file awareness, speculative execution (simulate edits before writing to disk), and 20 skills that encode correct multi-step operations like safe rename, blast-radius analysis, and end-to-end refactoring. Single Go binary, no runtime dependencies.50126MIT
- AlicenseBqualityAmaintenanceAgent-optimized MCP server that replaces built-in file, search, exec, and git tools with compact, structured JSON equivalents. Benchmarked 20–45% token savings for AI coding agents.202MIT
- AlicenseBqualityBmaintenanceMCP server connecting Claude/Cursor to Codex CLI, enabling code analysis via @ file references, multi-turn conversations, sandboxed edits, and structured change mode.13282 npm24MIT
- AlicenseAqualityAmaintenanceMCP Server for persistent code indexing. Gives AI assistants (Claude, Gemini, Copilot, Cursor) instant access to your codebase. 50x less context than grep.2254 npm43MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: multi_edit for editing multiple files (no reading), multi_read_edit for reading and optionally editing multiple files, and read_edit for single-file read+edit. No overlap.
All tools follow a consistent verb_noun pattern in snake_case: multi_edit, multi_read_edit, read_edit. The naming clearly communicates the function (edit vs read_edit) and scope (multi vs single).
With only 3 tools, the set is minimal but well-scoped for the server's focused purpose of reading and editing files. It's slightly on the low end but still reasonable.
The tool set covers all expected operations: reading, editing, single-file, multi-file, and combined read+edit. No obvious gaps for the stated domain of file editing.