Skip to main content
Glama
MCP Agent Operations

MCP Agent Operations

Related Servers

Alternatives to MCP Agent Operations

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Enables LLM agents to perform local development and automation over MCP STDIO, including project context retrieval, file read/write and patching, shell/Python execution, Git inspection, work-state tracking, and validation. It runs as a local Python process with Dev and Safe execution modes and audit logging for trusted single-developer environments.
      16
      Apache 2.0
    • F
      license
      A
      quality
      D
      maintenance
      Lightweight MCP server that exposes tools for system information and weather lookup, designed for agent integration via stdio.
      1
      -
    • A
      license
      B
      quality
      D
      maintenance
      Production-grade MCP server that gives AI agents safe access to your local dev environment: filesystem, databases, processes, and OpenAPI specs.
      15
      40 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight, stdio-based MCP server enabling AI assistants to perform local file system operations like reading, writing, searching, and executing commands.
      5,198 npm
      MIT

    TDQS

    B3/5.0

    Scored across 26 tools

    Disambiguation3/5

    The tool set is split into reasonably clear sub-domains (claim_*, skill_*, reference_*, verify_*, hierarchy), but several near-pairs invite misselection: skill_read vs skill_load, skill_read_resource vs skill_resource_load, and claim_extend vs claim_extend_deadline differ only in plurality or nuance. The long inline descriptions clarify the distinctions, but an agent must read them carefully to choose correctly.

    Naming Consistency3/5

    Most tools use a domain-prefix convention (claim_acquire, skill_list, reference_load, verify_yaml), but the hierarchy and detection tools break it by leading with the verb (create_hierarchy_plan, render_hierarchy_html, detect_technology_skills) and capture_repository_state stands alone. The mixture of prefix-first and verb-first orderings means there is no single predictable pattern, though each name is still readable.

    Tool Count2/5

    At 26 tools the surface is heavy, and it spans six loosely related sub-domains (claims, skills, references, hierarchy plans, verification, capture) rather than one coherent domain. Many tools are legitimate, but the aggregate exceeds what an agent can hold comfortably and pushes past the 25-tool threshold.

    Completeness4/5

    The claim lifecycle is essentially complete (acquire, extend, extend_deadline, heartbeat, release, reset, status, report, journal maintenance), and skills cover list/find/read/load/resources/refresh/validate/detect. Minor gaps remain: hierarchy plans can be created, updated, and rendered but never listed, read back, or deleted, and reference handling lacks a validate counterpart to reference_refresh.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues