Integration runtime configuration type

mcpoverride type

Use the mcpoverride type to create a configuration object that defines which Model Context Protocol (MCP) tools to enable in an MCP server. This configuration type is applicable only for MCP servers that expose REST API operations from a deployed integration runtime as MCP tools.


Summary of key details for the configuration type

File name or type Contains secrets Path extracted/imported to Maximum allowed per integration runtime
JSON No /home/aceuser/ace-server/overrides/APIName/mcptools.json 1

Creating the file for a configuration object of type mcpoverride

The mcpoverride type requires the contents of a .json file that contains MCP tool definitions for the REST API operations in a deployed integration runtime.

When you create an MCP server that exposes REST API operations as MCP tools, a configuration object of type mcpoverride is generated during the MCP server deployment. This configuration object is applied to the integration runtime that was selected to host the MCP server. The configuration object is named in the format integrationRuntimeName-mcp-overrides and it initially stores the MCP tool definitions that were specified while creating the MCP server. If you subsequently change your MCP tool selections by editing the details of the MCP server, the content of the integrationRuntimeName-mcp-overrides configuration object is updated to reflect your changes. For more information, see Creating and managing Model Context Protocol (MCP) servers.

The following example shows the JSON content of a configuration object that was generated to store the MCP tool definitions that were specified during MCP server creation. 

[
  {
    "name": "CustomerDatabaseV1",
    "mcptools": {
      "CustomerDatabaseV1_addCustomer": {
        "enabled": true,
        "title": "Add a customer to the database",
        "toolType": "RestApi",
        "subtype": "RestApi",
        "rest_path": "/customers",
        "rest_method": "POST",
        "application_uri": "/apiv2/rest-apis/CustomerDatabaseV1"
      },
      "CustomerDatabaseV1_deleteCustomer": {
        "enabled": true,
        "title": "Delete a specified customer from the database",
        "toolType": "RestApi",
        "subtype": "RestApi",
        "rest_path": "/customers/{customerId}",
        "rest_method": "DELETE",
        "application_uri": "/apiv2/rest-apis/CustomerDatabaseV1"
      },
      "CustomerDatabaseV1_getCustomer": {
        "enabled": true,
        "title": "Get a specified customer from the database",
        "toolType": "RestApi",
        "subtype": "RestApi",
        "rest_path": "/customers/{customerId}",
        "rest_method": "GET",
        "application_uri": "/apiv2/rest-apis/CustomerDatabaseV1"
      },
      "CustomerDatabaseV1_updateCustomer": {
        "enabled": true,
        "title": "Update a customer in the database",
        "toolType": "RestApi",
        "subtype": "RestApi",
        "rest_path": "/customers/{customerId}",
        "rest_method": "PUT",
        "application_uri": "/apiv2/rest-apis/CustomerDatabaseV1"
      },
      "CustomerDatabaseV1_getAllCustomers": {
        "enabled": true,
        "title": "Get all customers from the database",
        "toolType": "RestApi",
        "subtype": "RestApi",
        "rest_path": "/customers",
        "rest_method": "GET",
        "application_uri": "/apiv2/rest-apis/CustomerDatabaseV1"
      }
    }
  }
]
Note: At the current time, the mcpoverride configuration type is primarily intended for use by the wizards that you use to create or edit MCP servers from the Dashboard UI.