Skip to main content
Glama
reaper1067MSX

MAGI Orchestrator

by reaper1067MSX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to MAGI Orchestrator

No user-submitted related servers found.

    Related Servers

    • Hermes Squad

      BarnsL
      A
      license
      Not graded
      quality
      B
      maintenance
      Multi-agent AI orchestrator that runs parallel coding agents in isolated sessions with self-improving intelligence, exposed via an MCP server for task execution and management.
      MIT

    • overmind-mcp

      DeamonDev888
      A
      license
      Not graded
      quality
      B
      maintenance
      Orchestrates and controls multiple AI agent CLIs (Claude-Code, Gemini-cli, etc.) via a unified MCP server, enabling complex multi-agent missions with shared memory and HTTP singleton architecture.
      802 npm
      2
      MIT

    • Loki Mode

      asklokesh
      A
      license
      Not graded
      quality
      A
      maintenance
      Autonomous spec-to-product coding-agent CLI. Its MCP server exposes 34 tools over stdio: project state and task-queue ops, memory retrieve/store, code search, quality and verification reports, repo hotspots/co-changes, and structured findings/learnings.
      13,524 npm
      1,088
      Business Source 1.1

    • opencode-mcp-bridge

      Dheerax
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that lets any AI tool delegate tasks to the OpenCode CLI as a subagent, with multi-session orchestration, event tracking, and task contracts.
      28
      4 npm
      1
      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

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    get_magi_status and run_magi_iteration have clearly distinct purposes: one retrieves runtime status, the other executes an iteration. No overlap or ambiguity.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern: get_magi_status and run_magi_iteration, using snake_case throughout.

    Tool Count3/5

    With only 2 tools, the server feels thin for an 'Orchestrator' concept. However, the tools cover basic status and execution, so it is borderline appropriate.

    Completeness2/5

    The tool surface lacks many expected operations for an orchestrator, such as agent management, task listing, or configuration. Significant gaps exist.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources