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.
      221 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
      109 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.
      25 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.1/5.0

    Scored across 29 tools

    Disambiguation4/5

    Most tools are clearly differentiated by backend (e.g., codex_ask, cursor_ask) and action (ask, continue, status). The multiple swarm tools (agent_swarm, preset_swarm, antigravity_image_swarm) have overlapping concepts and could cause minor confusion, but descriptions help.

    Naming Consistency4/5

    Predominantly uses snake_case with a clear backend_action pattern (e.g., grok_ask, opencode_status). Minor deviations like agent_swarm, preset_swarm, and swarm_presets lack a backend prefix, but overall the convention is readable and consistent.

    Tool Count3/5

    29 tools is heavy for a typical MCP server, but it reflects 8 distinct backends each needing ask/continue/status, plus swarm utilities. The count is borderline appropriate given the broad scope, though it could be reduced with a parameterized backend approach.

    Completeness4/5

    The surface covers asking, continuing, diagnostics, parallel swarms, predefined panels, and image generation. Minor gaps include no session listing/deletion or cancellation, but core workflows for each backend are complete.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources