peon-orchestrator
Provides integration with OpenAI, enabling AI agents to use OpenAI models with configurable iteration limits and timeouts.
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., "@peon-orchestrator Spawn a coder agent, assign it to fix the bug in auth.js, then monitor status."
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.
Peon AI Orchestrator
MCP server orchestrator for managing AI agents (coder, reviewer, tester) in the Peon AI ecosystem.
Features
Agent Management: Dynamic spawning, stopping, and monitoring of agent processes.
Asynchronous Task Execution: Assign tasks and receive a
task_idimmediately. Agents process tasks in parallel.Persistent Task History: Global history of all tasks, statuses, and results, saved to disk and accessible even after agent termination.
Shared Atomic Storage: Thread-safe, file-based "pit" (
.peon-orchestrator/storage/) for data exchange with safe key encoding (Base64).AI Integration: OpenAI support with configurable iteration limits and timeouts.
Conductor-Ready: Detailed task statuses including
missing_toolsandpartialflags for iterative agent coordination.
Related MCP server: any-model-plugin
Installation
It is recommended to use uv for dependency management and execution.
1. Install uv
If uv is not installed yet:
curl -LsSf https://astral.sh/uv/install.sh | sh2. Install from GitHub
uv pip install git+https://github.com/prmgint/peon-ai-orchestrator.git3. Local Installation (for development)
uv pip install -e .Eclipse Configuration (MCP)
Open MCP settings in Eclipse (Peon AI / MCP Settings).
Add a new server:
Name:
peon-orchestratorCommand:
uvxArgs:
peon-orchestrator
Set environment variables:
ORCHAI_API_KEY,ORCHAI_MODEL(e.g.,gpt-4o).
Usage
The orchestrator provides the following tools via MCP:
Agent Management
spawn_agent(role_name, system_prompt, tools?)- Create an agent. Returnsagent_id.list_agents()- List agents withbusystatus and task counts.stop_agent(agent_id)- Stop an agent.
Task Management
assign_task(agent_id, task, tools?, max_iterations?)- Assign task asynchronously. Returnstask_id.task_status(agent_id, task_id)- Get detailed status (pending,running,done,error,agent_stopped).task_result(agent_id, task_id?)- Get enriched result withoutputandmissing_tools.aggregate_results(tasks)- Collect results for multiple{agent_id, task_id}pairs.cleanup_task_history(older_than_seconds?)- Remove old task metadata.
Storage Operations
read_storage(key)- Read value from shared storage.write_storage(key, value)- Write value (atomic). Protected keys are restricted.list_storage()- List all keys.storage_cleanup(pattern?, exclude?)- Remove keys using glob patterns.
Conductor Workflow
Spawn agents with specific roles.
Assign a task to an agent.
Poll
task_statusuntil it isdone.Analyze
missing_toolsin the result.Iterate by spawning new agents or reassigning with more tools if needed.
Aggregate sub-task results into a final synthesis.
License
MIT License.
Available Tools
14 toolsagent_statusC
Get the status of an agent
Inputs: agent_id (required).
aggregate_resultsC
Aggregate results for multiple tasks including missing_tools, status and output.
Inputs: tasks (required).
assign_taskA
Assign a task to an agent asynchronously. Returns task_id immediately. Use task_status and task_result to track progress.
Inputs: task (required), agent_id (required), tools, max_iterations.
broadcastA
Send a message to all running agents in parallel. Returns list of {agent_id, task_id}.
Inputs: message (required).
cleanup_task_historyC
Remove old tasks from history.
Inputs: older_than_seconds.
list_agentsA
List all managed agents with status, busy flag, current task and task counts
Inputs: no named parameters.
list_storageA
List all keys in shared storage
Inputs: no named parameters.
read_storageC
Read data from shared storage
Inputs: key (required).
spawn_agentC
Spawn a new agent with the given role and system prompt
Inputs: role_name (required), system_prompt (required), tools.
stop_agentB
Stop a running agent
Inputs: agent_id (required).
storage_cleanupA
Remove keys from storage matching a glob pattern with optional exclusion.
Inputs: exclude, pattern.
task_resultB
Get the result of a task enriched with task_id and status. If task_id is omitted, returns the last result.
Inputs: agent_id (required), task_id.
task_statusB
Get detailed status of a specific task including missing_tools, partial flag, and timestamps.
Inputs: task_id (required), agent_id (required).
write_storageB
Write data to shared storage. Handles JSON strings automatically. Protected keys are restricted.
Inputs: key (required), value (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Most tools are clearly distinct: agent lifecycle tools (list, spawn, stop, status) and task tools (assign, status, result, aggregate) separate cleanly. Minor overlap exists between list_agents and agent_status since list_agents already includes status fields, but descriptions clarify the singular focus of agent_status. Storage tools are unambiguous.
Naming mixes conventions: verb_noun (list_agents, spawn_agent, assign_task, read_storage, write_storage, aggregate_results), noun_noun (task_status, task_result, agent_status), and single verb (broadcast). While readable, the pattern is not uniform and violates expectations (e.g., agent_status vs status_agent, storage_cleanup vs cleanup_storage).
14 tools is within a reasonable range for an orchestrator covering agent lifecycle, task management, and shared storage. Each tool serves a distinct purpose and the count reflects the breadth of functionality without being excessive.
The tool surface covers core workflows well: agent creation/listing/removal/status, task assignment/tracking/results/aggregation, and storage read/write/cleanup. Minor gaps like a direct task cancellation or agent update are missing, but these are edge cases not fundamental to the domain.
Maintenance
Related MCP Connectors
Task manager for AI agents. Orchestrate agents to achieve large goals in unified control plane.
Durable background job execution, async task scheduling, and state persistence for AI agents.
Hosted runtime for persistent agent teams, durable workflows, memory, schedules, and goals.
Multi-agent coordination for AI agents: shared spaces, tasks, search, mailbox and persistent state.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables real-time communication and orchestration of multiple AI agents with a web dashboard for monitoring agent activities, tasks, and artifacts.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to delegate tasks, run adversarial reviews, and manage background jobs across multiple models and providers via anymodel_* tools.Apache 2.0
- AlicenseAqualityBmaintenanceEnables orchestrating external AI agents to execute development tasks with asynchronous management, automated acceptance verification, failure rework loops, and optional visual baseline validation.1116 npmApache 2.0
- AlicenseCqualityBmaintenanceEnables multiple CLI-based AI agents to collaborate as a coordinated team through shared task queues, shared memory, and a message bus, with DAG orchestration, rate-limit avoidance, parallel dispatching, and long-task management.633MIT