Skip to Content

MCP Client (Beta) Invoke Tools activity

Introduction

An MCP Client (Beta) Invoke Tools activity, using its MCP Client (Beta) connection, executes a specific tool on an MCP server and is intended to be used as a target to consume data in an operation. Use the List Tools activity first to see available tools and their required fields.

Note

This connector is currently in beta and available to select organizations. To request beta access or provide feedback, contact the Jitterbit Product Team.

Create an MCP Client (Beta) Invoke Tools activity

An instance of an MCP Client (Beta) Invoke Tools activity is created from an MCP Client (Beta) connection using its Invoke Tools activity type.

To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an activity instance in Component reuse.

An existing MCP Client (Beta) Invoke Tools activity can be edited from these locations:

Configure an MCP Client (Beta) Invoke Tools activity

Follow these steps to configure an MCP Client (Beta) Invoke Tools activity:

Step 1: Enter a name and specify settings

In this step, provide a name for the activity and specify the tool. Each user interface element of this step is described below.

Tip

Fields with a variable icon support using global variables, project variables, and Jitterbit variables. Begin either by typing an open square bracket [ into the field or by clicking the variable icon to display a list of the existing variables to choose from.

  • Name: Enter a name to identify the activity. The name must be unique for each MCP Client (Beta) Invoke Tools activity and must not contain forward slashes (/) or colons (:).

  • Choose tool: You can specify a tool using either of these two options: Inform tool name manually or Select tool from list.

    • Inform tool name manually: Select this option to provide the name of the tool in the MCP server. When this option is selected, this field is visible:

      • Tool name: Enter the name of the tool.

    • Select tool from list: Select this option to choose from a list of tools available in the MCP server. When this option is selected, this field is visible:

      • Select a Tool: This section displays tools that are available in the MCP server.

      • Selected tool: After you select a tool, it is listed here.

      • Search: Enter any column's value in the search box to filter the list of tools. The search is not case-sensitive. If tools are already displayed within the table, the table results are filtered in real time with each keystroke. To reload tools from the endpoint when searching, enter search criteria and then refresh, as described below.

      • Refresh: Click the refresh icon or the word Refresh to reload tools from the MCP server endpoint. This may be useful if tools have been added to the MCP server. This action refreshes all metadata used to build the table of tools displayed in the configuration.

      • Selecting a tool: Within the table, click anywhere on a row to select a tool. Only one tool can be selected. The information available for each tool is fetched from the MCP server endpoint:

        • Name: The name of the tool.

        • Description: The description of the tool.

      Tip

      If the table does not populate with available tools, the MCP server connection may not be successful. Ensure you are connected by reopening the connection and retesting the credentials.

  • Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.

  • Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Step 2: Review the data schemas

Any request or response schemas are displayed. Each user interface element of this step is described below.

  • Data schemas: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.

    The MCP Client (Beta) connector uses the Model Context Protocol. The schema nodes and fields are defined by the MCP server. Use the List Tools activity first to see available tools and their required fields.

  • Refresh: Click the refresh icon or the word Refresh to regenerate schemas from the MCP Client (Beta) endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.

  • Back: Click to temporarily store the configuration for this step and return to the previous step.

  • Finished: Click to save the configuration for all steps and close the activity configuration.

  • Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.

Next steps

After configuring an MCP Client (Beta) Invoke Tools activity, complete the configuration of the operation by adding and configuring other activities, transformations, or scripts as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.

Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.

MCP Client (Beta) Invoke Tools activities can be used as a target with these operation patterns:

To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.

When ready, deploy and run the operation and validate behavior by checking the operation logs.