Skip to main content
Glama
horizonmax11-sketch

AGY Observer MCP

by horizonmax11-sketch
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to AGY Observer MCP

No user-submitted related servers found.

    Related Servers

    • agy-worker-mcp

      thezoot3
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to run Google Antigravity CLI (agy) as durable, detached asynchronous jobs with a permission gate and broker-computed verdicts that do not trust agy's own exit code.
      9
      8 npm
      MIT

    • antigravity-delegate

      WangZhuo2015
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an agent to hand off bounded tasks to Gemini Flash through the Google Antigravity CLI, receiving live tool-progress notifications and a single compact final result over one MCP call. It runs event-driven with no polling, keeping raw events and evidence local while failing closed on errors, cancellation, or deadlines.
      MIT

    • antigravity-mcp

      alvarosw
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible coding agents to run the local Antigravity CLI as a coding agent, manage conversation context and common options, and inspect usage, quota, models, version, help, and read-only slash commands.
      18 npm
      MIT

    • Antigravity MCP Bridge

      Zythenth
      A
      license
      B
      quality
      A
      maintenance
      Enables delegating coding tasks to the official Antigravity CLI from any MCP client, with task listing, model selection, streamed event tracking, cancellation, and resumable sessions. Runs each task against an isolated copy of the repository so results can be previewed, tested, and only integrated into the original after explicit user confirmation.
      23
      249 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation3/5

    The set has several parallel read/note/create/execute tools across discussion, council, project, and run workflows. Descriptions help distinguish them, but an agent must carefully choose between similar pairs such as discussion_note vs council_note, discussion_read vs project_read, and discussion_create vs council_create.

    Naming Consistency4/5

    Nearly all tools use a consistent agy_ prefix and snake_case resource/action naming, e.g. agy_discussion_read, agy_council_round, agy_project_update. A few names are noun-only or less action-explicit, such as agy_run, agy_history, agy_status, and agy_info, but the overall pattern is predictable.

    Tool Count3/5

    At 20 tools, the surface is heavy and sits in the borderline range. The domain is genuinely complex, but the count is inflated by two parallel workflows (discussion and council) with analogous operations, making the set feel broader than necessary.

    Completeness4/5

    The surface covers creation, reading, notes, turns/rounds, recovery, extension, memory, project linkage, status, cancellation, and configuration. Coverage is strong, with only minor lifecycle gaps such as explicit deletion/archival controls beyond summary or status transitions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources