mcp-orchestrator
Skill6 starsChanged 6 months agoMITView on GitHub
Discover available MCP servers, evaluate their fit, install and configure them safely, and then use them effectively within sessions. Use when the user needs new capabilities (browser control, advanced git, observability, etc.) or when existing MCPs are under-utilized. Triggers: "set up MCPs", "install the right tools", "add an MCP for...", "what MCPs do we need?"
1 other project uses a version of this.
Adopted by
Most recently taken up by
- robertfxbr/mcp-orchestratortheir own version, first seen Jul 9, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- robertfxbr/mcp-orchestrator★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-reviewerSkill
- git-disciplineSkill
- plan-mode-orchestratorSkill
- security-auditSkill
- subagent-arenaSkill
- tdd-intelligenceSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Run grok inspect (or equivalent) to see loaded MCPs.
- Distinctive: line 27
Prefer narrowly-scoped, well-documented servers over kitchen-sink ones.
- Distinctive: line 28
Check security model, maintenance, and fit for agent use.
- Distinctive: line 34
Create or update skills that know how to drive the new MCP.
- Distinctive: line 37
After installation, immediately demonstrate value with a small example.
- Distinctive: line 38
Update relevant skills or the current plan to use the new capability.
- Distinctive: line 39
Document in the project (README, AGENTS.md, or showcase notes).
- Distinctive: line 43
Never install untrusted or overly broad MCP servers without explicit review.
- Distinctive: line 45
Prefer read-heavy MCPs for investigation phases.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
MCP Orchestrator
MCP (Model Context Protocol) is one of grok-build-0.1's strongest advantages. This skill makes it first-class.
Responsibilities
- Inventory current state
- Run
grok inspect(or equivalent) to see loaded MCPs. - List project and user-level MCP configuration.
- Run
- Identify the gap
- What real capability is missing for the current task?
- Examples: visual QA, deep git history analysis, session introspection, architecture visualization, external service access.
- Evaluate and recommend specific MCP servers
- Prefer narrowly-scoped, well-documented servers over kitchen-sink ones.
- Check security model, maintenance, and fit for agent use.
- From this arsenal: recommend
agent-session-analyzer,repo-graph,test-intelligence,browser-qa,skill-validatorwhen appropriate.
- Guide installation and configuration
- Provide exact commands or config snippets.
- Handle trust prompts and
.grok/config.tomlor project MCP files. - Create or update skills that know how to drive the new MCP.
- Integrate into workflow
- After installation, immediately demonstrate value with a small example.
- Update relevant skills or the current plan to use the new capability.
- Document in the project (README, AGENTS.md, or showcase notes).
Safety Rules
- Never install untrusted or overly broad MCP servers without explicit review.
- MCP servers that can execute arbitrary code or access secrets must be treated like hooks — require trust and clear documentation.
- Prefer read-heavy MCPs for investigation phases.
Recommended Arsenal MCPs
agent-session-analyzer— for meta work on agent behaviorrepo-graph— architecture understanding at scaletest-intelligence— surgical testingbrowser-qa— when building or changing UIsskill-validator— when extending the skill system itself
Success Criteria
- The right MCPs are installed and discoverable via
grok inspect. - There is at least one concrete, working example of the agent using the new MCP in the session.
- Any new skill or documentation needed to make the MCP usable long-term has been created or updated.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

