FlowTruxFlowTrux/Docs
Docssettings

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, file systems, and more.

MCP server configurations are managed at the organization level and assigned to specific workspaces.

Built-in Server Types

FlowTrux includes several built-in MCP server types:

ServerDescriptionRequired Configuration
YouTrackIssue tracking integration.baseUrl, apiKey
TelegramTelegram Bot messaging.botToken, chatId
SlackSlack workspace messaging.botToken, defaultChannel (optional)
FilesystemLocal file operations.outputDir, allowedDirs
StocksFinancial market data (Polygon or Finnhub).provider, apiKey
Google WorkspaceGoogle Sheets, Gmail, Calendar, Drive.clientId, clientSecret (+ OAuth connection)
FilesS3-based file storage operations.Automatically configured per workspace.
SSHRemote server command execution and file transfer.host, username, privateKey or password
TwilioSMS, voice calls, WhatsApp messaging.accountSid, authToken, fromNumber
PDFPDF document generation (markdown, reports, tables).Automatically configured per workspace.
NotionNotion pages, databases, blocks, comments.apiKey (integration token)
GitHubGitHub issues, PRs, repos, Actions.token (PAT), owner (optional)
JiraJira Cloud issues, projects, sprints, transitions.baseUrl, email, apiToken
WialonWialon Hosting / Local telematics: units, messages, geofences, reports, ACL.hostUrl, token

Adding an MCP Server

Built-in Servers

  1. Navigate to Settings > MCP Servers.
  2. Click Add Server.
  3. Select a built-in server type from the dropdown.
  4. Fill in the required configuration fields for that server type.
  5. Click Save.

External Servers

For MCP servers not included as built-in types:

  1. Navigate to Settings > MCP Servers.
  2. Click Add Server.
  3. Select External as the server type.
  4. Provide the command to run the server, arguments, and any environment variables.
  5. Click Save.

All configuration values are encrypted before being stored in the database.

Google Workspace Setup

The Google Workspace server requires an additional OAuth connection step:

  1. Create a project in Google Cloud Console.
  2. Enable the APIs you need: Sheets, Gmail, Calendar, Drive.
  3. Create OAuth 2.0 credentials (Web application type).
  4. Add the redirect URI: https://<your-domain>/api/auth/google-workspace/callback.
  5. In FlowTrux, add a Google Workspace MCP server with your Client ID and Client Secret.
  6. After saving, click Connect Google Account and authorize access on the Google consent screen.
  7. Assign the server to a workspace.

The UI shows the connection status: a green "Connected" badge with the authorized email, or an amber "Not connected" indicator with a "Connect" button.

Assigning to Workspaces

MCP servers are not available in any workspace by default. To assign them:

  1. Go to Settings > Workspaces.
  2. Click Edit on the target workspace.
  3. Under Allowed MCP Servers, check the servers you want to make available.
  4. Save.

Only assigned servers appear in the MCP Action node dropdown within the workflow editor. If no servers are assigned to the current workspace, the editor displays a warning message.

Testing a Server

To verify a server is working correctly:

  1. Assign the server to a workspace.
  2. Create or open a workflow in that workspace.
  3. Add an MCP Action node.
  4. Open the node inspector and confirm the server appears in the server dropdown.
  5. Select the server and verify its tools are listed.

Connection Pool

FlowTrux uses a workspace-scoped connection pool for MCP servers. Connections are reused across concurrent workflow executions within the same workspace. Idle connections are automatically cleaned up after 5 minutes. The pool supports a maximum of 50 entries.

← AI ProvidersKnowledge Bases→