MAGI Orchestrator
Integrates with Google Gemini API, supporting models like gemini-2.0-flash for task-based AI orchestration.
Integrates with OpenAI API for task-based AI orchestration using OpenAI models.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MAGI Orchestrator run build-auth-layer"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MAGI is a high-performance, task-based AI orchestrator designed to bring structure, persistence, and specialized intelligence to autonomous development. It operates as a bridge between your preferred AI models and your local environment, functioning simultaneously as a powerful interactive CLI and a background Model Context Protocol (MCP) server.
π Why MAGI? (Key Benefits)
Professional Interactive UI: Inspired by Claude Code, featuring dimmed reasoning for better focus, real-time action spinners, and clean result boxes.
Hybrid Power: Use it directly in your terminal for dedicated focus, or annex it to your favorite AI client (Gemini CLI, Claude Desktop) via MCP.
Persistent Orchestration: Unlike standard chat interfaces, MAGI manages its own state in a local
.magidirectory, including progress logs, activity history, and strict Guardrails (Signs) to prevent AI loops.Native SDK Integration: Fast and secure connections to official Google Gemini, Anthropic Claude, and OpenAI SDKs. No middleman proxies.
Zero-Touch Automation: Registration and skill installation happen automatically. Just install and start orquestrating.
Related MCP server: Agentic Control Framework (ACF)
π¦ Installation
Install MAGI Orchestrator globally via npm to get the magi command:
# Official installation
npm install -g magi-orchestratorNote: The automatic registration script (postinstall) will detect your Gemini CLI and Claude Desktop configurations and inject the MAGI server/skill automatically.
π How it Operates (Quick Start)
Option 1: Interactive CLI Mode (Recommended for Focus)
Run tasks directly from your terminal with rich, stylized feedback.
# Execute a task iteration interactively
magi run "build-auth-layer"Option 2: The "Annexed" Mode (Skill Injection)
Open your Gemini CLI and use the native skill:
/magi fix-login-bugMAGI will run in the background and report progress directly in your chat session.
βοΈ Configuration
MAGI looks for a magi-config.json file in your project directory. If not found, it uses sensible defaults.
{
"agents": [
{
"name": "gemini-flash",
"type": "gemini",
"model": "gemini-2.0-flash"
},
{
"name": "claude-sonnet",
"type": "claude",
"model": "claude-3-5-sonnet-20241022"
}
],
"defaultAgent": "gemini-flash",
"stateDirectory": ".magi"
}π Authentication
Set your API keys as environment variables:
GEMINI_API_KEY,ANTHROPIC_API_KEY,OPENAI_API_KEY.
π Operation Mechanics: The .magi Directory
MAGI keeps your project context clean by orchestrating everything inside the .magi folder:
progress.md: Tracking success criteria and current status.guardrails.md: Active "Signs" learned from previous failures to guide the AI.activity.log: Detailed history of every decision and action.
π Available CLI Commands
Command | Description |
| Start/Continue a task iteration interactively. |
| Manually trigger auto-registration in AI clients. |
| Start the MCP server (STDIO). |
| Report the current version (v1.2.1). |
Available Tools
2 toolsget_magi_statusA
Retrieve MAGI runtime status, default agent, available agent adapters, and resolved state directory.
Inputs: no named parameters.
run_magi_iterationA
Execute one MAGI iteration for a task using agentName when provided, otherwise the configured default agent.
Inputs: taskName (required), agentName.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 2 tools
get_magi_status and run_magi_iteration have clearly distinct purposes: one retrieves runtime status, the other executes an iteration. No overlap or ambiguity.
Both tools follow a consistent verb_noun pattern: get_magi_status and run_magi_iteration, using snake_case throughout.
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.
The tool surface lacks many expected operations for an orchestrator, such as agent management, task listing, or configuration. Significant gaps exist.
Maintenance
Related MCP Connectors
Task management your AI agents can actually run. One line becomes a context-ready task over MCP.
Nifty's MCP server β exposes tasks, projects, messages, and files as tools for AI agents.
LLM Orchestration Agent (Mcp)
Persistent memory, knowledge graph, task management and more for AI agents via MCP.
Related MCP Servers
- AlicenseNot gradedqualityFmaintenanceAn MCP server that orchestrates AI coding assistants (Claude Code CLI and Gemini CLI) to perform complex programming tasks autonomously, allowing remote control of your local development environment from anywhere.140MIT
- AlicenseDqualityDmaintenanceAI-native orchestration layer with 80+ tools for task management, code editing, browser automation, terminal control, and persistent memory across CLI, local MCP, and cloud deployments.697 npm31ISC
- AlicenseNot gradedqualityBmaintenanceOrchestrates 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.1,032 npm2MIT
- AlicenseNot gradedqualityBmaintenanceMulti-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