MCP Configuration

This article is a complete reference of all the configuration fields you need to fill to set up an MCP server integration. For the setup guide, please go to Basic Setup

---

Configuration Reference

The sections below describe MCP server connection, authentication, and tool configuration. For each field, you will find whether it is required, a description, and examples or allowed values.

Name and Description

Field name	Required	Description	Examples
Name	✅	The name of an MCP server integration displayed on the portal	Weather Server Currency Exchange Server
Description	❌	A brief description of what the integration does	This integration allows the agent to provide currency exchange information to users

Integration Code

Field name	Required	Description	Examples
Integration code	✅	Isolates MCP server configurations and prevents naming conflicts. Scopes discovered tools to the integration code, enabling multiple MCP servers in one agent	WEATHER BANKING ANALYTICS

⚠️ Important: Must be unique across all MCP integrations for the agent. Must be letters and digits only.

Server Endpoint

Field name	Required	Description	Examples
Server Endpoint	✅	The URL of the remote MCP server used to discover and execute tools during agent conversations. Full HTTP or HTTPS URL format	https://bank-api.internal:8443/mcp https://weather-api.example.com/mcp

⚠️ Note: For stdio Transport Protocol, Server Endpoint is a command used to start the MCP server process (for example: python server.py, node index.js). No HTTP connection is used.

Transport Protocol

Field name	Required	Description	Allowed values
Transport	❌	Determines how the platform exchanges messages with the MCP server. Different transports offer varying performance characteristics and compatibility	http_sse — HTTP Server-Sent Events for streaming responses streamable_http — Streamable HTTP with persistent connections for high-performance scenarios stdio — Standard input/output transport for local MCP servers

💡 Tip: Use streamable_http (default) for most production scenarios. Use http_sse if the MCP server specifically requires Server-Sent Events.
stdio transport is intended for local or embedded MCP servers executed as processes and is primarily used for development, testing, or on-prem deployments

Authentication

Authentication settings control how the platform authenticates with the remote MCP server.

Field name	Required	Description	Examples
Authentication Type	✅	Specifies the authentication mechanism to use when connecting to the MCP server. Determines how credentials are transmitted	Allowed values: none (default) bearer token api_key basic custom
Auth Token	When Authentication Type: bearer or token	The platform includes this token in all requests to the MCP server for authentication. Format: token string as provided by the MCP service	sk-1234567890abcdef bearer-token-xyz-789
API Key	When Authentication Type: api_key	API key value used for authentication	api-key-456789
API Key Header	When Authentication Type: api_key	HTTP header name used to send the API key	X-API-Key (default) X-Auth-Token X-RapidAPI-Key
API Key Query Parameter	When Authentication Type: api_key	Optional query parameter name for URL-based API key authentication. If set, the API key is sent in the URL and the header is not used	token api_key auth_token
Basic Auth Username	When Authentication Type: basic	Provides username for HTTP Basic authentication.	admin service_account
Basic Auth Password	When Authentication Type: basic	Provides password for HTTP Basic authentication	secure-pass-123
Custom Headers	When Authentication Type: custom	Allows arbitrary HTTP headers to be sent with every request to the MCP server. Enables integration with MCP servers using proprietary or complex authentication schemes not covered by standard types. Format: JSON object	{"X-Custom-Auth": "value123"} {"X-Client-ID": "abc", "X-Environment": "production"} {"X-Version": "v2", "X-Tenant": "customer-corp"}

Connection Settings

Field name	Required	Description	Recommended values
Request Timeout	❌	Prevents requests from hanging indefinitely. If a request exceeds this timeout, it is cancelled and an error is returned	Standard operations: 30 sec (default) Long-running operations: 60 to 120 sec
Maximum Retries	❌	Improves reliability by automatically retrying transient failures such as network glitches or temporary server unavailability	Critical operations: 5 to 10 Standard operations: 3 (default) Time-sensitive operations: 1 to 2

Connection Pooling

Connection pooling optimizes performance by reusing connections to the MCP server.

Field name	Required	Description	Recommended values
Minimum Pool Connections	❌	Pre-established connections reduce latency for subsequent requests but consume additional resources	Standard scenarios: 0 (default, connections created on demand) High-traffic scenarios: 2 to 5
Maximum Pool Connections	❌	Limits resource consumption and prevents overwhelming the server. Requests exceeding this limit wait for available connections	High-concurrency scenarios: 10 to 20 Standard scenarios: 5 (default) Resource-constrained scenarios: 2 to 3
Connection Inactivity Timeout	❌	Balances resource efficiency with connection reuse. Shorter timeouts free resources faster; longer timeouts reduce reconnection overhead	Frequent usage: 600 to 1800 sec (default: 600) Infrequent usage: 300 sec

Tool Discovery and Naming

Tool Name Transformation

Field name	Required	Description	Examples
Name Transformer	❌	Tool names are transformed before being registered with the agent. This affects how tools are referenced in agent configurations and invoked during execution.	See Transformation Rules below

Transformation Rules

Case Transformers

• camel — Convert to camelCase (for example, get_weather_forecast → getWeatherForecast)
• pascal — Convert to PascalCase (for example, get_weather_forecast → GetWeatherForecast)
• kebab — Convert to kebab-case (for example, get_weather_forecast → get-weather-forecast)
• snake — Convert to snake_case (for example, GetWeatherForecast → get_weather_forecast)
• upper — Convert to UPPERCASE (for example, get_weather → GET_WEATHER)
• lower — Convert to lowercase (for example, GetWeather → getweather)
• capitalize — Capitalize first letter
• title — Convert to Title Case

Regex Transformers

• s/pattern/replacement/flags — Regular expression substitution

Syntax:

• pattern — Regular expression to match
• replacement — Replacement string (use \1, \2 for capture groups)
• flags — Optional flags (i for case-insensitive, g for global)

Composite Transformers

Multiple transformations can be chained using commas. They are applied sequentially from left to right.

Examples:

• pascal — Convert all tool names to PascalCase
• s/^/weather_/ — Add weather_ prefix to all tools
• s/Get/Fetch/gi — Replace Get with Fetch (case-insensitive, globally)
• pascal,s/^/docs_/ — Convert to PascalCase, then add docs_ prefix
• s/^(.*?)_v[0-9]+.*$/\1/i,pascal — Remove version suffix and convert to PascalCase

Tool List and Filtering

Tool list and filters control which tools from the MCP server are exposed to the agent.

Field name	Required	Description	Examples
Tool list	✅ autofilled	Contains all the tools available within the MCP integration. It is autofilled after you configure and save the MCP server integration — you don't have to fill this field manually. If the field is not filled after you save the integration, it means the MCP server is not properly configured	get_current_weather — for a weather service SearchProductInventoryInfo — for a product info service
Include Tools Filter	❌	Only tools whose names contain at least one of the substrings are included. Filters are applied after name transformation, allowing selective exposure of relevant tools while hiding others. Comma-separated list of substrings.	weather,forecast — include only tools containing "weather" or "forecast" search,query — include only search and query tools
Exclude Tools Filter	❌	Tools whose names contain any of the substrings are excluded. Filters are applied after name transformation and are useful for hiding debug, internal, or administrative tools. Comma-separated list of substrings.	debug,internal — exclude tools containing "debug" or "internal" test,mock — exclude test and mock tools

⚠️ Important: Filter Order: Name transformation → Include Tools Filter → Exclude Tools Filter