Contact Us 1-800-596-4880
  1. Homepage
  2. Enhanced MuleSoft Experience
  3. Adding Services to Your Portfolio

  4. Register Services Manually

Register Services Manually

Register a service to add it to your portfolio when you already have the metadata, specification, endpoint, or card the new experience needs—without running a provider scan. You start from Home or from the catalog for that service type in Portfolio; completed registrations appear in the matching catalog.

For how manual registration fits with connecting providers, see Adding Services to Your Portfolio.

Before You Begin

Before getting started, make sure you have:

  • An Anypoint Platform account.

  • Any of these permissions:

    • Exchange: Exchange Contributor

    • Exchange: Exchange Administrator

    • Exchange: Exchange Creator

    For more information, see Enhanced Experience Permissions.

Get Started

  • Home

    Open Add Services, select the service type, then select manual registration if the UI offers it.

  • Portfolio

    Open the Agents, MCP Servers, LLM Proxies, APIs, or Gateways catalog, use the add control for that type (for example Add API), and select Register Manually.

Navigation labels can vary by catalog, enabled features, and release.

Agents

You register an agent by supplying one of these protocols:

  • A2A connection

    Point to an A2A endpoint to fetch an agent card.

  • Non-A2A connection

    Provide metadata and connection details when you’re not using a card workflow.

  • Agent Card File Provide an agent card file you already have.

The connection gets validated, makes it possible to review metadata, and saves the agent into the Agents catalog.

MCP Servers

You define how the system reaches the MCP server and validates runtime access:

  • By MCP URL — Connect over a URL and test the live server so tools and metadata can be discovered.

  • Upload Schema — Upload a schema and supply the details needed to register and test the server.

Successful registration stores the MCP server in the MCP Servers catalog.

LLM proxies

LLM proxy registration is a two-part configuration: you associate the proxy with a gateway (and related deployment context), then define routing (and any provider connections your flow requires). After the wizard completes, the LLM proxy appears in the LLM Proxies catalog.

APIs

To create an API, add it to the APIs catalog either by registering it manually or by connecting to a provider.

  • Register manually – Upload a specification file to define a new API.

  • Connect to provider – Discover and import APIs from external platforms. See Connect to Providers to Add Services.

Register an API Manually

When you register an API manually, you provide a specification file that defines the API structure, including endpoints, operations, and data types.

  1. In the navigation pane, select APIs.

  2. Click Add API.

  3. Select Register manually.

  4. Enter a name for the API.

  5. Select the API type.

  6. Upload the specification file.

  7. Click Create.

The experience supports multiple API types and specification formats:

  • REST APIs (OAS, RAML)

  • gRPC APIs (Proto files)

  • Async APIs (AsyncAPI specification)

Gateways

Register gateways manually when you want to add an existing gateway runtime to Portfolio without using provider discovery. This flow establishes gateway identity, connection context, and metadata so teams can govern and monitor gateway traffic in the enhanced experience.

Manual gateway registration includes:

  • Defining gateway identity and descriptive metadata used in catalog and governance views.

  • Providing environment and runtime connection details so the gateway maps to your organization topology.

  • Validating registration inputs before saving to make the gateway ready for operational workflows.

After registration, the gateway appears in the Gateways catalog in Portfolio, where teams can review details and apply supported governance workflows.

See Also