◈ AWS AGENTCORE BLUEPRINTS
PART IV · GOVERNANCE AND TRANSACTIONS · CHAPTER 26 / 36
TOCCONSULTING.FR
AMAZON BEDROCK / SERVICE DETAIL S11 REGISTRY

AGENTCORE REGISTRYPRACTICAL

CHAPTER 26 / 36
TOPIC catalog an MCP server, approve it, find it
REV 2026.07
IN PLAIN WORDS

You will create a catalog, add an entry for an MCP server, approve it, then search and find it. Terms: registry = the catalog; record = one entry (an agent, tool, MCP server, or skill); approval = the gate so only vetted entries appear; bedrock-agentcore-control = the admin API; bedrock-agentcore = the search API.

[ 1 ] CREATE A CATALOG, THEN ADD AN ENTRY
$ aws bedrock-agentcore-control create-registry \ --name "MyFirstRegistry" --description "My first Agent Registry" # note the registryId from the output, then add a record for an MCP server: $ aws bedrock-agentcore-control create-registry-record \ --registry-id <registryId> --name "WeatherServer" --descriptor-type MCP \ --descriptors '{"mcp": {"server": {"inlineContent": "{\"name\": \"weather/mcp-server\", \"description\": \"Weather data service\", \"version\": \"1.0.0\"}"}}}' \ --record-version "1.0" # created in CREATING, then DRAFT
[ 2 ] SUBMIT AND APPROVE (so it becomes discoverable)
$ aws bedrock-agentcore-control submit-registry-record-for-approval \ --registry-id <registryId> --record-id <recordId> # -> PENDING_APPROVAL $ aws bedrock-agentcore-control update-registry-record-status \ --registry-id <registryId> --record-id <recordId> \ --status APPROVED --status-reason "Reviewed and approved" # -> APPROVED
[ 3 ] SEARCH IT (people, or agents, find the entry)
# AWS CLI (search is on the data-plane client) $ aws bedrock-agentcore search-registry-records \ --search-query "weather" \ --registry-ids "<registry-id>"
# or boto3
import boto3
client = boto3.client('bedrock-agentcore')   # the search API

resp = client.search_registry_records(
    registryIds=['arn:aws:bedrock-agentcore:us-east-1:<account>:registry/<registryId>'],
    searchQuery='weather forecast tool',   # meaning + keywords
    maxResults=10)
for r in resp['registryRecords']:
    print(r['name'], r['descriptorType'], r['status'])
Only Approved records are returned (Draft, Pending, Rejected, Deprecated are hidden). Manage uses bedrock-agentcore-control; search uses bedrock-agentcore. A JWT-secured registry cannot use the CLI or SDK for search (those sign with IAM); call the search REST API over HTTPS with a JWT bearer token, or use its MCP endpoint with an MCP client. Note: the service moves to its own agent-registry namespace on 2026-08-06, which changes these commands and endpoints.
SRC: AWS AgentCore Developer Guide (Agent Registry get started, searching the registry)
DRAWN 2026.06, REV 2026.07.26
◄ PREVIOUS · CH 25
AgentCore Registry, Plain Language
NEXT · CH 27 ►
AgentCore Payments, Plain Language
AWS AGENTCORE BLUEPRINTS · CONTENTS
Back to tocconsulting.fr Cover & Table of Contents
PART I · FOUNDATIONS
01AgentCore Overview, Plain LanguageCONCEPT02AgentCore, Key Terms in Plain LanguageCONCEPT03AgentCore, Common Mistakes ExplainedCONCEPT04Inside an AgentCore Agent, BlueprintCONCEPT05Harness, Practical 1, Strands PathPRACTICAL06Harness, Practical 2, Managed HarnessPRACTICAL
PART II · CORE SERVICES
07AgentCore Runtime, Plain LanguageCONCEPT08AgentCore Runtime, PracticalPRACTICAL09AgentCore Memory, Plain LanguageCONCEPT10AgentCore Memory, PracticalPRACTICAL11AgentCore Gateway, Plain LanguageCONCEPT12AgentCore Gateway, PracticalPRACTICAL13AgentCore Identity, Plain LanguageCONCEPT14AgentCore Identity, PracticalPRACTICAL
PART III · TOOLS AND OPERATIONS
15AgentCore Code Interpreter, Plain LanguageCONCEPT16AgentCore Code Interpreter, PracticalPRACTICAL17AgentCore Browser, Plain LanguageCONCEPT18AgentCore Browser, PracticalPRACTICAL19AgentCore Observability, Plain LanguageCONCEPT20AgentCore Observability, PracticalPRACTICAL21AgentCore Evaluations, Plain LanguageCONCEPT22AgentCore Evaluations, PracticalPRACTICAL
PART IV · GOVERNANCE AND TRANSACTIONS
23AgentCore Policy, Plain LanguageCONCEPT24AgentCore Policy, PracticalPRACTICAL25AgentCore Registry, Plain LanguageCONCEPT26AgentCore Registry, PracticalPRACTICAL27AgentCore Payments, Plain LanguageCONCEPT28AgentCore Payments, PracticalPRACTICAL
PART V · MULTI-AGENT AND ARCHITECTURE
29A2A and Multi-Agent, Plain LanguageCONCEPT30A2A and Multi-Agent, PracticalPRACTICAL31Architecture Patterns, Plain LanguageCONCEPT32Multi-Tenant Agents, Plain LanguageCONCEPT33Agent Security and Threat Model, Plain LanguageCONCEPT34Governance at Org Scale, Plain LanguageCONCEPT35Governance at Org Scale, PracticalPRACTICAL36Multi-Region and Distribution, Plain LanguageCONCEPT