Skip to Content

MCP Client (Beta) List Tools activity

Introduction

An MCP Client (Beta) List Tools activity, using its MCP Client (Beta) connection, retrieves available tools from an MCP server and is intended to be used as a source to provide data in an operation. Use the returned data to configure the Invoke Tools activity.

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) List Tools activity

An instance of an MCP Client (Beta) List Tools activity is created from an MCP Client (Beta) connection using its List 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) List Tools activity can be edited from these locations:

Configure an MCP Client (Beta) List Tools activity

Follow these steps to configure the MCP Client (Beta) List Tools activity:

Step 1: Enter a name

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

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

  • 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 List Tools activity retrieves available tools and their required fields from the MCP server. Use the returned data to configure the Invoke Tools activity.

  • 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) List 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) List Tools activities can be used as a source 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.