Skip to main content
Glama
SinanTufekci

agent-intern

by SinanTufekci
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to agent-intern

No user-submitted related servers found.

    Related Servers

    • agent-rack

      lakpriya1s
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that bridges CLI coding agents like Claude Code, Codex, opencode, and Antigravity into any MCP client, enabling synchronous and asynchronous task execution, follow-up input, and a structured code review tool.
      103 npm
      1
      MIT

    • cc-agent

      Gonzih
      A
      license
      A
      quality
      D
      maintenance
      MCP server that spawns autonomous Claude Code agents in GitHub repos, enabling task delegation with persistent state, multi-step workflows, and job monitoring.
      47
      187 npm
      2
      Apache 2.0

    • agent-bridge-mcp

      yukinuma-cpu
      A
      license
      A
      quality
      C
      maintenance
      An MCP server and HTTP gateway that dispatches coding tasks to Claude Code, Codex, and Antigravity CLI sessions, keeps track of those sessions, and optionally runs an implement → review → verify loop against a real repository.
      6
      MIT

    • kilo-mcp

      primax79
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that bridges Claude with KiloCode, enabling Claude to act as architect and delegate coding tasks to Kilo's fast CLI agent while monitoring progress and reviewing results.
      MIT

    • antigravity-mcp

      k12club
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets Claude Code call the Google Antigravity CLI (agy) headlessly for a second opinion from a different model family, or to have agy read project files on Claude's behalf so large files never enter Claude's context window.
      39 npm
      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.3/5.0

    Scored across 24 tools

    Disambiguation5/5

    Every tool is namespaced by backend and action (ask/continue/status), so the 7-provider matrix is immediately clear. The swarm and image variants are also distinct: single vs. parallel, text vs. image. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tools follow a consistent lowercase snake_case pattern with a backend prefix and a predictable action verb: ask, continue, or status. Even the swarm/image tools fit the broader convention, making the naming scheme easy to infer.

    Tool Count3/5

    24 tools is on the heavy side and falls in the 16-25 borderline range. However, the count is systematic: 7 backends × 3 core operations plus a few genuinely additive swarm/image tools, so the size is justifiable even if it feels large.

    Completeness4/5

    The core lifecycle for each backend is covered well: new session (ask), resume (continue), and diagnostics/status. Minor gaps exist, such as no explicit cancel/list-session operations and image/swarm support only for Antigravity, but these are workable and the main workflows are complete.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources