Connect an AI Assistant

You can connect an AI assistant such as Claude to Fluentos and ask it questions about your campaigns in plain language, instead of clicking through reports.

Once connected, you can ask things like:

• “Is my welcome popup set up correctly for all our languages?”
• “Which campaigns on our shop are performing worst this month?”
• “Why did this campaign stop getting impressions?”

What the assistant can read

• Names of your organisations, websites and campaigns
• Campaign setup - triggers, targeting rules, schedule, steps, the languages configured on your website, and how a campaign competes with your others for the screen
• Campaign analytics - impressions, clicks, submissions, goals and trends over time
• Campaign wording - the headings, button labels and field labels a visitor sees, and how completely each language is translated
• Integrations - which integration a campaign sends its form to, which fields it sends and how existing contacts are treated
• Custom code - JavaScript you added to buttons or to campaign events, when it is asked to review it. Do not keep keys or passwords in that code

The connector also offers this wiki’s campaign settings pages, such as Display Rules, as resources the assistant can read on demand, so a question about what a setting does is answered from the same pages you read here.

What it can never do

• Read form submissions or contact data. It can tell you how many people completed a form, never who they were or what they entered.
• Read your integration credentials. It sees which integration a campaign uses, never the API keys or passwords behind it.
• See your images. It reads the text inside a campaign, not the pictures.
• Change anything. The connection is read-only. It cannot edit, publish, pause or delete.

This applies to every organisation you are a member of. If you work across several client accounts, the assistant can read all of them. Check with a client before connecting on their behalf.

Connect it

The server address is the same everywhere:

https://mcp.fluentos.com/mcp

Whichever app you use, the connection finishes the same way: the app opens Fluentos in your browser, you sign in as normal, review what the app will be able to read, and select Allow access. If this is your first time in Fluentos you accept the terms first, then land on that approval screen. When it is done you are sent back to the app with the connection ready.

Menu names below are the ones the apps use at the time of writing. If yours looks different, look for “connectors”, “MCP servers” or “integrations” in its settings.

Claude (web and desktop)

1. Open Settings → Connectors and choose Add custom connector.
2. Give it a name such as Fluentos, enter the server address and confirm.
3. Select Connect and complete the sign-in in the browser tab that opens.

Team and Enterprise admins can add the connector once for the whole organisation under Admin settings → Connectors; each person still signs in to Fluentos with their own account.

ChatGPT

Custom connectors in ChatGPT need a plan that allows them and developer mode switched on.

1. Open Settings → Connectors → Advanced and turn on Developer mode.
2. Back under Connectors, choose Create and enter a name and the server address, with OAuth as the authentication.
3. Complete the sign-in, then enable the connector in a chat through the + menu.

Claude Code

Run in a terminal:

claude mcp add --transport http fluentos https://mcp.fluentos.com/mcp

Then start Claude Code, type /mcp, pick fluentos and choose Authenticate to complete the sign-in. Add --scope user to the command if you want the connection in every project rather than only the current one.

Cursor

1. Open Cursor Settings → Tools & MCP and choose Add new MCP server.
2. Name it fluentos, pick the URL type and enter the server address.
3. Select Login next to the server and complete the sign-in.

You can also add it by hand to .cursor/mcp.json in a project, or ~/.cursor/mcp.json for every project:

{
  "mcpServers": {
    "fluentos": {
      "url": "https://mcp.fluentos.com/mcp"
    }
  }
}

Visual Studio Code

1. Open the Command Palette and run MCP: Add Server.
2. Choose HTTP, enter the server address and name it fluentos.
3. Choose whether to add it for this workspace or globally, then pick Allow when VS Code asks to sign in.

Or add it to .vscode/mcp.json:

{
  "servers": {
    "fluentos": {
      "type": "http",
      "url": "https://mcp.fluentos.com/mcp"
    }
  }
}

Windsurf

Open Windsurf Settings → Cascade → MCP servers, choose Add server and enter the server address, or add it to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "fluentos": {
      "serverUrl": "https://mcp.fluentos.com/mcp"
    }
  }
}

Then select Login on the server entry to complete the sign-in.

Gemini CLI

Add it to ~/.gemini/settings.json:

{
  "mcpServers": {
    "fluentos": {
      "httpUrl": "https://mcp.fluentos.com/mcp"
    }
  }
}

Then run /mcp auth fluentos inside Gemini CLI to complete the sign-in.

Other apps

Any app that supports remote MCP servers with OAuth sign-in can connect using the same address. Apps that only accept a fixed API key or token cannot, since Fluentos never issues long-lived keys: every connection is tied to a sign-in you can see and revoke from your profile.

Caution

The approval screen shows where your data will be sent - for Claude that is claude.ai. Any app can call itself anything, so judge it by that address rather than the name. If you do not recognise it, cancel.

Note

Finish the connection in the same browser you started it in. A connection can only be completed by the browser that started it and the browser that approved it, so a link someone else sends you cannot connect their assistant to your account. Still, only approve a connection you started yourself.

What to ask

The connector ships with five ready-made tasks: audit a campaign setup, check localisation, review campaign performance, diagnose an underperforming campaign, and suggest how to improve one. In Claude, open the attachments menu in the message box, choose the Fluentos connector, and pick one. Other apps list them wherever they show a connector’s prompts.

Or ask in your own words. Two pages help:

• Prompt Library: questions to copy and adapt, from pre-publish checks to monthly summaries.
• Project Instructions: a few lines about your cookies, variables and naming, saved once, make every answer sharper.

Give a time range when you ask about performance. Without one, the numbers are lifetime totals.

Disconnect it

Go to Profile → Connected apps in Fluentos and select Disconnect. Access stops within a minute, and the assistant has to ask permission again.

The same page lists every app you have connected and when. If you see one you do not recognise, disconnect it.

Things worth knowing

Your data leaves Fluentos. The assistant’s provider receives whatever it reads and processes it on their systems. Fluentos never uses your data to train AI models; what the provider does with it is covered by your agreement with them.

Campaign names come from your own account. The assistant reads them as data, not instructions, but it is worth knowing that whatever your team types as a campaign name is what the assistant sees.

Every request is logged. Fluentos records which assistant read what and when, and keeps that record for three months, so support can reconstruct any access on your account.