Skip to main content
Glama
jagones84

headroom_agent_mcp

by jagones84
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to headroom_agent_mcp

No user-submitted related servers found.

    Related Servers

    • secretary-mcp

      Ellen-11
      F
      license
      A
      quality
      C
      maintenance
      Enables main agents to delegate memory retrieval, web research, and multi-step tasks to internal sub-agents, returning concise conclusions while keeping detailed tool calls and raw content out of the main context.
      3
      -

    • Ultra-Eye

      Zhihong0321
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to delegate file reads, command output triage, page fetching, and image inspection to cheap flash models, returning concise answers and verified pointers while keeping raw dumps out of the main model's context.
      MIT

    • openkrak-mcp

      FrnzJulianBergmann
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to pre-compute repository structure and access structured intelligence briefs, including dependency graphs, hotspots, and blast radius, reducing token usage and improving code understanding.
      104 npm
      1
      -

    • BoteX

      kubainter
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP-compatible clients to delegate multi-step coding tasks to an autonomous subagent that reads outlines, applies validated patches, manages workspace memory, and returns structured results with rollback and cost tracking.
      12
      Apache 2.0
    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

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap between tools. run_discovery has a clearly defined purpose and inputs, making it unambiguous for an agent to select.

    Naming Consistency5/5

    The single tool name run_discovery follows a clear verb_noun convention. There are no other tools to create naming inconsistencies or mixed conventions.

    Tool Count4/5

    One tool is minimal, but it is appropriate for a narrowly scoped discovery/triage subagent. The count feels slightly thin compared to typical multi-tool servers, but the server's purpose is focused enough that a single tool can reasonably fulfill it.

    Completeness4/5

    The tool covers the stated discovery domain across docs research, logs triage, and codebase discovery, with support for scope paths, query hints, and safe terminal commands. Minor gaps exist around iterative refinement or returning raw context, but the core triage workflow is well covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources