Rawe Claude Agent Orchestrator
rawe-claude-agent-orchestrator is a Claude Code plugin for the Build phase that orchestrates specialized agents, plugins, and MCP servers with shared context.
by rawe · github.com/rawe/claude-agent-orchestrator
Route work across specialized Claude subagents, plugins, and MCP servers instead of one monolithic chat session.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install rawe-claude-agent-orchestrator@rawe/claude-agent-orchestratorBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:rawe/claude-agent-orchestrator") and the paste-ready config with skillselion.get_install_config("plugin:rawe/claude-agent-orchestrator").
What it does
rawe-claude-agent-orchestrator is a compact Claude Code plugin pair for builders who outgrow one general assistant and need deliberate delegation. It focuses on orchestrating specialized agents—each with plugins or MCP tools—so research, implementation, and review can run as separate roles with cleaner context boundaries. The described context store implies you can pass state between steps without pasting entire transcripts, which matters when you ship alone and cannot afford contradictory agent advice. Use it when your stack already includes multiple MCP servers or plugin packs and you want a single orchestration layer in Claude Code. It is community-maintained with minimal public traction, so validate behavior in a throwaway repo before relying on it for production workflows.
Highlights
- 2-plugin orchestrator bundle for Claude Code multi-agent setups
- Coordinates specialized subagents with plugin and MCP server support
- Context store keyword signals persisted handoff between agent roles
- Designed for delegation patterns rather than single-shot prompts
Why builders use it
One Claude session with every tool enabled becomes slow, confused, and hard to audit when you are juggling several agent roles.
After install, you can delegate tasks to focused subagents and MCP-backed plugins while the orchestrator keeps context structured across steps.
At a glance
- Type - Plugin in AI Agents.
- Adoption - 0 installs, 1 stars, 0 votes.
FAQ
Who is rawe-claude-agent-orchestrator for?
It is for solo builders and tinkerers who run several Claude Code plugins or MCP servers and need a coordinator agent instead of one overloaded session.
When should I use rawe-claude-agent-orchestrator?
Use it when tasks naturally split across roles—research, implement, verify—and you want subagents plus MCP without manual copy-paste handoffs.
How do I add rawe-claude-agent-orchestrator to my agent?
Add the rawe/claude-agent-orchestrator plugin from its GitHub repo in Claude Code, enable both plugins, then configure your subagents and MCP servers the orchestrator expects.
Comments
Share how you use rawe-claude-agent-orchestrator, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.