Skip to Content

MCP Client (Beta) connector

Summary

The MCP Client (Beta) connector establishes access to a Model Context Protocol (MCP) server.

The MCP Client (Beta) connector provides an interface for creating an MCP Client (Beta) connection, the foundation used for generating instances of MCP Client (Beta) activities. These activities, once configured, interact with an MCP server through the connection.

The MCP Client (Beta) connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Note

This connector is an MCP client, used to connect to an external MCP server to use its tools and capabilities. The connector doesn't provide tools itself.

Note

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

Connector overview

This connector is used to first configure an MCP Client (Beta) connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific MCP Client (Beta) connection and its activities are referred to as an MCP Client (Beta) endpoint:

MCP Client (Beta) activity types

  • List Tools: Retrieves available tools from an MCP server and is intended to be used as a source in an operation. Use the returned data to configure the Invoke Tools activity.

  • Invoke Tools: Executes a specific tool on an MCP server and is intended to be used as a target in an operation. Use the List Tools activity first to see available tools and their required fields.

Note

This connector is a Connector SDK-based connector, which may be referred to by Jitterbit when communicating changes made to connectors built with the Connector SDK.

Endpoints created with this connector are included in endpoint usage reporting and count toward your license.

Prerequisites

The MCP Client (Beta) connector requires the use of an agent version 10.1 or later. These agent versions automatically download the latest version of the connector when required.

Troubleshooting

If you experience issues with the MCP Client (Beta) connector, these troubleshooting steps are recommended:

  1. Click the Test button in the connection configuration to ensure the connection is successful and to ensure the latest version of the connector is downloaded to the agent (unless using the Disable Auto Connector Update organization policy).

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for cloud agents or for private agents) to generate additional log files and data.

  4. If using private agents, you can enable connector verbose logging for this connector by adding this logger configuration entry to your private agent's logback.xml file:

    <logger name="org.jitterbit.connector.mcp" level="DEBUG"/>

    For more information on connector verbose logging, see Verbose logging for connectors using Jitterbit private agents.

  5. If using private agents, you can check the agent logs for more information.