Integration components connect the flow to MCP servers (workspace-configured or external) and third-party collaboration tools.
MCP Client
Connects to an MCP (Model Context Protocol) server configured in your workspace and exposes its tools to an Agent component.
Use in a flow
- Ensure the MCP server you need is deployed and enabled in your workspace.
- Add an MCP Client node to the canvas.
- Select the server from the MCP Server dropdown (use the refresh button if the list is empty).
- Optionally add entries under MCP Configuration to pass extra key-value settings to the tools.
- Connect the Tools output to agent_tools on your Agent.
MCP Client (Tools) ──► Agent (agent_tools)
Parameters
| Parameter | Required | Description |
|---|---|---|
| MCP Server | Yes | Select a deployed MCP server from your workspace. Use the refresh button to reload the dropdown. |
| MCP Configuration | No | Optional key-value pairs passed to the MCP tools as configuration (e.g., a database name or API scope). |
Outputs
| Output | Description |
|---|---|
| Tools | All tools from the selected MCP server, ready to connect to an Agent’s agent_tools input. |
Limitations
- Workspace servers only — Only servers deployed and enabled in your workspace appear in the dropdown.
- One server per component — Each MCP Client node connects to a single server. Add multiple nodes for multiple servers.
- Deployed status required — Only servers in a deployed state are available for selection.
Public MCP Client
Connects to any publicly accessible MCP server by URL. Add one or more server endpoints, connect the component to an Agent, and the Agent can use the tools exposed by those servers.
Use in a flow
- Add a Public MCP Client node to the canvas.
- Under MCP Server Configurations, add each server you want to use (name, URL, and optional headers).
- Enable the servers you need. If a server shows Requires Auth, click Authorize and complete the sign-in flow.
- Connect the Tools output to agent_tools on your Agent.
Public MCP Client (Tools) ──► Agent (agent_tools)
MCP Server Configurations
Each row represents one MCP server:
| Field | Required | Description |
|---|---|---|
| Name | Yes | A friendly label for the server. |
| Server URL | Yes | The HTTP URL of the MCP server. |
| Headers (JSON) | No | Optional custom HTTP headers as JSON (e.g., {"Authorization": "Bearer TOKEN"}). |
| Enabled | — | Toggle to include this server when the flow runs. |
Auth Status values: Connected, Authorized, Requires Auth, Disabled, Connection Error, Not checked, Probing…
Outputs
| Output | Description |
|---|---|
| Tools | All tools from enabled MCP servers, ready to connect to an Agent’s agent_tools input. |
Limitations
- Public HTTP endpoints only — Each server must be reachable at the URL you provide.
- Authorization required — Servers that need OAuth must be authorized before the flow can use their tools.
- Duplicate tool names — If multiple servers expose tools with the same name, only one is kept.
Collaborations
Lets an Agent work with Outlook — reading email, sending messages, and managing calendar events.
Note
All calendar and availability times use UTC. When scheduling meetings or checking availability, use UTC datetimes (e.g.,
2026-06-05T14:00:00).
Use in a flow
- Add a Collaborations node to the canvas.
- Set Platform to Outlook.
- Connect the Toolset output to agent_tools on your Agent.
- Run the flow while signed in with Microsoft. Leave Access Token (Optional) empty unless you need a manual override.
Collaborations (Toolset) ──► Agent (agent_tools)
What the Agent can do
Once connected, the Agent can: read inbox, send email, read a specific email, view calendar events, book a meeting, cancel a meeting, check availability, and get current time (UTC).
Parameters — General
| Parameter | Default | Hidden | Description |
|---|---|---|---|
| Platform | Outlook | No | Collaboration platform. Currently supports Outlook only. |
| Access Token (Optional) | — | Yes | Leave empty to use your signed-in Microsoft account. Only fill in to override authentication. |
Parameters — Email
| Parameter | Default | Hidden | Description |
|---|---|---|---|
| Email Filter | — | Yes | Filter which emails to list (e.g., unread only or from a specific sender). |
| Email Order By | receivedDateTime desc | Yes | How to sort listed emails. |
| Skip Count | 0 | Yes | Number of emails to skip when paginating. |
| Max Results | 10 | Yes | Maximum number of emails to return. |
| To Recipients | — | No | Comma-separated email addresses to send to. |
| Subject | — | No | Email subject line. |
| Body | — | No | Email body content. HTML is supported. |
| CC Recipients | — | Yes | Comma-separated CC addresses. |
| BCC Recipients | — | Yes | Comma-separated BCC addresses. |
| Email ID | — | No | ID of a specific email to retrieve. |
Parameters — Calendar
| Parameter | Default | Hidden | Description |
|---|---|---|---|
| Start Date | — | No | Start of the calendar range in UTC (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS). |
| Number of Days | 7 | No | How many days of events to fetch from the start date. |
| Meeting Subject | — | No | Title of the meeting. |
| Meeting Start Time | — | No | Meeting start in UTC (ISO format). |
| Meeting End Time | — | No | Meeting end in UTC (ISO format). Must be after the start time. |
| Attendees | — | No | Comma-separated attendee email addresses. |
| Is Online Meeting | false | Yes | When enabled, creates an online meeting link (e.g., Teams). |
| User Emails | — | No | Comma-separated emails to check availability for. |
| Availability Start Time | — | No | Start of the availability window in UTC. |
| Availability End Time | — | No | End of the availability window in UTC. |
| Time Interval (minutes) | 30 | Yes | Granularity of the free/busy schedule in minutes. |
Outputs
Connect Toolset to the Agent’s agent_tools input. Individual action outputs (Inbox Emails, Sent Email, Calendar Events, etc.) are also available if you want to wire specific actions directly in the flow.
Limitations
- Outlook only — Platform currently supports Outlook.
- UTC times — All calendar and availability fields expect UTC datetimes.
- Microsoft sign-in required — The flow must run with a signed-in Microsoft account, unless you provide an access token override.