superagenticmcp
Skill1 starsChanged 3 months agoApache-2.0View on GitHub
SuperAgenticMCP — the switchboard for your agent swarm. MCP-native router and multi-agent control plane that plans tasks, routes tool calls to racked MCP servers by capability and latency, streams execution, and files results into a memory-scope graph. Use when the user needs multi-agent orchestration over MCP, a local agent switchboard, capability-based tool routing, or a live patch-board view of agent↔server traffic.
- Installs packages
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- memory-scopeSkill
- multi-agent-workflowSkill
- routing-capabilitySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Run a local switchboard that racks/unracks servers and regenerates config
≈ “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
SuperAgenticMCP
Patch every agent into every tool.
When to use this skill
- Orchestrate multiple agents (planner / workers / critic) against a set of MCP servers
- Route tool calls by capability with latency as a tie-breaker
- Run a local switchboard that racks/unracks servers and regenerates config
- Observe live agent→server traffic (patch board + JSONL log + run receipt)
- Persist run artifacts into a linked memory-scope constellation
- Generate or consume a
superagentic.jsonrouter config
How to run the MCP server
pip install superagenticmcp
# or from source:
pip install -e .
superagenticmcpMCP client config:
{
"mcpServers": {
"superagenticmcp": {
"command": "superagenticmcp",
"args": []
}
}
}Board mode (when implemented):
superagenticmcp up --board
# board on http://localhost:7420Core ideas
- Rack — toggle MCP servers online; they appear on the board and become routable
- Plan — planner decomposes the task order into steps across servers
- Route — capability match first, latency second, fallback when a server is offline
- Observe — every call is a JSONL line; the same stream feeds the log and the board
- Remember — completed runs file artifacts into a linked memory graph
Principles
- Observable by default — routing and failures must be visible (log + board + receipt)
- Config as truth — rack state and
superagentic.jsonstay in sync - Fail closed on budgets — a run that hits its call budget stops and says so
- Demo is not runtime — the HTML hero is for design feel; production path is the Python MCP server
- Additive surface — keep the public MCP tool surface stable and clear
Interactive shell
No install required:
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.

