AWS shows agents finding MCP servers and A2A agents at runtime via Agent Registry
Overview
AWS Machine Learning Blog publishes a walkthrough of an orchestrator agent that uses AWS Agent Registry to find MCP servers and A2A agents at runtime instead of hardcoding them.
The sample deploys an order-management MCP server through Amazon Bedrock AgentCore Gateway, two A2A agents, and an orchestrator, and runs three demo scenarios. According to the post, registry search returns connection metadata but not invocation credentials, so the application must obtain credentials through a separate configuration path. Only records that complete the configured approval workflow are available through the discoverable data plane. The sample configures an Anthropic Claude Sonnet model through a cross-Region model ID.
Written by AI from the articles below · updated Oct 20, 12:53 PM ET
Check the sources:
Article timeline
The articles in this story. Times are ET.
- AWS Machine Learning BlogOfficialPickAWS shows how agents can discover tools at runtime with Agent Registry
AIAWS Machine Learning Blog explains how an orchestrator agent can use AWS Agent Registry to find MCP servers and A2A agents at runtime instead of hardcoding them. The sample deploys an order-management MCP server through Amazon Bedrock AgentCore Gateway, two A2A agents, and an orchestrator, and runs three demo scenarios. Registry search returns connection metadata but not invocation credentials, which the application must obtain through a separate configuration path.
Heat Trend
Not enough continuous observations to show a trend yet.