MCP Server Trigger

Learn more about the MCP Server Trigger and how to use it on the Digibee Integration Platform.

Overview

The MCP Server Trigger is a trigger that allows a Digibee pipeline to receive and process requests coming from an MCP (Model Context Protocol) client.

It acts as the entry point for events or actions initiated by external tools connected through the MCP protocol, for example, tools used by AI assistants or automation services that communicate with Digibee.

What it’s used for

It’s used when you want to:

• Enable AI or external services (like an MCP-compliant assistant) to run an action, get more context or interact with a Digibee pipeline.

• Enforce business playbooks and processes to make your Agent smarter

  • Agents struggle with unstructured guidance. Digibee ensures correct step-by-step execution.

• Make sure your Agent Adhere to business rules and policies

  • You can externalize your rules into MCP pipelines. It'll guarantee deterministic and auditable decisions.

How it works

1. The MCP client sends a request that matches the trigger configuration.

2. The MCP Server Trigger starts the pipeline and provides the input payload.

3. The pipeline executes its logic (transformations, integrations, and so on).

4. The result is returned to the MCP server, following the expected output schema.

Tools configuration

To start configuring the trigger, you must add tools. Each tool exposed by an MCP server includes a set of core fields that define its identity, purpose, permissions, and data structure.

Adding a new tool

1. Go to the MCP Server Tools section.

2. Click Add Tools.

3. Fill in the fields described below.

4. After saving, the tool will appear in the Tools List, where you can add, edit, or delete entries.

Tool fields

Tool Name

Unique identifier for the tool. It should be concise, descriptive, and typically use snake_case.

Example: search_web

Description

Short and clear summary of what the tool does. Helps both the model and users understand its purpose.

Example: Performs a web search and returns the top results.

Schema Configuration

You can define how your tool handles both input and output data using JSON Schemas. These schemas describe the expected structure, data types, and validation rules.

The configuration applies to two sections:

• Input Schema: Defines the structure of the data received by the tool.

• Output Schema: (Optional) Defines the structure of the data returned by the tool.

Both can be configured in two ways:

Option 1: Wizard

Use the Wizard to guide your configuration by clicking Add Property and filling in the parameters:

• Name: Defines the property name within the JSON object.

• Type: Specifies the data type (string, number, boolean, array, or object).

• Required: Indicates whether the field is mandatory.

• Description: Describes the purpose or meaning of the property.

• Enum Values: (Applicable only to the string type) Lists the allowed values for the property.

• Array Type: (Applicable only to the array type) Defines the data type of the array elements (string, number, boolean, or array).

• Object Properties: (Applicable only to the object type) Defines the set of properties contained within the object.

Example: Input Schema

Name	Type	Required	Description	Enum Values
query	string	✅ Yes	The search term or keywords to look up.	—
limit	number	❌ No	Number of results to return.	N/A

Resulting JSON Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "description": "The search term or keywords to look up."
    },
    "limit": {
      "type": "integer",
      "description": "Number of results to return.",
      "default": 5
    }
  },
  "required": ["query"]
}

Example: Output Schema

Name	Type	Required	Description	Array Type
results	array	❌ No	List of URLs matching the search query.	string

Resulting JSON Schema

{
  "type": "object",
  "properties": {
    "results": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "List of URLs matching the search query."
    }
  }
}

Option 2: Schema

Alternatively, enter the JSON Schema directly in the provided field.

Parameters configuration

Parameter	Description	Data type	Default value
Server Name	Name of the MCP server. This is for reference purposes only.	String	N/A
Description	Short description for identifying the MCP Server.	String	N/A
Maximum Timeout	Maximum time (in milliseconds) for the pipeline to process information before returning a response. Limit: 900000 ms.	Integer	30000
The Maximum Allowed Request Size In Mb	Maximum size of the payload in megabytes. The maximum configurable size is 5 MB.	Integer	5
External API	If enabled, the MCP Server becomes accessible through Digibee’s external gateway, allowing it to communicate over the public Internet.	Boolean	True
Internal API	If enabled, exposes the MCP Server through Digibee’s internal gateway, restricting access to the internal network only. Both the External API and Internal API options can be active simultaneously.	Boolean	False
API Key	If enabled, the endpoint can only be accessed with an API key configured in the Digibee Integration Platform.	Boolean	False
Documentation	Optional field to describe the trigger configuration and any relevant business rules.	String	N/A

Visual representation of the tools

After saving the trigger configuration, a visual representation of the tools is displayed in the pipeline.

Tools can only be edited through the trigger's configuration form. Any changes made are immediately reflected in the pipeline after saving.

Each tool is connected to a Block Execution connector. This connector is designed to logically separate the integration into different subflows, making pipeline management easier. To complete the configuration, you must create the flows for each route within the OnProcess and OnException subflows.

Regardless of the number of tools configured, there is always a default route for cases where a tool is not found. You can configure this route to handle missing tools appropriately.

Important notes:

• If you create the flow before configuring the trigger, existing connectors will be disconnected once the trigger is saved.

• Deleting a tool from the Tools List will disconnect the corresponding Block Execution connector from the main flow.