📡 MCP Radar

luckeyfaraday/frontier-orchestrator

Multi-agent orchestration for Claude Code: MCP server + skill that keeps Claude as lead engineer while delegating backend work to OpenAI Codex and frontend/design work to Kimi

⭐ 6 stars
⑂ 0 forks
TypeScript
momentum ▲ 12.0
created 2026-07-17
on radar since 2026-07-19
star trend 4 → 6 since 2026-07-19
agentic-codingai-agentsclaudeclaude-codecodexdeveloper-toolsmcpmcp-servermodel-context-protocolmulti-agentorchestrationtypescript
View on GitHub ↗

About frontier-orchestrator

Frontier Orchestrator — Multi-Agent Orchestration for Claude Code

Frontier Orchestrator is a Model Context Protocol (MCP) server and Claude Code skill that turns Claude into the lead engineer of a multi-agent team. Claude decomposes tasks, defines cross-stack contracts, and verifies results — while delegating:

- Backend work (APIs, databases, migrations, auth, infrastructure, security, backend tests) to OpenAI Codex - Frontend and design work (UI, UX, components, styling, accessibility, animation, client state) to Kimi Code - Tooling and mechanical maintenance (build configuration, dependency upgrades, CI, release automation, generated boilerplate, repository transformations, test/lint cleanup) to Grok Build

Each specialist runs as a sandboxed subprocess in your repository, receives a role-scoped brief with explicit file ownership and acceptance criteria, and reports back in a structured format that Claude reviews before anything reaches you.

Frontier coding agents have different strengths. Instead of asking one model to do everything, Frontier Orchestrator routes each part of a full-stack task to the agent best suited for it — with enforced coordination discipline so agents never trample each other's changes:

- Domain-first routing — backend behavior goes to Codex, frontend and UX behavior goes to Kimi, and only domain-neutral tooling or mechanical maintenance goes to Grok unless you explicitly override routing. Grok is never selected solely because it is faster. - Workspace mutation guard — two specialists cannot edit overlapping directories at the same time unless C

From the project README.

Maintaining this server?

Add the radar badge to your README — it shows your project was picked up by MCP Radar and links to this page:

[![On MCP Radar](https://mcp.liqiwa.com/badge.svg)](https://mcp.liqiwa.com/s/luckeyfaraday--frontier-orchestrator.html)

Related MCP servers

azimov777/casefile

The task tracker your AI agents keep for each other: every task carries a case file, so the next agent picks up where the last one stopped. MCP server + live board. Self-hosted, one-line install.

⭐ 3TypeScript
coffeecoproject/layermap

LayerMap MCP: a layered map of your codebase for coding agents: callers, callees and the impact of a change, for TypeScript, JavaScript, Go, Python and Java. MCP server, CLI, and plugins for Claude Co

⭐ 5TypeScript
adityajha2005/decisionkit

Fast, cheap, probability-scored decisions for coding agents, scripts and CI. CLI + MCP server + Claude Code plugin for the OpenAI Decisions API and Jev (TypeSafe AI).

⭐ 4TypeScript
00200200/usagetrim

Keep the signal. Cut the noise. Local CLI + MCP — fold verbose tool output for Claude Code, Codex, Cursor & Desktop.

⭐ 11Python
zriyox/codex-supervisor-mcp

Codex MCP server: run parallel Codex CLI workers in isolated git worktrees, state on disk, web dashboard, auto-update.

⭐ 3JavaScript
NiazMorshed2007/jev-review

Local-first MCP plugin for continuous software-quality review by AI coding agents, powered by Jev.

⭐ 209TypeScript

📬 Get the weekly radar in your inbox

The top new MCP servers of the week, every Monday. No spam, unsubscribe anytime.