Visitar URL original
Patchloom alternatives | Glama
Skip to main content
Glama
Patchloom

Patchloom

Official

Related Servers

Alternatives to Patchloom

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP 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.
      3
      15 npm
      3
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      AST-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.
      2
      28
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A 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.
      28
      11
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Advanced 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.
      1
      10
      MIT

    TDQS

    B3.4/5.0

    Scored across 66 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count2/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessUsually handled