Skip to main content

MCP Server Connector

The MCP Server Connector lets an integration flow call a tool on a Model Context Protocol (MCP) server as a single step of the process, and use the returned result in the rest of the flow.

Service Description

There is a single component option to configure a connector to communicate with an MCP server:

  • MCP Server Connector

The Model Context Protocol is an open standard that lets AI models and automation layers invoke typed operations — tools — exposed by a server. The MCP Server Connector brings that capability inside MIP: instead of opening a separate, ungoverned channel to an AI or tool provider, the call becomes one node in an existing integration flow. The connector resolves the tool's arguments from the message, invokes the configured MCP server, and places the tool result back on the flow so the following steps (mappings, decisions, other connectors) can act on it.

Because the call lives inside the flow, it inherits everything the flow already provides: the same execution log, the same monitoring panel, the same error-handling pattern, and the same identity and authorization model. The MCP server itself — its connection details, transport, authentication and discovered tools — is defined once under Operations → MCP Servers and referenced here by name, so a single definition can be reused across many flows.

Beginning

Follow these steps before starting the integration:

  • Define the MCP server under the MCP Servers tab on the Operations page (Server Config JSON, transport, authentication and Default Tool).
  • Run Refresh Tools on that MCP Server so its tool catalog is available, and confirm the Status is Connected.
  • If the server requires authentication, create the matching credential (Bearer, API Key, Basic or OAuth2) in the Credentials tab and reference it from the MCP Server definition.