Skip to content

Multi-Agent System

Multi-agent architecture with A2A protocol peers, MCP tool servers, and an orchestrating agent. Agents discover each other, delegate tasks, and share tools, and reach a model through the ModelGateway of the Platform tenant chart the stack deploys with.

Namemulti-agent
Version0.1.0
Tagsai, agents, a2a, mcp, multi-agent
Sourcecomposites/multi-agent.yaml

Render it

# CLI
npx @nanohype/sdk render-composite multi-agent --out ./my-app

# SDK
import { LocalSource, renderComposite } from "@nanohype/sdk";
const result = await renderComposite(source, "multi-agent", variables);

# MCP — from an agent
get_composite({ name: "multi-agent" })

What it draws together

TemplateRendered atNotes
monoreporootthe root project
a2a-agentpackages/orchestrator
agentic-looppackages/agent
mcp-server-tspackages/tools
guardrailspackages/guardrailsonly when IncludeGuardrails
eval-harnesspackages/evals
ts-serviceapps/api
module-auth-tspackages/auth
k8s-app-tenantinfra

Variables

Required

ProjectName string
Project name Must be lowercase kebab-case.

Optional

LlmProvider string — defaults to gateway
LLM provider the packages deployed on the substrate call: gateway, the Platform ModelGateway, which holds the Bedrock role there, so none of them holds a model credential. The eval harness runs on a CI runner and keeps its own bedrock default
IncludeGuardrails bool — defaults to true
Include safety guardrails
Tenant string — defaults to ${ProjectName}
Owning team: the tenants-<team> namespace the Platform, BudgetPolicy and ModelGateway CRs are applied in, the Platform's spec.tenant, and the team label on the tenant chart's resources and telemetry
Image string — defaults to ${ProjectName}
Container image repository the tenant chart deploys, without a tag; each values-<env>.yaml pins one
AppMetric string — defaults to http
Prefix of the RED series the tenant chart's Grafana dashboard reads: <prefix>_requests_total, <prefix>_errors_total and <prefix>_request_duration_seconds. The default, http, is the prefix apps/api (a ts-service) emits them under