Setup & Usage
MCP is the tool layer behind Integrations in Fluent.
It lets Fluent do more than generate text. With MCP enabled, Fluent can search the web, fetch pages, read files, work with apps such as Notes or Calendar, create reminders, use Memory tools, control the browser, or run shell commands.
What It Is
In Fluent, MCP is not a separate UI. It is configured in Settings → Integrations.
Enable an integration, and Fluent exposes its tools to the model. Disable it, and those tools are not available. This keeps MCP tied to concrete integrations instead of turning it into a separate system the user has to manage by hand.
Start
Recommended first setup:
- Open Settings → Integrations
- Enable one built-in integration or click Add Integration
- Open the integration settings
- Leave only the tools you actually need enabled
- Set approval behavior for tools that write or delete
- Test with a small request
Good first integrations:
- Finder for file workflows
- Web Search for research
- Reminders or Calendar for creation workflows
Built-In
Fluent includes built-in integrations for:
- Finder
- Reminders
- Notes
- Calendar
- Web Search
- Web Fetch
- Browser Automation
- YouTube
- Shell
- Location
- Memory
Built-in integrations are enabled directly from Settings → Integrations.
After enabling one, open its settings and review:
- Which tools are enabled
- Which tools ask for approval
- Whether you need any custom tools in that integration
Each integration is configured separately. Open its settings to view the available tools, disable the ones you do not want, and set approval behavior where needed.
Fluent asks for macOS permissions only when that integration needs them.
Approvals
Approval settings matter most for tools that can write, edit, remove, or trigger actions outside Fluent.
Typical pattern:
- Allow read-only tools more freely
- Keep write or destructive tools behind approval
This is configured per tool, not only per integration.
External
For external MCP servers, click Add Integration.
Use the catalog if the server is listed. Use Configure Manually if you already know the server details.
Manual setup usually requires:
- Command and arguments for local process servers
- URL for remote servers
- Environment variables or credentials
After saving, Fluent connects to the server and discovers the tools it exposes.
Custom Tools
Built-in integrations can be extended with custom tools.
Custom tools are useful when you want a narrow, repeatable operation instead of relying on the model to improvise each step. A custom tool can run:
- JavaScript in the browser
- AppleScript on macOS
- Shell script in Terminal
You can also define parameters and have them injected into the tool automatically.
Usage
Use normal prompts. You do not need a separate MCP syntax for everyday work.
Examples:
- "Turn these meeting notes into reminders"
- "Research these competitors and list the important differences"
- "Read this folder and tell me what changed"
If the workflow repeats, turn it into an Action. If it should run in the background, schedule that Action.
Context still matters. Tool access is most useful when the request also includes the right page, selection, file, or Memory group.
Tool Set
A smaller tool set usually works better than a larger one.
Disable tools you do not need. Keep destructive tools behind approval unless you trust the workflow completely. This makes MCP behavior easier to predict and easier to troubleshoot.
Why Use MCP
Use MCP when the task should read, fetch, search, create, update, or automate something.
Without MCP, Actions stay prompt-based. With MCP, the same action can inspect a page, search the web, read a folder, create a reminder, update a note, or search Memory before it answers.
Start with one integration, one small task, and one approval setting you understand. Expand only after that works.