Skip to main content
Glama

Related Servers

Alternatives to antigravity-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients such as Claude Code, Codex, and Cursor to dispatch background subagent jobs to the Antigravity IDE's local agent engine and collect results asynchronously. Jobs run through the IDE's authenticated session without an API key, with optional Gemini REST fallback and on-disk job history.
      6
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to asynchronously submit tasks to a persistent coding agent already running on a development machine, disconnect, and retrieve results later through a secure, policy-controlled gateway.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables MCP clients to submit long-running jobs that are executed safely in isolated child processes with a durable SQLite queue, configurable timeouts, retries with backoff, and backpressure.
      5
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables agents to submit and manage persistent, dependency-aware task graphs with immutable artifacts, resource reservations, durable event streaming, and retryable process execution over MCP.
      12
      MIT
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables MCP clients to securely execute bounded coding tasks through registered backends, with idempotent job submission, status polling, and artifact retrieval. It isolates each job in Git worktrees and supports optional branch publishing and pull request creation under strict policy constraints.
      -

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool maps to a distinct action: workspace inspection, model listing, async dispatch, job status/list/cancel, and synchronous code search. The only mild overlap is between check_agent_job and list_active_jobs (both about job state) and between dispatch_gemini_agent and gemini_code_search (both invoke Gemini), but descriptions clearly separate single-job inspection from enumeration and async background work from synchronous analysis.

    Naming Consistency4/5

    Six of seven tools follow a clean verb_noun snake_case pattern (get_active_workspace, dispatch_gemini_agent, list_available_models, check_agent_job, list_active_jobs, cancel_agent_job). gemini_code_search deviates by leading with a noun/namespace, a minor inconsistency but still readable and predictable.

    Tool Count5/5

    Seven tools is well-scoped for an IDE orchestration server, with each tool earning its place across discovery, dispatch, and job management. Nothing feels redundant or padded.

    Completeness4/5

    The subagent lifecycle is fully covered (dispatch, check, list, cancel) alongside workspace discovery, model enumeration, and synchronous code analysis. Minor gaps exist—no retry/resume of a job, no follow-up message to a running agent, and no explicit wait-for-completion primitive—but agents can poll with check_agent_job.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues