Skip to main content
Reference under review. The endpoints documented on this page use /resource/.../runtime-internal/... and similar internal paths. They are not part of the public integration API and may change between releases without notice. For supported MCP setup, see MCP Integration overview.

Overview

The MCP API provides programmatic access to manage Model Context Protocol servers, their tools, and integrations within FlowX.AI. Use these endpoints to automate MCP server configuration, test connections, and manage tool availability.
All API endpoints require proper authentication and authorization. Ensure you have the necessary permissions to access Integration Management APIs.

Base URL

Replace {your-domain} with your FlowX.AI deployment domain.

Authentication

All API requests must include authentication headers. The specific authentication mechanism depends on your FlowX.AI deployment configuration. Example Request Headers:

MCP System Management

Create MCP System

Create a new MCP server connection as a data source.

Path Parameters

string
required
The unique identifier of the application.
string
required
The unique identifier of the application version.

Request Body

string
required
The action to perform. Must be CREATE for creating a new system.
string
required
The name of the MCP server resource.Validation:
  • Must be unique within the project
  • Only letters, numbers, and special characters [], (), ., _, - are allowed
object
required
The configuration payload for the MCP system.
string
required
The display name for the MCP server.
string
required
The system type. Must be MCP for MCP servers.Allowed values: REST, NOSQL_DB, MCP
string
required
The base URL of the MCP server.Example: https://api.example.com/mcp
object
required
Authentication configuration for the MCP server.
string
required
The authentication type.Allowed values: NO_AUTH, SERVICE_ACCOUNT
object
Authentication configuration details (required when type is not NO_AUTH).
string
OAuth 2.0 client ID (required for SERVICE_ACCOUNT).
string
OAuth 2.0 client secret (required for SERVICE_ACCOUNT).
string
OAuth 2.0 token endpoint URL (required for SERVICE_ACCOUNT).
string
Optional description of the MCP server’s purpose.

Request Example

Response

string
The unique identifier of the created MCP system.
string
The resource identifier used for referencing this system.
string
The resource definition identifier.
string
The system type, always MCP for MCP servers.
array
Array of available tools. Initially empty; populated after connection test.
Client secrets are not returned in API responses for security reasons.

Test MCP Connection

Test the connection to an MCP server before or after creating it.

Path Parameters

string
required
The unique identifier of the application.
string
required
The unique identifier of the application version.

Request Body

string
required
The base URL of the MCP server to test.
object
required
Authentication configuration to test.
string
required
The authentication type.Allowed values: NO_AUTH, SERVICE_ACCOUNT
object
Authentication configuration details (required when type is not NO_AUTH).

Request Example

Response

number
HTTP status code: 200 for success, 400/500 for failures.
string
Human-readable message describing the result.
array
Array of available tools (only included on successful connection).

Get MCP System Details

Retrieve detailed information about an MCP system, including its tools.

Path Parameters

string
required
The unique identifier of the application.
string
required
The unique identifier of the application version.
string
required
The resource ID of the MCP system.

Response


Get All Systems

Retrieve information about all available systems, including MCP servers, filtered by type.

Path Parameters

string
required
The unique identifier of the application.
string
required
The unique identifier of the application version.

Query Parameters

boolean
default:"false"
Whether to include manifest information in the response.
string
Comma-separated list of dependency types to include (e.g., LIB).

Response

This endpoint returns all system types (REST, NOSQL_DB, MCP). Filter by the type field to identify MCP servers.

Tool Management

Enable/Disable MCP Tool

Enable or disable a specific tool from an MCP server.

Path Parameters

string
required
The unique identifier of the application.
string
required
The unique identifier of the application version.
string
required
The resource ID of the MCP system.
string
required
The ID of the MCP system.
string
required
The ID of the tool to enable or disable.

Request Body

boolean
required
Set to true to enable the tool, false to disable it.

Request Example

Response

number
HTTP status code.
string
Human-readable message describing the result.
object
The updated tool object with its new status.
Disabling a tool that is currently used in active workflows may affect those workflows. Always verify tool usage before disabling.

Workflow Node Configuration

Custom Agent Node Structure

When creating or updating a Custom Agent node in a workflow, use the following structure:
The mcpServers array in aiOptions references MCP systems by their resourceDefinitionId and appId, allowing the Custom Agent to access enabled tools from those servers.

Error Codes

Common HTTP status codes returned by MCP APIs:

Common Error Messages

Error: “Name must be unique inside the project.”Cause: An MCP system with this name already exists in the project.Solution: Choose a different, unique name.
Error: “Name can only contain letters, numbers and the following special characters [] () . _ -”Cause: The name contains invalid special characters.Solution: Remove or replace invalid characters with allowed ones.
Error: “Connection failed: Invalid authentication credentials”Cause: The provided authentication credentials are incorrect or expired.Solution: Verify the client ID, client secret, and identity provider URL.
Error: “Connection failed: MCP server is unreachable”Cause: The MCP server is down or the URL is incorrect.Solution: Verify the server URL and ensure the server is running.
Error: “Insufficient permissions to access Integration Management”Cause: Your user account doesn’t have the required permissions.Solution: Contact your administrator to grant Integration Management access rights.

Rate Limiting

Rate limiting policies depend on your FlowX.AI deployment configuration. Contact your system administrator for specific rate limit details.

Next steps

Add MCP Data Source

Learn how to configure MCP servers via UI

Custom Agent Node

Use MCP tools in Integration Designer workflows

MCP Integration Overview

Learn about MCP integration capabilities

Integration Designer

Learn about Integration Designer and data sources
Last modified on May 12, 2026