Back to Browse

SuperAgentic MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

MCP-native router and multi-agent control plane: plan, route tool calls, stream execution.

About

MCP-native router and multi-agent control plane: plan, route tool calls, stream execution.

Security Report

5.2
Moderate5.2Moderate Risk

SuperAgenticMCP is a well-structured alpha-stage MCP server with clean code organization, proper dependency management, and no critical security vulnerabilities. The codebase is early-stage with mostly stub implementations, minimizing attack surface. No hardcoded credentials, dangerous patterns, or authentication bypass issues detected. Permissions are appropriately scoped for a developer tool. Supply chain analysis found 7 known vulnerabilities in dependencies (1 critical, 3 high severity).

7 files analyzed · 11 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-anamized-superagenticmcp": {
      "args": [
        "superagenticmcp"
      ],
      "command": "uvx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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

SurfaceEntry
Web control planesuperagenticmcp.html / web/ (offline hero)
MCP Serversuperagenticmcp
CLIsuperagenticmcp-cli status
SDKfrom superagenticmcp.sdk import SuperAgenticClient
Board (target)superagenticmcp up --boardhttp://localhost:7420
Skillsskills/*/SKILL.md
AGENTS.mdCoding-agent contract
Verifybash scripts/verify.sh
CI.github/workflows/ci.yml

Why SuperAgenticMCP?

ProblemApproach
Agents need many MCP serversOne process racks servers and routes by capability
Tool calls are opaqueLive patch board + JSONL log + run receipt
Multi-agent coordination is ad-hocBuilt-in planner / worker / critic loop
Memory evaporates between runsMemory scope constellation of artifacts
Config drifts from realityRack toggles generate superagentic.json

Features

CapabilityStatus
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)🚧

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)

OfferLink
Support Agentic OS Kernels — $99buy.stripe.com/…
Agentic OS Cycle — $0.75buy.stripe.com/…
Public Goods Supportdonate.stripe.com/…

GitHub Sponsors: ANAMIZED

USDC (crypto)

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

NetworkAddressExplorer
Base0xD3d0E9eDAe3Ac7bb199a8EAA761BdA423b878438basescan
Ethereum0xD3d0E9eDAe3Ac7bb199a8EAA761BdA423b878438etherscan
SolanaETQwWf19axArsY493UfC6bxe2BmEzmzvCb58PPnC38Asolscan

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


Related projects


License

Apache-2.0

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

Reviews

No reviews yet

Be the first to review this server!