Back to timeline

Wed, October 2100:22AgentAPI & pricingMCP & SkillsAgentsAPI & pricing guide

AWS launches Agent Registry for runtime discovery of MCP and A2A capabilities

Decision Brief

What changedAWS released Agent Registry, a managed service that lets orchestration agents discover MCP servers and A2A agents at runtime via semantic search, instead of hardcoding tools into code.
Why it mattersThe orchestrator re-searches and builds ephemeral sub-agents per request, so new capabilities only need registration and approval rather than code changes and redeployment, solving the multi-team independent release problem.
Who should careAgent builders
Affected stackMCPClaude
Builder actionUpdate MCP to the latest version
Source confidenceHigh · Official release / blog / repo

AWS Agent Registry is a managed catalog service for cataloging and discovering MCP servers, agents, and agent skills. Publishers register protocol descriptors and searchable descriptions; records go through a DRAFT to PENDING_APPROVAL to APPROVED flow, and only approved records are returned by the data plane. The search_discoverable_registry_records API supports hybrid keyword and semantic retrieval, returning record ID, name, description, type, version, and protocol descriptor, but not invocation credentials, which apps must fetch from a separate trusted config path. In the sample architecture, the orchestrator runs on Amazon Bedrock AgentCore runtime, the order management tool is exposed as an MCP server via AgentCore Gateway, and pricing and support agents run over A2A. Each request searches the Registry first, builds MCP clients or A2A tools from the returned descriptors, and the assembled internal agent holds only that round's discovered tools, destroyed once the request ends. For enterprise platform teams maintaining many internal APIs, new capabilities only need registration and approval, with no orchestrator code changes or coordinated redeploys; for developers building agents with the Claude API, credential-free discovery results mean they still manage OAuth tokens and IAM signing themselves, so the search layer and auth layer must be designed separately.

Summary basis: full article readCompiled from the source scope noted above; the original remains authoritative.

Sources

Related intel

留言

登入后即可留言,和其他 builder 交换实测心得。

还没有留言,抢头香。