> For the complete documentation index, see llms.txt.
Skip to main content

Check out Port for yourself ➜ 

Build an AI Agent Registry

Implement with AI

Send this guide to your coding agent.

Prerequisite: Install Port MCP

This guide demonstrates how to build a centralized AI Agent Registry using Port, enabling your organization to discover, govern, and manage AI agents from multiple agent providers in a single unified view.

AI Agent Registry catalog with metadata columns

Common use cases​

  1. Agent Discovery - Enable developers to find and reuse existing AI agents across the organization instead of building duplicates.

  2. Multi-platform visibility - View Claude managed agents, AWS Bedrock agents, and Azure AI Foundry agents in one place.

  3. Governance & Compliance - Track agent status, models used, and deployment regions for compliance requirements.

Prerequisites​

  1. A Port account with permissions to create blueprints and integrations.

  2. Depending on which agent providers you want to integrate:

Set up data model​

We'll create a blueprint to represent AI agents in your organization's catalog, tracking their platform, status, model, and region.

Create AI Agent blueprint​

  1. Go to the Data model page in Port.

  2. Click on + Blueprint.

  3. Click on the {...} Edit JSON button.

  4. Copy and paste the following JSON configuration:

    AI Agent blueprint (click to expand)
    {
    "identifier": "aiAgent",
    "description": "AI agents deployed across cloud platforms",
    "title": "External AI Agent",
    "icon": "GPU",
    "schema": {
    "properties": {
    "description": {
    "title": "Description",
    "type": "string",
    "description": "What this agent does"
    },
    "platform": {
    "title": "Platform",
    "type": "string",
    "enum": ["aws-bedrock", "aws-agentcore", "azure-foundry"],
    "enumColors": {
    "aws-bedrock": "orange",
    "aws-agentcore": "orange",
    "azure-foundry": "blue"
    },
    "description": "Cloud platform where the agent is deployed"
    },
    "status": {
    "title": "Status",
    "type": "string",
    "enum": ["CREATING", "PREPARING", "PREPARED", "NOT_PREPARED", "ACTIVE", "DELETING", "FAILED", "VERSIONING", "UPDATING"],
    "enumColors": {
    "CREATING": "yellow",
    "PREPARING": "yellow",
    "PREPARED": "green",
    "NOT_PREPARED": "red",
    "ACTIVE": "green",
    "DELETING": "pink",
    "FAILED": "red",
    "VERSIONING": "yellow",
    "UPDATING": "yellow"
    },
    "description": "Current deployment status"
    },
    "model": {
    "title": "Model",
    "type": "string",
    "description": "Foundation model used by the agent"
    },
    "region": {
    "title": "Region",
    "type": "string",
    "description": "Cloud region where agent is deployed"
    },
    "createdAt": {
    "title": "Created At",
    "type": "string",
    "format": "date-time",
    "description": "When the agent was created"
    },
    "updatedAt": {
    "title": "Updated At",
    "type": "string",
    "format": "date-time",
    "description": "When the agent was last updated"
    }
    },
    "required": ["platform"]
    },
    "mirrorProperties": {},
    "calculationProperties": {},
    "relations": {}
    }
  5. Click Create to save the blueprint.

Connect your agent providers​

Now that we have our data model, let's configure integrations to automatically discover AI agents from your agent providers.

Ingest Claude managed agents

Port's Claude managed agents integration is a built-in connector that discovers Claude agents, environments, sessions, vaults, memory stores, and skills in your Context Lake.

  1. Install the Claude managed agents integration. Hosted by Port is the recommended installation method.
  2. The integration ships with default blueprints and mappings, so you do not need the custom aiAgent blueprint from the previous section.
  3. Click Resync to start discovering your Claude agents.

For workflow examples that trigger Claude agents from Port, see Assign PR reviewers with a Claude managed agent.

Let's test it​

After configuring your integrations, trigger a resync to populate your catalog:

  1. Go to the Connectors page.

  2. Find your agent provider integration and click Resync.

  3. Navigate to the AI Agent catalog page.

  4. You should see your agents appearing from all connected agent providers.

Developers can now see all AI agents in one place, with key metadata like platform, status, model, and region visible at a glance.

Summary​

You've built a centralized AI Agent Registry that:

  • Discovers agents automatically from Claude, AWS Bedrock, AgentCore, and Azure AI Foundry.
  • Provides a unified view of all agents across agent providers.
  • Tracks key metadata including status, model, and region.

Next steps​