AWS Agent Registry: runtime semantic discovery of MCP tools and A2A agents

AWS ML Blog · rss · 2026-10-21

The problem: hardcoded tools don't scale

Hardcoded tools work in demos, but enterprise systems expose hundreds of internal APIs (pricing, support, orders, inventory), so models burn tokens disambiguating tool names; every new capability forces orchestrator code changes, redeploys, and coordinated team releases.

Solution: Discover → Instantiate → Execute

AWS Agent Registry is a managed catalog for MCP servers, agents, and agent skills. The core loop:

Reference architecture

The sample deploys an order-management MCP server (AgentCore Gateway + Lambda), two A2A agents on AgentCore runtime, an orchestrator, and the Registry, using Bedrock (Claude Sonnet), Cognito, and Secrets Manager. Three demos: MCP-only (order status), MCP + A2A chaining (pricing/discounts), and pure semantic matching ("return and refund" matched an agent whose name contains neither word). The repo ships deployment, orchestrator, helper, and cleanup scripts.

Tip: write descriptions in user-facing language that distinguishes each capability from neighbors, and evaluate search quality with representative queries — catalog growth alone doesn't improve ranking.

Original post →

More from coding & agent

coding & agent channel →