Skip to main content
Version: 8.9 (unreleased)

Configure MCP Client connectors

Learn how to configure MCP Client connectors, including connector mode, tool access, and availability.

Connector mode

Choose how the connector operates based on your use case.

AI Agent tool mode

Use when the connector is invoked as a tool from within an AI Agent ad-hoc sub-process. This is the default mode.

The Method and Parameters fields accept FEEL expressions and default to toolCall.method and toolCall.params, which are automatically populated by the AI Agent connector during tool discovery and tool calling.

Operation

Configure the operation to execute on the MCP server. You typically only need to change the default value if the ad-hoc sub-process multi-instance uses an input element other than toolCall.

FieldRequiredDescription
MethodYesThe MCP method to call. Defaults to toolCall.method.
ParametersYesThe parameters to pass with the MCP client execution. Defaults to toolCall.params.

Standalone mode

Use when invoking MCP operations directly from a BPMN process without an AI Agent. This mode allows you to call MCP servers independently of the agentic orchestration flow.

Select the operation to perform:

OperationDescriptionConfiguration
List toolsRetrieves the list of tools available on the MCP server.No additional configuration required.
Call toolInvokes a specific tool on the MCP server.Tool name: The name of the tool to invoke.
Arguments: Tool arguments as a FEEL context expression.

Tools

Filter the list of tools provided by the MCP server. If not configured, all tools provided by the MCP server will be available to the AI agent.

FieldRequiredDescriptionExample
Included toolsNoList of allowed tools provided by the MCP server.["read_file", "read_multiple_files"]
Excluded toolsNoList of tools to exclude. Overrides any included tools.["write_file"]

For example, an MCP client connected to a file system MCP server could be configured with ["read_file", "read_multiple_files"] as included tools to only allow read-only operations to the file system. Alternatively, it could be configured with ["write_file"] as a list of excluded tools to prevent write operations.

Output mapping

Specify the process variables to map and export the tool calling response into.

FieldRequiredDescription
Result variableYesDefaults to toolCallResult. Change only if using the AI Agent Task connector and the output mapping of the ad-hoc sub-process multi-instance is configured to use a different variable for the content mapping.
Result expressionNoOptionally unpack the response content into multiple process variables using the Result expression field as a FEEL context expression.