Skip to main content

MCP Basics

Model Context Protocol (MCP) lets you connect external servers that provide domain-specific tools. These tools extend your AI agents with new capabilities.

After connection, the platform automatically discovers available tools. Agents can use them without hardcoded or custom integrations.

Key Features​

  • Automatic Tool Discovery from remote MCP servers
  • Real-time Capability Extension without redeployment
  • Fine-grained Control via tool filters and name transformations
  • Multiple Server Support through unique integration codes
  • Flexible Authentication options for secure connections

Use Cases​

  • Access domain-specific tools. Examples: weather services, financial calculations, document processing
  • Integrate specialized business services. Examples: CRM operations, inventory management
  • Extend agents with third-party capabilities. Examples: external APIs, analytics services

How MCP Tools Work​

This section explains how MCP tools are discovered, registered, and invoked during agent execution.

MCP Scheme

Tool Discovery​

When an MCP integration is configured, the platform:

  1. Connects to the specified MCP server endpoint
  2. Authenticates using the provided credentials
  3. Requests the list of available tools from the MCP server
  4. Applies name transformations to tool names
  5. Applies include and exclude filters
  6. Registers the resulting tools with the agent

Tool Invocation​

During agent execution:

  1. The agent decides to use an MCP tool based on its workflow configuration
  2. The platform sends a tool execution request to the MCP server using the original tool name provided by the MCP server
  3. The MCP server processes the request and returns results
  4. The platform delivers the results to the agent
  5. The agent incorporates the results into its response or decision-making process

Multiple Integrations​

Multiple MCP servers can be configured with different integration codes. Each integration operates independently:

  • Tools from different servers are isolated by their integration code
  • Authentication, timeouts, and other settings are per-integration
  • Name transformations and filters are applied independently

Example Scenario:

  • Integration Code: WEATHER — Connects to weather service, filters to include only weather-related tools
  • Integration Code: BANKING — Connects to banking API, applies strict authentication and timeout settings
  • Integration Code: DOCS — Connects to document service, transforms tool names to PascalCase with docs_ prefix

⚠️ Note: With stdio transport, the MCP server runs as a single local process per integration code. This process is shared across all agents and sessions using that integration.

Basic Setup​

This basic setup contains all the steps required to integrate MCP servers as agent tools.

How to Set Up an MCP Integration​

Each MCP integration is configured through a web-based form on the Flametree portal. The form collects connection details, authentication credentials, and operational parameters. Multiple MCP servers can be configured simultaneously by assigning each a unique integration code.

  1. Go to Settings > Connectivity
  2. Open MCP > MCP Tools
  3. In the upper-right corner, press Add +
  4. Use the Make default toggle to make this integration default
  5. Use the System integration toggle to make this integration a system integration
  6. Fill in the fields below:
Show MCP configuration fields
FieldDescription
NameCustom name of the integration. Required field
DescriptionCustom description of the integration
Integration codeA unique identifier for an MCP integration. Required field
Server EndpointThe primary connection port for an MCP integration. Required field
Transport ProtocolThe communication protocol used to interact with the MCP server
Authentication TypeSpecifies the authentication mechanism to use when connecting to the MCP server
Auth TokenBearer or authentication token sent in the Authorization header
API KeyThe API key value
API Key HeaderThe HTTP header name
API Key Query ParameterOptional query parameter name for URL-based authentication
Basic Auth UsernameUsername for HTTP Basic authentication
Basic Auth PasswordPassword for HTTP Basic authentication
Custom HeadersJSON object containing HTTP header name–value pairs attached to each MCP server request
Request TimeoutThe maximum time in seconds the platform will wait for a response from the MCP server
Maximum RetriesThe maximum number of retry attempts for failed requests
Include Tools FilterControls which tools from the MCP server are exposed to the agent
Exclude Tools FilterControls which tools from the MCP server are not exposed to the agent
Name TransformerApplies transformations to tool names discovered from the MCP server, improving readability and consistency
Tool listA list of tools available for your MCP server integration. Will be autofilled after you finalize the integration setup. You need to add them to your agent's Workflow
Minimum Pool ConnectionsThe minimum number of connections to maintain in the connection pool
Maximum Pool ConnectionsThe maximum number of concurrent connections allowed to the MCP server
Connection Inactivity TimeoutTime in seconds before idle connections are removed from the pool
  1. Press Save to create the integration

For a complete configuration reference and detailed description of all the fields, go to Configuration Reference

How to Connect to Agent​

After creating an integration with an MCP server, you need to connect the newly created MCP Tool to your agent.

To do this:

  1. In the left sidebar menu, go to Agents
  2. Choose and open the agent you wish to connect
  3. In the right sidebar menu, go to Models > MCP Tools
  4. Select the MCP server you have created
  5. Add the tools you wish to be included in your agent’s communications to the Workflow:
  6. Press Save in the upper-right corner to apply the change

⚠️ Important: After you set up the integration, restart the agent if it was running. To do it, press Stop agent and then Start agent.