Skip to main content
Glama
plumbkit

plumb

Official
by plumbkit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Local

Related Servers

Alternatives to plumb

No user-submitted related servers found.

    Related Servers

    • ARNO

      julianbei
      A
      license
      A
      quality
      A
      maintenance
      The IDE for agents — read by symbol, edit against a revision, validate with your own build, revert. It is a local stdio MCP server for coding agents. It reads code by symbol with tree-sitter and real language servers (Go, Java, Scala, TypeScript, Python, Rust, Ruby), edits against a known revision and returns compiler diagnostics with each edit, runs the repository's own build, test etc.
      12
      Apache 2.0

    • uacos

      caotiensinh
      A
      license
      Not graded
      quality
      C
      maintenance
      Local-first code intelligence and safety layer for AI coding agents. MCP server exposes dependency graph, impact analysis, and AST-compressed repo context, backed by typed local memory, patch-scope safety gates, and git-independent transaction rollback.
      1
      MIT

    • my-pi

      BoxBoxmari
      A
      license
      C
      quality
      B
      maintenance
      Local-first MCP runtime for coding agents with bounded workspace access, content-preconditioned writes, AST search, LSP navigation and diagnostics, and Git status/diff. Designed to give coding agents useful repository access without treating unrestricted shell access as the default integration boundary.
      2
      13
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 58 tools

    Disambiguation3/5

    Many tools overlap by category—search (search_in_files, find_replace, workspace_search, topology_search), read (read_file, read_symbol, read_multiple_files, file_outline), and edit (edit_file, find_replace, transaction_apply, replace_symbol_body). The descriptions draw careful boundaries and cross-reference alternatives, but with 58 tools an agent can still misselect among similar-sounding options.

    Naming Consistency4/5

    Names are overwhelmingly snake_case and mostly verb_noun (write_file, find_references, run_task), with no camelCase or chaotic mixing. A few bare nouns (git, diagnostics) and noun phrases (file_outline, workspace_symbols) are minor deviations, but the pattern stays predictable.

    Tool Count1/5

    58 tools far exceeds the 3–15 well-scoped range and the 25+ 'too many' threshold, placing it in the extreme-mismatch tier by the rubric. The breadth reflects a large platform, but the surface is very heavy for an agent to navigate.

    Completeness5/5

    Coverage is exceptionally broad: file CRUD, LSP navigation and refactoring, topology analysis, memories, multi-agent collaboration, git, task running, and mutation testing. No obvious domain gap stands out.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources