Skip to main content

​
Overview

The Model Context Protocol (MCP) integration connects FlowX.AI with external MCP servers and exposes their tools to AI agents. AI agents can interact with external systems, databases, APIs, and services through this protocol.
MCP is a protocol for AI agents to access external tools and data sources.

​
Key features

  • Connect MCP servers as data sources in Integration Designer
  • Enable or turn off specific tools exposed by MCP servers
  • Use MCP tools in workflow processes through Custom Agent nodes
  • Secure connections with multiple authentication methods
  • Monitor tool usage and execution details in console logs

​
How it works

​
High-level workflow

  1. Add MCP server: Configure an MCP server connection as a data source in Integration Designer
  2. Authorize access: Authenticate the connection using supported authentication methods
  3. Manage tools: View and enable or turn off available tools from the MCP server
  4. Use in workflows: Add Custom Agent nodes to workflows and select which MCP servers to use
  5. Execute and monitor: Run workflows and track tool usage in console logs

​
Supported protocols and features

The MCP integration is actively being developed. The features listed below represent the current capabilities. Additional protocol support and authentication methods will be added in future releases.

​
Transport protocols

The following transport protocols are currently supported:
Server-Sent Events protocol for real-time, unidirectional communication from the MCP server to FlowX.AI.Use Case: Ideal for streaming responses and long-running operations where the server needs to push updates to the client.
HTTP-based streaming protocol for receiving data in chunks over a persistent connection.Use Case: Suitable for large data transfers and scenarios where you need progressive response handling.
Not Currently Supported:
  • Proxy-based MCP connections are not supported in the current release

​
Authentication methods

MCP integrations support the following authentication methods:

​
None

No authentication required. Use for public MCP servers or development environments.

​
Service account

OAuth 2.0 service account authentication using the client credentials flow. Required Configuration:
  • Client ID: The OAuth client identifier
  • Client Secret: The OAuth client secret
  • Identity Provider URL: The authorization server endpoint
Use Service Account authentication for production environments.
OAuth Support: Currently, only the OAuth 2.0 client credentials flow is supported. Other OAuth flows (authorization code, implicit, etc.) will be added in future releases.

​
Use cases

​
External API integration

Connect to external APIs and services through MCP tools. AI agents can fetch data, trigger actions, and integrate with third-party systems.

​
Database operations

Query databases, retrieve records, and perform data operations through MCP tools.

​
Custom business logic

Expose custom business logic as MCP tools for AI agents to execute.

​
Multi-system orchestration

Use multiple MCP servers in a single Custom Agent node to orchestrate operations across different systems.

​
Next steps

MCP Data Sources

Add, configure, and manage MCP servers and their tools

Custom Agent Node

Use MCP tools in workflows with Custom Agent nodes

MCP API Reference

API documentation for MCP integration

Integration Designer

Integration Designer and data sources

Integrations Overview

Integration ecosystem overview