Skip to main content
Glama

SuperAgenticMCP

CI License Python 3.11+ MCP SDK CLI Board USDC

The switchboard for your agent swarm.

SuperAgenticMCP is a production-oriented, MCP-native router and multi-agent control plane. It sits between your agents and the MCP servers they need — planning the task, routing each tool call to the right server, streaming every step, and filing results into memory.

Patch every agent into every tool.

Support Agentic OS Kernels ($99) · Agentic OS Cycle ($0.75) · Public Goods Support · USDC

Layout standard: Server OS — see docs/LAYOUT.md.


Surfaces

Surface

Entry

Web control plane

superagenticmcp.html / web/ (offline hero)

MCP Server

superagenticmcp

CLI

superagenticmcp-cli status

SDK

from superagenticmcp.sdk import SuperAgenticClient

Board (target)

superagenticmcp up --board → http://localhost:7420

Skills

skills/*/SKILL.md

AGENTS.md

Coding-agent contract

Verify

bash scripts/verify.sh

CI

.github/workflows/ci.yml


Related MCP server: agentloop

Why SuperAgenticMCP?

Problem

Approach

Agents need many MCP servers

One process racks servers and routes by capability

Tool calls are opaque

Live patch board + JSONL log + run receipt

Multi-agent coordination is ad-hoc

Built-in planner / worker / critic loop

Memory evaporates between runs

Memory scope constellation of artifacts

Config drifts from reality

Rack toggles generate superagentic.json


Features

Capability

Status

MCP over stdio (+ streamable HTTP planned)

✅ scaffold

Capability-first routing + latency tie-break

🚧 / demo in hero

Planner → parallel workers → critic

🚧 / demo in hero

Hot-swap server rack

🚧 / demo in hero

Live patch board + phosphor log

✅ hero

Memory scope (3D constellation)

✅ hero

Call budgets + offline skip

🚧

Dynamic superagentic.json

🚧

Server OS layout + verify contract

✅

Self-learning model routing (bandit)

🚧

Agentic commerce (x402)

✅ routes to x402-cloudflare-starter GET /v1/cycle · /v1/search · /v1/draft

Commerce is not reimplemented here. Rack the x402 Worker; keep Stripe Payment Links for humans. Receipts are not Desk unlocks.


Quick start

git clone https://github.com/ANAMIZED/SuperAgenticMCP
cd SuperAgenticMCP
python -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"

superagenticmcp                 # MCP server (stdio)
superagenticmcp-cli status
make test
bash scripts/verify.sh

Zero-install hero:

https://htmlpreview.github.io/?https://github.com/ANAMIZED/SuperAgenticMCP/blob/main/superagenticmcp.html

MCP client config

{
  "mcpServers": {
    "superagenticmcp": {
      "command": "superagenticmcp",
      "args": []
    }
  }
}

Docker (scaffold)

docker compose up --build

How routing works

  1. Protocol — Model Context Protocol; one session per racked server.

  2. Agent loop — Planner decomposes; workers run in parallel where allowed; critic checks before ship.

  3. Routing — Capability match first, latency as tie-break, fallback when a server drops.

  4. Guardrails — Per-server allow-lists and per-run call budgets.

  5. Telemetry — JSONL lines + board replay.

  6. Footprint — Single process for the core path; no DB required.


Repository layout

src/superagenticmcp/   # MCP, CLI, SDK
skills/                # Packaged skills (Server OS style)
web/                   # Control-plane path
scripts/verify.sh      # Verify contract
tests/                 # Smoke + contract tests
superagenticmcp.html   # Hero demo
docs/LAYOUT.md         # Permanent layout standard = Server OS
AGENTS.md              # Agent contract

Support

Fiat (Stripe)

Offer

Link

Support Agentic OS Kernels — $99

buy.stripe.com/…

Agentic OS Cycle — $0.75

buy.stripe.com/…

Public Goods Support

donate.stripe.com/…

GitHub Sponsors: ANAMIZED

USDC (crypto)

Non-custodial addresses controlled by ANAMIZED. Pure x402 micropayments preferred for agents — see x402-cloudflare-starter.

Network

Address

Explorer

Base

0xD3d0E9eDAe3Ac7bb199a8EAA761BdA423b878438

basescan

Ethereum

0xD3d0E9eDAe3Ac7bb199a8EAA761BdA423b878438

etherscan

Solana

ETQwWf19axArsY493UfC6bxe2BmEzmzvCb58PPnC38A

solscan

Send only USDC on the matching network. Wrong asset or chain can mean permanent loss.



License

Apache-2.0

Built for the Model Context Protocol · Unit 001 · SA-MCP MK.4 · Server OS layout

Available Tools

5 tools
list_rackList racked MCP serversA

List MCP servers currently mounted on the SuperAgentic rack (name, command or URL, notes). Use after rack_add to confirm membership. Empty list means no servers have been registered in this process. Read-only; use rack_add / rack_remove to mutate. Does not probe remote health.

Inputs: no named parameters. Returns: object

rack_addAdd a server to the rackA

Register an MCP server on the in-memory rack so later route_task calls can target it by name. Overwrites an existing entry with the same name (idempotent upsert). Does not start the child process and does not validate the command. Use list_rack to inspect and rack_remove to delete. Local write only.

Inputs: name (required), command (required), notes. Returns: object

rack_removeRemove a server from the rackA

Remove one MCP server from the in-memory rack by name. Destructive. Missing names return an error object rather than raising. Does not stop a running child — only drops the catalog entry. Use list_rack first to confirm the name.

Inputs: name (required). Returns: object

route_taskPlan a task against the rackA

Produce a routing plan for a natural-language task against the current rack. In this release the planner is a deterministic stub: it lists candidate servers and does not execute downstream tools. Use after rack_add. Not a substitute for status. Read-only with respect to the rack; no network calls yet.

Inputs: task (required), preferred_server. Returns: object

statusGet router statusA

Return SuperAgenticMCP router health: version, process status, and how many MCP servers are currently racked. Use this as a connectivity probe before list_rack or route_task. Read-only local state. Does not call downstream MCP servers (not open-world). Pair with list_rack for the actual catalog.

Inputs: no named parameters. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct role: status reports router health, list_rack shows catalog contents, rack_add and rack_remove mutate the rack, and route_task plans routing. There is no meaningful overlap or ambiguity between tools.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case pattern such as list_rack, rack_add, and rack_remove. The lone status tool breaks the verb_noun pattern, but it is still a simple, readable name and does not cause confusion.

    Tool Count5/5

    Five tools is well-scoped for a router/rack management server. Each tool covers a necessary operation without redundancy or unnecessary bloat.

    Completeness4/5

    The surface covers the core lifecycle: health check, catalog listing, add/upsert, remove, and routing plan generation. Minor gaps exist such as no single-server detail endpoint and route_task being a deterministic stub, but the main workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      A production-ready MCP gateway and control plane that provides credential vault, policy engine, audit logging, and managed runtime for routing tool calls between AI agents and downstream MCP servers.
      59
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI agents to run a deterministic orchestration loop with decomposition, subagent execution, and review feedback across multiple LLM backends.
      61
      MIT