MCP Subagent Server

Created By
dvcrna year ago
MCP for letting agents delegate tasks to sub-agents (Claude Code, Aider, Q)
Overview

what is MCP Subagent Server?

MCP Subagent Server is a Model Context Protocol (MCP) server designed to allow letting agents to delegate tasks to sub-agents like Claude Code, Aider, and Q.

how to use MCP Subagent Server?

To use the MCP Subagent Server, configure it in your MCP configuration file and run the server using the provided commands. You can then execute tasks through sub-agents and monitor their status and logs.

key features of MCP Subagent Server?

  • Configure and run multiple sub-agents through MCP tools.
  • Bi-directional communication between parent and sub-agents.
  • Real-time streaming logs for monitoring.
  • Tools for executing tasks, checking status, and retrieving logs.

use cases of MCP Subagent Server?

  1. Delegating tasks to different sub-agents for efficient execution.
  2. Monitoring the status and logs of sub-agent tasks in real-time.
  3. Facilitating communication between parent agents and sub-agents for better task management.

FAQ from MCP Subagent Server?

  • Can I add new sub-agents?

Yes! You can add new sub-agents by modifying the SUBAGENTS object in the source code.

  • How do I check the status of a sub-agent?

Use the check_subagent_status tool with the run ID of the sub-agent.

  • Is there support for real-time logging?

Yes! The server provides real-time streaming logs for monitoring sub-agent execution.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dvcrn
Star
0
Language
TypeScript
License
AGPL-3.0 license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago