MCP Servers
Configuring MCP servers for tool connectivity in workflows.
MCP (Model Context Protocol) servers provide tool connectivity for workflows. They allow Agent and Action nodes to interact with external services such as Slack, Telegram, Google Workspace, Notion, and more.
MCP server configurations are managed at the organization level on the Resources page (Resources > MCP Servers) and enabled per workspace. The number of configurations you can have depends on your plan.
Built-in Server Types
FlowTrux includes 13 built-in MCP server types:
| Server | Description | Required Configuration |
|---|---|---|
| YouTrack | Issue tracking integration. | baseUrl, apiKey |
| Telegram | Telegram Bot messaging. | botToken, chatId |
| Slack | Slack workspace messaging. | botToken, defaultChannel (optional) |
| Stocks | Financial market data (Polygon or Finnhub). | provider, apiKey |
| Google Workspace | Google Sheets, Gmail, Calendar, Drive. | Quick connect (just sign in with Google), or bring your own clientId + clientSecret (+ OAuth connection) |
| Files | File operations on your organization's built-in storage. | Automatic - uses your organization's file storage. |
| PDF document generation (markdown, reports, tables). | Automatic - uses your organization's file storage. | |
| SSH | Remote server command execution and file transfer. | host, username, privateKey or password (+ port optional) |
| Twilio | SMS, voice calls, WhatsApp messaging. | accountSid, authToken, fromNumber |
| Notion | Notion pages, databases, blocks, comments. | apiKey (integration token) |
| GitHub | GitHub issues, PRs, repos, Actions. | token (PAT), owner (optional) |
| Jira | Jira Cloud issues, projects, sprints, transitions. | baseUrl, email, apiToken |
| Wialon | Wialon Hosting / Local telematics: units, messages, geofences, reports, ACL. | hostUrl, token |
Adding an MCP Server
- Navigate to Resources > MCP Servers.
- Click Add Server.
- Select a built-in server type.
- Give the configuration a display name and fill in the required fields for that server type.
- Pick the workspaces where it should be available.
- Click Save.
All configuration values are encrypted before being stored.
You can create several configurations of the same server type with different names - for example, two Telegram configurations pointing at different bots, or a "Jira Production" and a "Jira Sandbox". Each configuration is enabled per workspace independently.
Remote MCP Servers
Besides the built-in types, you can connect a Remote MCP Server that you host yourself: provide the HTTPS URL and, optionally, authentication (bearer token or API key header). FlowTrux connects to your server over the network - it never runs your code. Availability of this option depends on the deployment configuration.
Google Workspace Setup
The Google Workspace server supports two connection methods:
Quick connect (recommended)
No Google Cloud setup needed: add a Google Workspace server, click Connect Google Account, and sign in on the Google consent screen. This uses FlowTrux's own Google app with a light permission scope.
Bring your own OAuth app
For full control over scopes and quotas:
- Create a project in Google Cloud Console.
- Enable the APIs you need: Sheets, Gmail, Calendar, Drive.
- Create OAuth 2.0 credentials (Web application type) with the redirect URI shown in the FlowTrux configuration dialog.
- In FlowTrux, add a Google Workspace MCP server with your Client ID and Client Secret.
- After saving, click Connect Google Account and authorize access.
Either way, the UI shows the connection status: a green "Connected" badge with the authorized email, or an amber "Not connected" indicator with a "Connect" button.
Enabling in Workspaces
MCP servers must be enabled per workspace. Either pick the workspaces when creating the configuration, or later:
- Open the workspace's settings (
/workspaces/<workspace>/settings). - Go to the Enabled resources tab.
- Under MCP Servers, check the configurations you want available.
- Save.
Only enabled servers appear in the editor - in the MCP Action node's server dropdown and in the Agent node's tools section. If none are enabled for the current workspace, the editor displays a warning.
Testing a Server
To verify a server is working correctly:
- Enable the server in a workspace.
- Create or open a workflow in that workspace.
- Add an MCP Action node.
- Open the node inspector and confirm the server appears in the server dropdown.
- Select the server and verify its tools are listed.