Skip to main content
Glama
HackerWilson

agy-mcp-server

by HackerWilson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agy-mcp-server

No user-submitted related servers found.

    Related Servers

    • antigravity-mcp

      Kio-pon
      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
      MIT
    • Awaitless by xpluspro

      Awaitlessofficial

      xpluspro
      A
      license
      A
      quality
      A
      maintenance
      Durable MCP server for managing long-running jobs locally, over SSH, or on Slurm clusters. Jobs survive client disconnects and return exit codes, bounded logs, and JSON artifacts.
      11
      41 PyPI
      1
      MIT

    • agy-worker

      elio-zwd
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for local AGY worker runtime, enabling controlled task execution with permission checks, evidence collection, and status tracking for build, browser, and image workflows.
      -

    • mcp-job-queue

      tommypj
      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
    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.1/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a distinct purpose: starting new tasks, continuing sessions, submitting async jobs, checking status, fetching results, canceling, listing sessions, diagnosing, reading transcripts, and listing models. There is no ambiguity between them.

    Naming Consistency4/5

    The majority follow the 'antigravity_' prefix pattern with verb suffixes (e.g., antigravity_continue, antigravity_start). The one exception is 'run_antigravity', which inverts the order but remains clear. Overall, the naming is predictable and readable.

    Tool Count5/5

    With 10 tools, the server is well-scoped for managing Antigravity agent tasks. Each tool serves a necessary function, covering execution, monitoring, history, diagnostics, and model discovery without bloat.

    Completeness5/5

    The toolset covers the full lifecycle of agent tasks: starting (sync/async), continuing, checking status, retrieving results, canceling, listing sessions, reading transcripts, and diagnosing the environment. No critical gaps are apparent for the intended domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources