AgentCore is the platform to build, connect, and optimize agents at scale, designed from the ground up for agents: open to any model, any framework, any enterprise architecture. Whether you’re shipping your first agent or your thousandth, you have one platform that scales with you. The registry extends that same flexibility to how you organize and govern what you’ve built. It indexes agents regardless of where they’re built or hosted – on AWS, other cloud providers, or on premises.

The registry stores metadata for every agent, tool, MCP server, agent skill, and custom resources as a structured record. It captures who published each record, what protocols it implements, what it exposes, and how to invoke it. The registry supports established standards like MCP and A2A natively, with the flexibility to define custom schemas for your organization. There are two ways to register a record. You can provide metadata manually through the console, AWS SDK, or API, specifying capability descriptions, ownership, compliance status, and usage documentation. Or you can point to an MCP or A2A endpoint, and the registry will automatically pull in the details. Your registry can reflect your full agent landscape from day one, not only the pieces that happen to run on AWS.

The registry is accessible through the AgentCore Console, APIs, and as an MCP server. Any MCP-compatible client can query it directly, including Kiro and Claude Code. For organizations with custom identity providers, OAuth-based access means that teams can build their own discovery UIs without requiring IAM credentials.

Without a central registry, developers search externally for third-party tools or duplicate work that a neighboring team already shipped. You lose visibility into what’s been built, who owns it, and whether it’s approved for use. The registry solves this with hybrid search that combines keyword and semantic matching: all queries use keyword matching, but longer, natural language queries also use semantic understanding to surface conceptually related results. This means a search for “payment processing” surfaces tools tagged as “billing” or “invoicing,” even if they’re named differently. Discovery becomes the path of least resistance. Teams can search by name, descriptions, and resource type to find what already exists before building something new. Developers search the registry first. If a vetted capability exists, they use it. If it doesn’t, they build it, register it, and make it available to everyone else. You can see what exists across your organization.