MCP connector

The Model Context Protocol (MCP) connector lets you create and configure an MCP connection in Integration Connectors. You can use this connection in your business applications to securely exchange data and perform operations with MCP.

For the list of supported entities and operations, see Entity operation examples. For information about the supported connector-specific actions, see Actions.

MCP connector versions

The MCP connector supports two versions:

MCP v1: Use this connector version to access the MCP v1 API.
MCP v2: Use this connector version to access the MCP v2 API.

For information about creating a MCP connection, see Create and configure a MCP connector.

Entities, operations, and actions

All the Integration Connectors provide a layer of abstraction for the objects of the connected application. You can access an application's objects only through this abstraction. The abstraction is exposed to you as entities, operations, and actions.

Entity: An entity can be thought of as an object, or a collection of properties, in the connected application or service. The definition of an entity differs from a connector to a connector. For example, in a database connector, tables are the entities, in a file server connector, folders are the entities, and in a messaging system connector, queues are the entities.
However, it is possible that a connector doesn't support or have any entities, in which case the Entities list will be empty.
Operation: An operation is the activity that you can perform on an entity. You can perform any of the following operations on an entity:
- List
- Get
- Create
- Update
- Delete
Selecting an entity from the available list, generates a list of operations available for the entity. For a detailed description of the operations, see the Connectors task's entity operations. However, if a connector doesn't support any of the entity operations, such unsupported operations aren't listed in the Operations list.
Action: An action is a first class function that is made available to the integration through the connector interface. An action lets you make changes to an entity or entities, and vary from connector to connector. Normally, an action will have some input parameters, and an output parameter. However, it is possible that a connector doesn't support any action, in which case the Actions list will be empty.

Supported entities and operations

The MCP connector supports entities and operations, with the specific ones available depending on the tool connected through MCP.

Entity operation examples

This section provides examples of entity operations for different tools.

List Jira Issues entity

This example lists all Issues in the Issues entity using a Jira MCP connection.

In the Configure Connector Task window, click Entities.
Select Issues from the Entity list.
Select the List operation, and then click Done.

In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:

{
      "operation": "LIST_ENTITIES",
      "connection_name": "projects/YOUR_PROJECT_ID/locations/YOUR_LOCATION/connections/YOUR_JIRA_CONNECTION_NAME",
      "service_name": "projects/YOUR_TENANT_PROJECT_ID/locations/YOUR_LOCATION/namespaces/cloudrun/services/YOUR_RUNTIME_SERVICE",
      "host": "https://YOUR_TENANT_PROJECT_ID-YOUR_LOCATION.us-west1-runtime-connectors-google.com",
      "entity": "Issues",
      "entity_id": "Issues",
      "page_token": ""
    }

List all requests

This example lists all Requests in the Requests entity.

In the Configure Connector Task window, click Entities.
Select Requests from the Entity list.
Select the List operation, and then click Done.

Get a user by ID

This example gets the user with AccountId as `6035864ce2020c0070b5285b` from the Users entity. `AccountId` is the primary key for the Users entity. To get a specific entity, use the List operation with a filterClause on the primary key, as the Get operation isn't supported for this entity.

In the Configure Connector Task window, click Entities.
Select Users from the Entity list.
Select the List operation, and then click Done.
In the Task Input section of the Connectors task, click filterClause and then enter `AccountId`=6035864ce2020c0070b5285b in the Default Value field.

Actions

The MCP connector provides various actions, with the specific ones available depending on the tool connected through MCP.

Action examples

This section describes how to perform some of the actions available through the MCP connector for different tools.

Jira actions: Get issues

This example demonstrates how to list Jira issues using an MCP connection configured for Jira.

In the Configure connector task dialog, click Actions.
Select the get_issues action, and then click Done.
In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
```
  {
    "issue_ids": ["YOUR_ISSUE_ID_1", "YOUR_ISSUE_ID_2"]
  }
```

Linear actions: List issues

This example demonstrates how to list issues in Linear using an MCP connection configured for Linear.

In the Configure connector task dialog, click Actions.
Select the list_issues action, and then click Done.
In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
```
  {
    "limit": 50
  }
```

Sentry Actions: Whoami

This example demonstrates how to get user info from Sentry using an MCP connection configured for Sentry.

In the Configure connector task dialog, click Actions.
Select the whoami action, and then click Done.
In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
```
  {
    "name": "example-org"
  }
```

Find organizations

This example demonstrates how to find organizations in Sentry using an MCP connection configured for Sentry.

In the Configure connector task dialog, click Actions.
Select the find_organizations action, and then click Done.
In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
```
  {}
```

Intercom Actions: Search conversations

This example demonstrates how to search for conversation details in Intercom using an MCP connection configured for Intercom.

In the Configure connector task dialog, click Actions.
Select the search action, and then click Done.
In the Task Input section of the Connectors task, click connectorInputPayload and then enter a value similar to the following in the Default Value field:
```
  {
    "query": "object_type:conversations state:open created_at:gt:2024-01-01"
  }
```

System limitations

The MCP connector has system limitations that may vary based on the specific tool being connected. By default, Integration Connectors allocates 2 nodes (for better availability) for a connection.

For information on the limits applicable to Integration Connectors, see Limits.

Note: The number of Integration Connectors nodes will autoscale dynamically based on your usage. However, if you want to reserve capacity for large volumes without waiting for autoscaling, you can adjust the minimum node value for a connection. More nodes are required to process more transactions for a connection. Conversely, fewer nodes are required if a connection processes fewer transactions. To configure the node values, do the following:

If you are a pay-as-you-go customer, configure the minimum and maximum node value in the edit connection page.
If you are a subscription based customer, contact support.

The maximum transactions that a node can handle depends on various factors. So, before adjusting the minimum nodes for better throughput, it is recommended you check if your backend systems are set up optimally to handle the required traffic.