Patchloom
OfficialRelated Servers
Alternatives to Patchloom
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that combines Read+Edit file operations into single tool calls. 80-95% fewer tool calls formulti-file refactoring across Claude, Cursor, Windsurf, and more.315 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable coding agents to perform batched, token-efficient file and search operations with tolerant, automatically verified edits and diffs. It supports sandboxed workspace access, optional command execution, caching, and post-edit syntax/import checks.MIT
- AlicenseAqualityBmaintenanceAST-targeted code editing MCP server with 28 surgical tools for structural edits across 11 languages. Built on tree-sitter, replaces brittle search/replace with byte-correct edits keyed by symbol names.228MIT
- AlicenseAqualityBmaintenanceA robust, language-agnostic Model Context Protocol (MCP) server that provides AI coding agents with the ability to edit files surgically via Abstract Syntax Trees (AST) instead of relying on token-heavy, brittle search-and-replace or diff operations.2811MIT
- AlicenseAqualityDmaintenanceAdmission-control MCP server for AI coding agents — rejects bad file edits without coaching the LLM.31MIT
- AlicenseBqualityDmaintenanceAdvanced code search and transformation MCP server for AI assistants. Combines ugrep's speed with intelligent replace capabilities, dry-run previews, and language-aware refactoring across 11 tools.110MIT
TDQS
Scored across 66 tools
Tools are largely separated by domain prefixes (ast_, doc_, md_, file/apply/undo), and descriptions explicitly scope overlapping-looking operations such as doc_set vs doc_update and replace_text vs ast_replace. Still, the large doc/markdown/AST clusters contain several near-neighbors that require careful reading to select correctly.
Almost all tools use snake_case with a consistent domain-prefix convention (ast_, md_, doc_) plus verb_noun file/search/plan names. A few names are noun-like (server_info, operation_schema, git_status) rather than verb_noun, but the overall pattern is predictable.
66 tools is far beyond the recommended 3-15 range and exceeds the 25+ 'too many' threshold; the broad patch/edit domain justifies more than a small set, but this volume imposes high selection overhead on an agent. The surface would benefit from consolidation or tiered exposure.
Coverage is extensive across file editing, AST manipulation, markdown, structured documents, search, planning, and undo, with CRUD-style coverage for most resources. Minor gaps remain, such as markdown section/table deletion, notebook read/create, and directory operations, but core workflows are not dead-ended.