AWS Agent Registry is generally available and answers as an MCP server

Agent Registry left preview on August 31, 2026 and is now open to every AWS customer. The service keeps a private catalog of the agents, tools, skills, MCP servers, and custom resources an organization already runs, and puts search and an approval step in front of it. This is not another agent framework. It answers a question that gets expensive as a company grows: does this thing already exist somewhere inside it?

What general availability adds

The preview already had manual and URL-based record creation, approval workflows, semantic and keyword search, and audit trails in AWS CloudTrail. General availability adds the parts an organization needs before it can treat a registry as infrastructure rather than a side project.

The most consequential of them is automatic detection. A registry picks up agents running on AgentCore runtime and on AgentCore gateways across an entire organization, so records stay current without anyone writing them by hand. A catalog nobody updates is a catalog nobody trusts, and hand-written entries go stale first.

• Registries and records can be provisioned as code with AWS CloudFormation, Terraform, and the AWS CDK.
• Tags on registries and records support organization, cost allocation, and access control.
• AWS Resource Access Manager shares registries across accounts and backs organization-wide registries.
• Agents on AgentCore runtime and AgentCore gateways are detected automatically across the organization.
• Amazon Quick can discover custom connectors from the registry on its Connectors page.

The registry answers as an MCP server

Records can be reached from the AWS Agent Registry console, the AWS CLI, and the AWS SDK, and also from Amazon Bedrock AgentCore, Amazon Quick, and the Kiro IDE. The console pairs semantic search with keyword search and a browse view for walking through registries and records.

The detail that matters most to anyone building agents is the one easiest to miss. The registry is exposed as an MCP server, so an assistant in an editor can query it directly. Discovery becomes something an agent does in the middle of a task, rather than something a person does in a browser tab beforehand.

Where it runs, and what the note leaves out

Agent Registry is available in five AWS Regions: US East (N. Virginia), US West (Oregon), Europe (Ireland), Asia Pacific (Tokyo), and Asia Pacific (Sydney). An organization outside those Regions has to weigh whether a central catalog is worth the cross-Region hop.

The announcement says nothing about price. There is no pricing line, no free tier, and no statement that the service comes with AgentCore, so the cost of running a registry is not something this page answers. Anyone budgeting for it has to open the pricing page rather than the launch note.