Agentic Team MCP
Enables agent execution through the Gemini Antigravity CLI and Google Gemini direct API providers.
Enables agent execution through the OpenAI direct API and supports heavy code generation via the Codex CLI.
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., "@Agentic Team MCPSpin up a three-tier team to refactor the auth module and have the CEO propose a plan first."
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.
Agentic Team MCP — Persistent Multi-Agent Orchestration for Model Context Protocol
Live interactive Web Studio floor visualization showing Root Watchdog supervision, hierarchical reporting trees, and dynamic agent collaboration links. (See animated preview: assets/web_studio_preview.gif)
Agentic Team MCP is an enterprise-grade, local-first multi-agent orchestration platform designed around the Model Context Protocol (MCP). It establishes a persistent, hierarchical agent workforce (Root Watchdog Supervisor → CEO Strategy → Manager Execution → Specialist Workers) that bridges native CLI coding environments (Claude Code, Gemini Antigravity, Codex) with unified direct API providers (DeepSeek, Z.ai/GLM, Google Gemini, OpenAI, and OpenRouter).
Author's Note
Abdulaziz Komilov (@menma4ever), student researcher in local model fine-tuning and quantization, building persistent, cost-effective multi-agent teams across native CLIs (Claude Code, Gemini Antigravity, Codex) and Model Context Protocol.
Modern agent frameworks often suffer from three fatal flaws: fragile ephemeral execution contexts, proprietary cloud lock-in, and ballooning API token costs. Agentic Team MCP was engineered to solve these problems by coupling persistent SQLite event sourcing with native CLI adapters (leveraging existing subscription authorizations like Claude Code, Gemini Antigravity, and Codex CLI) alongside high-efficiency open-weights models (DeepSeek-V3/R1 and GLM-5). The result is an autonomous, self-healing team architecture capable of executing complex engineering milestones locally, deterministically, and cost-effectively.
Related MCP server: MEMGRAPH-MCP
Visual Architecture
flowchart TD
subgraph ClientLayer["User & Client Layer"]
User["Developer / User"]
ClaudeDesktop["Claude Desktop"]
CursorIDE["Cursor IDE"]
WebBrowser["Web Browser (Studio GUI)"]
TelegramUser["Telegram Mobile Client"]
end
subgraph GatewayLayer["MCP & Gateway Layer"]
MCPServer["FastMCP Stdio Server<br/>(mcp_server/server.py)"]
WebStudio["Web Studio & REST Gateway<br/>(FastAPI / Uvicorn)"]
TelegramBridge["Telegram Supervisor Bridge<br/>(core/telegram_bridge.py)"]
end
subgraph CoreLayer["Orchestrator Core"]
Engine["Orchestrator Engine<br/>(engine/orchestrator.py)"]
SQLiteStore["SQLite Event Sourcing<br/>(team.sqlite3)"]
Queues["Task Queues & Loop Monitor"]
WatchdogBrain["Watchdog Supervisor Engine<br/>(core/watchdog_brain.py)"]
end
subgraph TeamHierarchy["Hierarchical Agent Team"]
Watchdog["Root Watchdog Agent<br/>(Global Supervisor & Bridge)"]
CEO["CEO Agent<br/>(Strategic Planning & Architecture)"]
Manager["Manager Agent<br/>(Milestone Breakdown & Task Dispatch)"]
Worker1["Specialist Worker 1<br/>(Implementation / Code)"]
Worker2["Specialist Worker 2<br/>(Documentation / QA)"]
end
subgraph ExecutionLayer["Execution Harnesses & Providers"]
subgraph CLIAdapters["Native CLI Harnesses"]
ClaudeCode["Claude Code CLI"]
AntigravityCLI["Gemini Antigravity CLI"]
CodexCLI["Codex CLI"]
HermesCLI["Hermes / OpenClaw"]
end
subgraph DirectAPI["Direct API Providers"]
DeepSeekAPI["DeepSeek (V3 / R1)"]
ZaiAPI["Z.ai / GLM-5"]
GeminiAPI["Google Gemini"]
OpenAIAPI["OpenAI"]
OpenRouterAPI["OpenRouter / SiliconFlow / Groq"]
end
end
User --> ClaudeDesktop
User --> CursorIDE
User --> WebBrowser
TelegramUser <--> TelegramBridge
ClaudeDesktop -->|"stdio MCP"| MCPServer
CursorIDE -->|"stdio MCP"| MCPServer
WebBrowser -->|"HTTP / WebSocket"| WebStudio
TelegramBridge <--> WatchdogBrain
MCPServer -->|"Engine Actions"| Engine
WebStudio -->|"REST / Event Streams"| Engine
WatchdogBrain <--> Engine
Engine <--> SQLiteStore
Engine <--> Queues
Watchdog -.->|"Supervises"| CEO
Watchdog -.->|"Supervises"| Manager
Engine --> CEO
CEO -->|"Dispatches Roadmap"| Manager
Manager -->|"Assigns Task"| Worker1
Manager -->|"Assigns Task"| Worker2
Worker1 --> CLIAdapters
Worker2 --> DirectAPIWhy Agentic Team MCP?
Feature | Agentic Team MCP | Traditional Multi-Agent Frameworks | Standard MCP Servers |
Persistence Model | Resilient SQLite Event Sourcing (resumes after restart/crash) | In-memory or ephemeral sessions | Ephemeral (lifetime of stdio pipe) |
Team Hierarchy | Strict 5-Tier (Watchdog → CEO → Manager → Specialists → Owner) | Flat peer-to-peer or unstructured swarm | Single-agent tool provider |
Execution Harness | Dual Harness (Native CLI Subprocesses + Direct API) | API-only (HTTP calls) | External tool execution only |
Cost Optimization | Subscribed CLI Auth Pools (Claude Code, Antigravity, Codex) | Per-token commercial billing only | Host application pays per call |
Local-First Security | Air-gapped local storage, zero telemetry, auto key-redaction | Cloud dashboard telemetry & logs | Depends on client implementation |
Real-time Web Studio | Full-screen canvas, live terminal streams, process monitors | Static CLI output or paid SaaS dashboard | None (headless) |
Human In The Loop | Telegram Mobile Bridge & Root Watchdog supervision | Webhooks or email alerts | Host client UI only |
Tool Protocol | Full Model Context Protocol (MCP) specification support | Custom proprietary tool schemes | MCP Standard |
Key Architectural Capabilities
1. Persistent Multi-Agent State & Event Sourcing
Unlike ephemeral agent systems that lose all state on reload, Agentic Team MCP records all state mutations, messages, agent definitions, and task outcomes in an event-sourced SQLite database (team.sqlite3). If your system reboots, the engine reconstitutes the full agent graph and automatically resumes pending assignments.
2. Multi-Account Google Auth Pool (core/auth_pool.py)
Directory Isolation: Per-account directory sandboxes (
auth/google/account_XX/) with separate credential vaults.Windows Keyring Vault Swap: Automated backup and capture of active tokens preventing profile contamination on Windows.
Sticky KV-Cache Affinity: Grants agents slot affinity (
forced_auth_slot_id) to maximize prompt cache hits.Automatic 429 Quota Failover: Detects rate limits or token saturation and fails over to healthy slots seamlessly.
3. Multi-Harness Subsystem (harness/)
Native CLI Subprocess Runners: Directly leverages your active terminal subscriptions (
agy,codex,claude) in headless mode without per-token charges.High-Throughput Direct API Client: Async SSE streaming client supporting DeepSeek-V3/R1, Zhipu GLM, OpenAI, Experiential Labs (
xpl), and Groq.Context Preservation & Handoffs: Automatically serializes transcripts on model/harness switches (
manager/.handoffs/<hash>.json) to prevent cognitive amnesia.
4. Root Watchdog & Autonomous Telegram Bridge (core/telegram_*)
Always-on Mobile Supervision: Connect via Telegram (
@ufljarvisbot) with strict chat ID whitelisting (5644286697).Human-like UX: 4.5s typing simulation loop, mobile-first formatting, and automated
[DISPATCH]&[SEND_FILE]directives.Multimodal Ingestion (
core/multimodal.py): Audio voice notes are transcribed via speech-to-text; images and PDFs are converted to native vision tokens.
5. Real-Time Web Studio GUI (web/)
Full-Screen Team Floor: Interactive node-link canvas showing agent states (
idle,working,resting,failed). Click the fullscreen icon to expand the floor to the entire display.Live SVG Message Vectors: Real-time traveling pulses along SVG vectors whenever agents exchange messages or report results.
Comprehensive Telemetry: Granular dashboards tracking
input_tokens,output_tokens,cache_read_tokens, and provider burn in real time.
6. Granular Security Boundary
Strict Workspace Sandboxing: Specialist workers operate strictly within their assigned project directories (
workers/<name>/).Automatic Key Redaction: Zero-secret leakage policy regex-redacts sensitive API keys and tokens across console streams and log files.
2-Minute Quickstart Guide
Prerequisites
Python 3.11+ installed and available on your system
PATH.Git installed.
(Optional) Installed CLI tools:
claude(Claude Code),agy(Antigravity CLI), orcodex(OpenAI Codex).
Step 1: Installation & Setup
Windows (One-Click Setup)
Clone the repository and run the automated PowerShell setup script:
git clone https://github.com/menma4ever/agentic-team-mcp.git
cd agentic-team-mcp
.\Setup.ps1Manual Virtual Environment Setup (Cross-Platform)
# 1. Clone the repository
git clone https://github.com/menma4ever/agentic-team-mcp.git
cd agentic-team-mcp
# 2. Create and activate a Python virtual environment
python -m venv .venv
# On Windows (PowerShell):
.venv\Scripts\Activate.ps1
# On Linux / macOS:
source .venv/bin/activate
# 3. Install core dependencies
pip install -r requirements.txtStep 2: Configuration
Copy the clean example settings template to settings.json:
cp settings.example.json settings.jsonEdit settings.json with your preferred API keys or enable local CLI harnesses:
{
"api_keys": {
"deepseek": "sk-your-deepseek-key",
"zai": "your-zai-api-key",
"gemini": "your-gemini-api-key",
"openai": "",
"anthropic": ""
},
"cli_auth_enabled": {
"claude": true,
"agy": true,
"codex": false
}
}Step 3: Launching the Platform
Launch Web Studio & Orchestrator Engine
On Windows, simply double-click Launch.cmd or run:
Launch.cmdAlternatively, from an activated virtual environment:
python main.pyThis automatically boots the background orchestrator service, launches the Web Studio GUI, and opens your default browser at http://127.0.0.1:8765/#token=<token>.
Available Command-Line Arguments
python main.py [OPTIONS]
Options:
--port INTEGER Port for web studio & engine (default: 8765)
--no-browser Start engine and studio without opening browser
--mcp Run as stdio Model Context Protocol (MCP) server
--console TEXT Open human-in-the-loop interactive console for agentStep 4: Connecting to MCP Clients
Agentic Team MCP operates as a high-performance stdio MCP server that connects directly to your background engine.
Claude Desktop Configuration
Add the server definition to your claude_desktop_config.json:
Windows:
%APPDATA%\Claude\claude_desktop_config.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"agentic-team": {
"command": "C:\\path\\to\\agentic-team-mcp\\.venv\\Scripts\\python.exe",
"args": [
"C:\\path\\to\\agentic-team-mcp\\main.py",
"--mcp"
]
}
}
}Cursor IDE Configuration
Add the configuration to .cursor/mcp.json in your workspace or global Cursor settings:
{
"mcpServers": {
"agentic-team": {
"command": "C:\\path\\to\\agentic-team-mcp\\.venv\\Scripts\\python.exe",
"args": [
"C:\\path\\to\\agentic-team-mcp\\main.py",
"--mcp"
]
}
}
}Available MCP Tools Reference
When connected via MCP, Agentic Team exposes a comprehensive set of orchestration tools:
Tool Name | Scope | Description |
| Workspace | Enumerate all active and completed multi-agent team projects. |
| Workspace | Initialize a new project and provision the root CEO agent. |
| Inspection | Retrieve the full hierarchical agent tree with live statuses and telemetry. |
| Owner | Inspect real-time execution event logs and command outputs. |
| Owner | Read authenticated conversation messages and handoff records. |
| Orchestration | Dispatch an operational Manager under the CEO for milestone management. |
| Orchestration | Provision specialized workers with assigned task descriptions and harnesses. |
| Messaging | Dispatch targeted, authenticated peer or hierarchy messages. |
| Management | Dynamically switch models or harnesses with saved state handoff. |
| Status | Query worker lifecycle stage, current activity, and recent outputs. |
| Cleanup | Safely decommission worker processes and clean up or archive workspaces. |
| Hierarchy | Bubble up blocking architectural or security issues to the CEO. |
| Action Bus | Unified action channel ( |
Directory Structure
agentic-team-mcp/
├── assets/ # Studio screenshots & preview assets
│ ├── web_studio_team_floor.png
│ ├── web_studio_preview.gif
│ └── web_studio_overview.png
├── Launch.cmd # Fast Windows launcher
├── Setup.ps1 # Automated PowerShell virtualenv & dependency setup
├── LICENSE # MIT License
├── README.md # Project documentation & guides
├── requirements.txt # Core dependencies
├── settings.example.json # Example configuration template
├── main.py # Main entry point (Web Studio, Engine & MCP Server)
├── core/ # Core supervisor, telegram bridge, auth pool & config
│ ├── auth_pool.py # Multi-account rotation & CLI auth slots
│ ├── catalog.py # Dynamic model & harness discovery
│ ├── config.py # Pydantic schema validation & redaction
│ ├── credential_store.py # Secure local credential storage
│ ├── multimodal.py # Visual analysis & image processing
│ ├── service.py # Engine lifecycle & process locking
│ ├── telegram_bridge.py # Telegram supervisor bridge & alert loop
│ ├── telegram_supervisor.py # Interactive mobile control endpoints
│ ├── watchdog_brain.py # Root Watchdog intelligence & evaluation
│ └── workspace.py # Sandboxed workspace directories
├── engine/ # Orchestration core & persistence
│ ├── actions.py # Agent action handlers & dispatching
│ ├── loop_monitor.py # Stuck-loop detection & runaway turn prevention
│ ├── message_router.py # Priority messaging & event routing
│ ├── models.py # Pydantic data models for agents & tasks
│ ├── orchestrator.py # Central event loop & agent scheduler
│ └── store.py # SQLite event-sourcing database layer
├── harness/ # Subprocess & provider execution harnesses
│ ├── cli_runner.py # PTY/pipe adapters for Claude, Antigravity, Codex
│ └── direct_api.py # Direct async streaming HTTP API client
├── mcp_server/ # Model Context Protocol stdio server
│ └── server.py # FastMCP tool declarations & engine proxy
├── tests/ # End-to-end integration & unit test suites
│ ├── test_auth_pool.py
│ ├── test_backend_audit.py
│ ├── test_engine.py
│ ├── test_google_quota_recovery.py
│ ├── test_release.py
│ ├── test_runtime_revision.py
│ ├── test_service.py
│ ├── test_telegram_bridge.py
│ └── test_watchdog_brain.py
└── web/ # Web Studio dashboard & REST API
├── app.py # FastAPI server & WebSocket endpoints
└── static/ # Interactive graph, terminal streams, and UICommunity & Feedback
We welcome contributions, feedback, and questions from researchers and builders working on autonomous multi-agent systems and MCP tooling.
Telegram: @zwyci / Bot: @ufljarvisbot
Discord:
77terminator77GitHub Issues: menma4ever/agentic-team-mcp/issues
GitHub Discussions: menma4ever/agentic-team-mcp/discussions
License
Distributed under the MIT License. See LICENSE for complete terms.
This server cannot be deployed
Maintenance
Related MCP Connectors
Agent-native collaboration network: orchestrate a team of long-running agents from any MCP client.
LLM Orchestration Agent (Mcp)
Control plane for autonomous software labor. Agents claim objectives over MCP with audit trail.
System-of-record notebook for AI coding agents: pages, datastores, tasks, skills over MCP.
Related MCP Servers
- 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.698 npm31ISC
- FlicenseAqualityDmaintenanceA durable multi-agent orchestrator for software development with explicit run graphs, checkpoint/resume capabilities, and project memory exposed through MCP resources and tools. It enables coordinated agent workflows for coding, review, repair, CI, and approval with SQLite-backed memory retrieval and pluggable research backends.10-
- AlicenseBqualityFmaintenanceEnables orchestrating multiple AI CLI agents (Claude Code, Codex, Gemini CLI, Copilot CLI) through a unified MCP interface for task delegation, cross-agent comparison, and specialized tools like code review and debugging.147 npm14MIT
- 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