---
title: "MCP — Tools for Fast Line Pro"
description: "How to give your Fast Line Pro agent tools — scenario sections the agent calls during the dialogue to perform actions and return real data to the customer."
---

# MCP Overview

> **This article is about MCP tools in scenarios for Fast Line Pro.** To connect an external AI assistant (Cursor) to your **ConnectiveOne instance** via `/mcp/token`, see [ConnectiveOne instance MCP](/en/learn/mcp/instance-mcp-overview.md) and [how to get the MCP token](/en/settings/how-to/get-mcp-instance-token.md).

**MCP is what gives your Fast Line Pro agent "hands".** Instead of only answering from the knowledge base, the agent can call scenario sections as tools: check order status, look up bonus balance, query CRM, create a ticket. The customer gets real data right in the dialogue, not just text.

<video src="https://storage.static.kwizbot.io/connectiveone-docs/Supercharge_Your_AI_Agent.mp4" controls width="100%"></video>

---

## Who This Is For

- **Integrators and configurators** — you set up Fast Line Pro and bot scenarios; you want the agent to do more than answer — to check, look up, create tickets.
- **Support and product** — you want the first line to close more requests on its own: the agent pulls order status, balance, availability — and the customer doesn't have to wait for an operator.

---

## How It Works

**MCP (Model Context Protocol)** is the way to turn scenario sections into tools for the agent.

You build a section that does one thing: e.g. "check order status" or "get bonus balance". At the section entry you add an **MCP Tool** trigger and describe what goes in and what comes out (Input Schema, Return Schema). The platform exposes that section to the agent as a tool. During the conversation, the agent decides when to call which tool: passes the order number, client id — and gets the result. All the logic lives in your scenario; the agent just calls and plugs the result into its reply.

**Without MCP** — the agent only answers from the knowledge base. **With MCP** — it answers and acts, gives the customer real data.

---

## Why It Matters

- **Fewer handoffs to operators** — the agent closes requests about status, balance, availability, ticket creation on its own.
- **Real data in the dialogue** — the customer doesn't hear "contact support"; they get order status, bonus balance, CRM checks right in the chat.
- **No duplication** — the same section can work in the bot (e.g. "My order" button) and as an MCP tool for the agent.
- **You stay in control** — you decide which tools the agent has and what each does; everything stays in your scenario.

---

## Important

- **Fast Line Pro is required** — MCP tools are used by the Fast Line Pro agent during the dialogue; this is not a separate product.
- **Each tool is a scenario section** with an MCP Tool trigger; you write the result to a constant so the platform can return it to the agent.
- **Setup** — you create MCP Tool sections in Scenario Builder and connect them to the Fast Line Pro agent. Your administrator or integrator can walk you through the steps.

---

## Next Steps

- **[Fast Line Pro Overview](/en/learn/fastlinepro/fastlinepro-overview.md)** — how Fast Line Pro works, knowledge base, agents; MCP adds tools on top of that.
- **[Processes and Scenarios — Scenario Builder](/en/learn/scenario-builder/processes-and-scenarios.md)** — overview of scenarios and sections in ConnectiveOne.
- **[Integrator Overview](/en/learn/implementer/implementer-overview.md)** — full guide for integrators, including scenarios and Fast Line Pro.