---
schema_version: "1"
id: 8f944f62eac6f17c5835af853263ef843350361cbfad681dd419f3dd6aad7cb3
title: Adding an MCP Bridge Instance
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-manager/latest/create-instance-task-mcp-bridge.md
canonical_url: https://docs.mulesoft.com/api-manager/latest/create-instance-task-mcp-bridge
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 194ff25f031df38bd1066be84ce678b6553653171e885b16bde4a2d314228bc7
description: MuleSoft Documentation Site
release: 2.x
latest: true
---
---
product: API Manager
version: 2.x
is-latest-version: true
---

# Adding an MCP Bridge Instance

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

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](/mulesoft/current/en-us/api-manager/latest/_images/mcp-bridge-instance.png)

> [!NOTE] MCP Bridge doesn’t support API instances with multiple upstream services.

> [!NOTE] After deploying an MCP Bridge, you can update its configuration, including the APIs and
> their versions. See [Update an MCP Bridge](#update-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

    <table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Field Name</th><th>Description</th><th>Required</th><th>Notes</th></tr></thead><tbody><tr><td><p><strong>Base path</strong></p></td><td><p>Specifies the URL prefix for all instance paths, relative to the host root. It must start with a leading slash <code>/</code>.</p></td><td><p>Yes</p></td><td></td></tr><tr><td><p><strong>Client provider</strong></p></td><td><p>Specifies a client provider for the instance.</p></td><td><p>No</p></td><td><p>Anypoint Platform acts as the client provider by default. To configure an external client provider, see <a href="https://docs.mulesoft.com/access-management/managing-api-clients">Client Providers</a>.</p></td></tr><tr><td><p><strong>Instance label</strong></p></td><td><p>Specifies a label for the instance.</p></td><td><p>No</p></td><td><p>If you have multiple managed instances of the same asset, add a label to differentiate each instance from the others.</p></td></tr><tr><td><p><strong>Advanced Options</strong></p></td><td></td><td></td><td></td></tr><tr><td><p><strong>Consumer endpoint</strong></p></td><td><p>Specifies a proxy application’s address for consumers to use for sending requests.</p></td><td><p>No</p></td><td></td></tr></tbody></table>

    Self-Managed Omni Gateway (Connected Mode)

    <table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Field Name</th><th>Description</th><th>Required</th><th>Notes</th></tr></thead><tbody><tr><td><p><strong>Protocol</strong></p></td><td><p>Specifies whether to use HTTP or HTTPS.</p></td><td><p>Yes</p></td><td><p>If you select HTTPS, specify a TLS context for inbound traffic.</p></td></tr><tr><td><p><strong>Inbound TLS</strong></p></td><td><p>TLS Context used for the inbound HTTPS traffic.</p></td><td><p>No</p></td><td><p><a href="https://docs.mulesoft.com/gateway/latest/conn-tls-config">Configure a TLS Context for Omni Gateway</a> before adding a TLS Context to your server.</p></td></tr><tr><td><p><strong>Port</strong></p></td><td><p>Specifies the number to use if the displayed port is incorrect.</p></td><td><p>No</p></td><td><p>Instances can share the same port across the same target if the <strong>Base path</strong> is different for both instances.</p></td></tr><tr><td><p><strong>Base path</strong></p></td><td><p>Specifies the URL prefix for all server paths, relative to the host root. It must start with a leading slash <code>/</code>.</p></td><td><p>Yes</p></td><td></td></tr><tr><td><p><strong>Instance label</strong></p></td><td><p>Specifies a label for the instance.</p></td><td><p>No</p></td><td><p>If you have multiple managed instances of the same asset, add a label to differentiate each instance from the others.</p></td></tr><tr><td><p><strong>Advanced Options</strong></p></td><td></td><td></td><td></td></tr><tr><td><p><strong>Consumer endpoint</strong></p></td><td><p>Specifies a proxy application’s address for consumers to use for sending requests.</p></td><td><p>No</p></td><td></td></tr></tbody></table>

9.  Click **Next**.

10. Configure the upstream services for your API instances:

    <table><colgroup><col> <col> <col> <col></colgroup><tbody><tr><td><p>Field Name</p></td><td><p>Description</p></td><td><p>Required</p></td><td><p>Notes</p></td></tr><tr><td><p><strong>Route Label</strong></p></td><td><p>Label to better identify multiple API instances.</p></td><td><p>Yes</p></td><td><p>By default, the label is the API name.</p></td></tr><tr><td><p><strong>Upstream URL</strong></p></td><td><p>URL to access for the upstream service. This must end with a <code>/</code>.</p></td><td><p>Yes</p></td><td><p>For example, use the URL of your asset in Exchange.</p></td></tr><tr><td><p><strong>Outbound TLS</strong></p></td><td><p>TLS Context used for the outbound traffic to the upstream service</p></td><td><p>No</p></td><td><p><a href="https://docs.mulesoft.com/gateway/latest/conn-tls-config">Configure a TLS Context for Omni Gateway</a> before adding a TLS Context to your server.</p></td></tr></tbody></table>

    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

- [API Manager Overview](https://docs.mulesoft.com/api-manager/latest/latest-overview-concept)

- [Defining Agent Networks](https://docs.mulesoft.com/agent-network/latest/af-define-your-agent-network-specification)

- [Downloading Omni Gateway](https://docs.mulesoft.com/gateway/latest/install)

- [Registering and Running Omni Gateway in Connected Mode](https://docs.mulesoft.com/gateway/latest/conn-reg-run)