# Integrate an MCP server with Amazon Connect
<a name="3p-apps-mcp-server"></a>

To integrate an MCP server with Amazon Connect, you must configure a Bedrock AgentCore gateway. The gateway transforms your APIs, Lambda functions, and services into MCP-compatible tools for AI agents.

**Note**  
Only one instance can be associated with a gateway, and that instance must be configured with the gateway's Discovery URL in Bedrock AgentCore. Each gateway can only be used with one MCP server.

## How to integrate an MCP server
<a name="3p-apps-mcp-server-how-to-integrate"></a>

1. On the **Add integration** page, enter the following information:

   1. **Basic information**
      + **Display name** – A friendly name for the application. This name is displayed on security profiles and to your agents on the tab in the agent workspace. You can change this name later.
      + **Description (optional)** – You may optionally provide a description for this application.
      + **Integration type** – Select **MCP server**.  
![\[The Add integration page showing Basic information fields for an MCP server application.\]](http://docs.aws.amazon.com/connect/latest/adminguide/images/integrations-3p-mcp-app.png)

   1. **Application details**

      Select a Bedrock AgentCore gateway to connect with Amazon Connect. Gateways convert APIs, Lambda functions, and services into MCP-compatible tools for AI agents. If no gateways currently exist, create a new one using Bedrock AgentCore.  
![\[The Application details section showing gateway selection.\]](http://docs.aws.amazon.com/connect/latest/adminguide/images/integrations-3p-mcp-select-gateway.png)

      A new gateway can be created in Bedrock AgentCore.
**Note**  
The Discovery URL must follow this format: `[connect instance URL]/.well-known/openid-configuration`. For example: `https://my-instance.my.connect.aws/.well-known/openid-configuration`.  
![\[Additional gateway configuration options.\]](http://docs.aws.amazon.com/connect/latest/adminguide/images/3p-apps-mcp-bedrock.png)

   1. **Instance association (optional)**

      Select the instance that is configured with the selected gateway's Discovery URL. Defaults to **None**. If you are not ready to select an instance or if no instance has been associated with the selected gateway's Discovery URL, you may still create the MCP server integration now and associate an instance later.  
![\[The Instance association section showing instance selection options.\]](http://docs.aws.amazon.com/connect/latest/adminguide/images/3p-apps-mcp-instance.png)

1. Choose **Add integration**.

1. If the integration was successfully created, you will be sent to the **View integration** page where you will see a success banner and the integration summary.  
![\[The View integration page showing a success banner after integrating an MCP server.\]](http://docs.aws.amazon.com/connect/latest/adminguide/images/3p-apps-mcp-success.png)