Contact Us 1-800-596-4880
  1. Homepage
  2. API Manager (2.x)
  3. Manage API Instances
  4. Add API Instances

  5. Add an Omni Gateway MCP Bridge instance

Adding an MCP Bridge Instance

Omni Gateway MCP Bridge enables you to create MCP servers from your APIs. With the MCP Bridge, you can expose your APIs as MCP tools so agents can discover and call them.

Define your MCP bridge by selecting APIs and mapping them to MCP tools. When an agent requests the list of available tools (tools/list), the gateway responds with an MCP descriptor that defines each tool’s name, description, and input schema. When an agent calls a tool (tools/call), the MCP Bridge maps the tool name and arguments to an HTTP request based on your configuration.

This diagram shows the relationship of the upstream and downstream configurations to your upstream service and agent client:

The MCP Bridge instance is deployed on a gateway between the upstream apis and downstream configuration

MCP Bridge doesn’t support API instances with multiple upstream services.
After deploying an MCP Bridge, you can update its configuration, including the APIs and their versions. See Update an MCP Bridge.

Add a New Agent or Tool Instance

To add and a new MCP Bridge for Omni Gateway:

  1. Ensure that all APIs you want to add to your MCP Serve exist in Exchange.

  2. To begin creating your MCP Server instance, you can start from these locations:

    • From API Instances:

      1. Click on an existing API instance you want to add to an MCP Server.

      2. Click Actions > Add to new MCP Server instance.

    • From Agent and Tool Instances:

      1. Click Add > MCP Bridge.

  3. From Select a gateway, choose an Omni Gateway for deploying the MCP server instance.

  4. Click Next.

  5. Select the APIs you want to add to your MCP Server.

  6. Define the MCP server’s asset name.

  7. Click Next.

  8. Configure the downstream configuration settings:

    Managed Omni Gateway
    Field Name Description Required Notes

    Base path

    Specifies the URL prefix for all instance paths, relative to the host root. It must start with a leading slash /.

    Yes

    Client provider

    Specifies a client provider for the instance.

    No

    Anypoint Platform acts as the client provider by default. To configure an external client provider, see Client Providers.

    Instance label

    Specifies a label for the instance.

    No

    If you have multiple managed instances of the same asset, add a label to differentiate each instance from the others.

    Advanced Options

    Consumer endpoint

    Specifies a proxy application’s address for consumers to use for sending requests.

    No
    Self-Managed Omni Gateway (Connected Mode)
    Field Name Description Required Notes

    Protocol

    Specifies whether to use HTTP or HTTPS.

    Yes

    If you select HTTPS, specify a TLS context for inbound traffic.

    Inbound TLS

    TLS Context used for the inbound HTTPS traffic.

    No

    Configure a TLS Context for Omni Gateway before adding a TLS Context to your server.

    Port

    Specifies the number to use if the displayed port is incorrect.

    No

    Instances can share the same port across the same target if the Base path is different for both instances.

    Base path

    Specifies the URL prefix for all server paths, relative to the host root. It must start with a leading slash /.

    Yes

    Instance label

    Specifies a label for the instance.

    No

    If you have multiple managed instances of the same asset, add a label to differentiate each instance from the others.

    Advanced Options

    Consumer endpoint

    Specifies a proxy application’s address for consumers to use for sending requests.

    No

  9. Click Next.

  10. Configure the upstream services for your API instances:

    Field Name

    Description

    Required

    Notes

    Route Label

    Label to better identify multiple API instances.

    Yes

    By default, the label is the API name.

    Upstream URL

    URL to access for the upstream service. This must end with a /.

    Yes

    For example, use the URL of your asset in Exchange.

    Outbound TLS

    TLS Context used for the outbound traffic to the upstream service

    No

    Configure a TLS Context for Omni Gateway before adding a TLS Context to your server.

    To switch among API instances, select the name of the API.

  11. Click Next.

  12. Define your API Tools:

    1. Select an API to map to a tool.

    2. Select an HTTP request Method and Resource.

    3. Define an AI tool name.

    4. Write a tool Description.

    5. Review the suggested Input schema and update it if needed.

  13. Optionally, click HTTP mapping edit the autopopulated HTTP mapping:

    1. Map incoming tool params to:

      • Query Parameters

      • URI Parameters

      • HTTP Headers

      • Payload Body

    2. Define DataWeave expressions to extract the tool parameters from the incoming request.

  14. Click Next.

  15. Review your selections and edit them if necessary.

  16. If you are ready to deploy, click Save & Deploy. Otherwise, select Save to deploy the instance later.

Update an MCP Bridge

You can update an existing MCP Bridge instance to change its APIs or configuration settings.

To update an MCP Bridge instance:

  1. In Agent and Tool Instances, click the MCP Bridge instance you want to update.

  2. Click Actions > Edit.

  3. In the APIs section, click the edit icon to update the APIs associated with this MCP Bridge.

  4. To change the API version, select a different version from the Select version dropdown.

  5. Click through the remaining steps to review and update any other settings as needed.

  6. Click Save & Deploy to apply the changes.

See Also