How to get an MCP token for your ConnectiveOne instance?

If you want an AI assistant (for example in Cursor) to work with your ConnectiveOne instance — view bots, users, chats, or statistics — you first need a token from the MCP Token Configuration page. Below is how to get it and where to paste it.

When you need this

• You are connecting Cursor to a ConnectiveOne instance for the first time.
• Your previous token expired — the AI assistant shows an authorization error.
• You need to grant token page access to a user who is not root (via the MCP Token role permission).

What to know

• MCP Token Configuration — the ConnectiveOne page at /mcp/token where the token and a ready-made Cursor configuration are generated.
• Authentication token — a long-lived access key for the MCP client. It is valid for about 30 days; after that, generate a new one on the same page.
• Cursor Configuration — a ready JSON block on the page; copy it in one click and paste it into Cursor MCP settings.
• Preset — the tool set mode (the page shows a preset table). The generated configuration uses analysis by default (mostly read-only views and analytics).

For how instance MCP differs from MCP tools in Fast Line Pro, see the instance MCP overview.

Before you start

• You are logged in to ConnectiveOne (web UI / Constructor).
• You have the root role or the MCP Token module permission on your role.
• Cursor or another MCP client is installed that supports URL + header configuration as in the copied JSON.

If you lack the MCP Token permission, ask an administrator to enable it in role settings (the MCP Token module in permissions).

Steps

Option 1 — via the help menu

1. In the top bar, click the help icon (?).
2. Select MCP Token Configuration.
3. If you are not logged in, the sign-in page opens; after a successful login you are redirected to the token page.

Option 2 — direct link

• If you are already logged in, open in the browser:
  https://<your-connectiveone-domain>/mcp/token
• If you are not logged in, open:
  https://<your-connectiveone-domain>/login?mcp=true
  — after sign-in (email/password or Google SSO) the MCP Token Configuration page opens.

Copy the token or configuration

On MCP Token Configuration:

1. Under Authentication Token, click Copy Token if you only need the key.
2. Or click Copy Configuration under Cursor Configuration — this is easiest for Cursor: the full JSON with server URL, instance address, and token is copied.
3. Note Token expires — record the date so you can renew the token in time.

Add the configuration to Cursor

1. Open Cursor.
2. Open MCP settings:
   • per project — file .cursor/mcp.json, or
   • globally — Preferences: Open User Settings (JSON) (Cmd/Ctrl + Shift + P).
3. Paste the copied JSON (or add the connectiveone-engine block to existing mcpServers).
4. Save the file and restart Cursor so the connection applies.

Change the preset if needed

The token page lists presets (minimal, analysis, setup, scenario, full). For a different tool set, after pasting the configuration into Cursor change the preset value in the corresponding header according to the table on the page. Preset full exposes all tools; actions may be irreversible — use only if you understand the risks.

What happens next

After restarting Cursor, the AI assistant can call ConnectiveOne tools for your instance — within your user permissions and the chosen preset.

How to verify it works

• In Cursor, the connectiveone-engine MCP server appears without an authorization error.
• Ask the assistant for instance data (for example, a list of bots) — the answer should be based on real data, not an access error.

Troubleshooting

Related

• ConnectiveOne instance MCP — overview
• MCP — Tools for Fast Line Pro
• Configure roles