External Integrations

Fluent supports external MPC servers and offers a catalog of 7,000 servers available.

Supported services or apps include Notion, Gmail, Slack, Asana, Obsidian, Telegram, or any other MCP compatible server.

External integrations currently require advanced knowledge and configuration. However, Fluent aims to simplify the process as much as possible.

Catalog

The easiest path to find a necessary integration is the catalog.

Open Settings → Integrations, click Add Integration, search for the server you want, and add it from there. Fluent can prefill much of the configuration for catalog integrations, which makes setup faster.

You can also click the "Instructions" button to open the GitHub repository webpage of that integration for setup & configuration details.

Manual Setup

Use Configure Manually when you already know the server details.

Fluent supports:

• Stdio servers
• HTTP
• SSE
• OpenAPI, which is currently more experimental

Manual setup usually requires one of these:

• Command and arguments
• Server URL or run command with arguments
• Environment variables
• Tokens or credentials

Use Allow Insecure SSL only for trusted local or internal endpoints that require it.

Connected State

After saving the integration, Fluent connects to the server and discovers the tools it exposes.

If the connection succeeds, you can:

• Review the tool list
• Disable tools you do not want
• Set approval behavior per tool

If it fails, Fluent shows connection status, an error message, and logs. Check those first before changing the settings.

Local Servers

If you're using local process servers, Fluent spawns them as child processes and keeps control over them.

If the server is launched through npx, uvx, or another local runtime (e.g. docker), make sure that runtime is installed and available in your shell environment. Most local connection failures come from:

• Wrong command
• Wrong arguments
• Missing environment variables
• Missing runtime

When To Use Them

Use an external integration when the workflow depends on a third-party service or app.

If the same task is already covered by a built-in integration, use the built-in one first. Setup is usually shorter and troubleshooting is simpler.