Connect an AI assistant with MCP

On this page

An assistant that supports the Model Context Protocol (MCP), such as Claude, ChatGPT, Cursor or Claude Code, can work in your space through the maxclicks MCP server. You ask it in plain language, and it calls the same API your integrations use: as you, in one workspace, with the permissions you granted when you connected it.

For example, a coffee brand asks: "How many contacts are in the Lapsed buyers segment, and how did our last broadcast to them perform?" The assistant counts the segment, finds the broadcast and reads its metrics, then answers with the numbers. Asking it to send something works the same way, and the send is real.

What an assistant can do in your space

The server gives the assistant tools for most of what the Public API covers. Setup that you author in the app stays read only.

Area	What the assistant can do
Contacts and objects	Look up, create, update and delete records in a schema, and read a contact’s audit trail.
Events	Fire one event or a batch, and list past events of an event schema.
Segments	List segments, count them, list their contacts, delete them, and create one from a plain description.
Sending	Send a prepared template to a contact, and change, schedule or send a broadcast drafted in the app, then read its runs and metrics.
Workflows	List workflows and runs, pause and resume a workflow, and start a workflow that has an incoming webhook trigger.
Webhooks	Create, update, delete and rotate the secret of a webhook.
Suppressions	List suppressions, and add or remove manual and legal ones. Needs Admin.
Setup	Read schemas, attributes, templates, domains, senders and topics.

An assistant cannot create or edit schemas, attributes, template or broadcast content, domains, senders or topics, and it cannot create a broadcast or build and publish a workflow. Those stay in the app, and the assistant reads what you built there.

Connect your assistant

Add the maxclicks server to your assistant
Open your assistant's settings for MCP servers (some apps call them connectors) and add a remote server with the address https://mcp.maxclicks.ai/mcp. If the app asks how to authenticate, choose OAuth or sign in.
In Claude Code, run this in a terminal, then type /mcp in Claude Code, select the server and authenticate:
```
claude mcp add --transport http maxclicks https://mcp.maxclicks.ai/mcp
```
In Cursor, add the server to .cursor/mcp.json, reload the window and sign in when Cursor asks:
```
{
  "mcpServers": {
    "maxclicks": { "url": "https://mcp.maxclicks.ai/mcp" }
  }
}
```
Sign in to maxclicks
The assistant opens maxclicks in your browser. Sign in if you are not signed in already. Finish in the browser tab the assistant opened, and keep the assistant open while you do.
Check who is asking
The page names the app as it describes itself and marks it Not verified, because any app can claim any name. Some apps also show Details from: the website that published the app's name and where it may return. Check Returns to: it shows the website that receives the connection, or An app running on this computer or An app installed on this device. For an app on your device, continue only if you started the connection from that app just now.
Choose the workspace and permissions
Under Workspace, click the workspace the assistant should work in. Only workspaces where you hold the Write permission appear. Under Permissions, keep or clear Read, Write and Admin. The page offers only what the app asked for and what your role holds in that workspace.
Allow access
Click Allow access. Your browser returns to the app, which finishes connecting on its own. To stop instead, click Deny: the request closes and nothing is connected.

The maxclicks consent page showing the app name with a Not verified badge, the Returns to address, a list of workspaces, and Read and Write permission checkboxes above the Deny and Allow access buttons

Before you ask for a change, ask the assistant "Which maxclicks workspace are you connected to?" It reports the workspace and your role, which catches a connection to the wrong workspace before anything is written.

Choose what the assistant can do

A connection carries the permissions you checked. It never carries more than your own role: if an admin later removes a permission from your role, the connection loses it too.

Permission	What the assistant can do with it
Read	See records, events, segments, templates, campaigns, workflows and sending setup.
Write	Create and change records, fire events, send templates and broadcasts, and run workflows.
Admin	Add and remove email suppressions.

Assistants ask for Read and Write unless they need more. Clear Write when the assistant only reports on your data. When it tries something the connection was not granted, it receives an error saying the connection was not granted that permission. Connect again and check it, or ask an admin for a role that has it.

Disconnect an assistant

Every connection is listed under Settings → Developers → API keys, named after the app, with a code such as OAuth · claude.ai in the Code column.

Open your API keys
Open Settings → Developers and select the API keys tab.
Delete the connection
Find the row with the app's name. Click the × button at the end of the row (its tooltip reads Delete API key), then confirm with Delete API key. The app loses access at once.

The tab lists the API keys and connections you created. To reconnect, connect the assistant again from the app.

A connection keeps working while the app uses it: the app renews its access every hour on its own. When a connection goes unused for 30 days, it expires and disappears from the list, and the app asks you to sign in again.

One connection covers one workspace. To work in a second workspace, add the server to your assistant again under another name and choose that workspace when you connect.

Use an API key instead

An assistant that cannot sign in can use a workspace API key. On the API keys tab, click Create API key, name it, and copy the key: it is shown once. Configure the assistant to send it as Authorization: Bearer followed by the key. Store the key in the assistant's secret settings, never in a prompt or a shared file.

A key acts with your full role in its workspace, without the permission choices of a connection, so prefer signing in when the assistant supports it. The MCP server reference covers a local setup that reads the key from your computer, and API authentication covers both credentials in detail.

Fix a connection that fails

What you see	What to do
This request is no longer open	The request waited more than 10 minutes, or was already answered. Start connecting again from the app.
This app is not registered, or its registration expired	Remove the maxclicks server in the app, add it again, and retry.
You need "write" access to a workspace to connect an app	Ask a workspace admin for a role that can edit, then connect again.
The assistant says the connection was not granted a permission	Connect again and check that permission, or ask an admin for a role that has it.
The assistant can no longer reach maxclicks	The connection was deleted, or expired after 30 days unused. Connect again.

See invite members and set permissions for what each role can do, and manage suppressions before you give an assistant Admin.

Frequently asked questions

Does the assistant see my maxclicks password?

No. You sign in on maxclicks itself. The app receives only an access token for the workspace and permissions you chose.

What does Not verified mean?

maxclicks cannot confirm who made the app, so the name is the app’s own claim. The Returns to address is the reliable part: it is where the connection is delivered. When the page also shows Details from, that website published the name.

Does an assistant cost anything?

The assistant’s requests count like your own API use. Creating a segment from a description runs AI and uses credits, and email the assistant sends counts toward your sending like any other email.

Can I connect the same assistant to two workspaces?

Yes. Each connection covers one workspace, so connect once per workspace. Each appears separately on the API keys tab.