ConnectiveOne instance MCP
Instance MCP lets an external AI assistant work with your ConnectiveOne instance: view bots, users, chats, statistics, scenario settings, and more. You get the connection token on the MCP Token Configuration page (/mcp/token) in the ConnectiveOne web UI.
Do not confuse with Fast Line Pro MCP. The MCP overview for Fast Line Pro describes something else: scenario sections as tools for the AI agent during a customer dialogue. Here we mean connecting your instance to an external editor or assistant (usually Cursor).
Who this is for
- Administrators and integrators — quickly pull instance data, verify settings, or analyze configuration through an AI assistant.
- Implementation teams — connect Cursor or another MCP client to a specific customer instance without manually wiring the integration.
How it works
- An authorized user opens MCP Token Configuration in ConnectiveOne.
- The system generates an authentication token (valid for about 30 days) and a ready-made Cursor configuration block.
- You paste the configuration into your MCP client (e.g. Cursor).
- The AI assistant talks to the ConnectiveOne MCP server, which acts on your behalf within your user permissions.
Which actions are available depends on the preset (tool mode) in the generated configuration. By default the page uses the analysis preset — mostly read-only views and analytics.
Access rights
A token can be obtained by:
- root users (full administrator);
- users whose role has the MCP Token module permission (access to the configuration page).
Without permission, the page shows an access-denied message and redirects to the home page.
Next steps
- How to get an MCP token for your instance — step-by-step: help menu,
/mcp/token, copying the Cursor configuration. - MCP — Tools for Fast Line Pro — scenario MCP tools for the Fast Line Pro agent.
- Configure roles — how to grant the MCP Token permission to a role when access should not be limited to root only.