Documentation
УКР
How-to
Article MarkdownReport an error

How to bind a Scenario MCP Tool section to a Fast Line Pro agent?

An MCP Tool section from Scenario Builder can become a Fast Line Pro agent tool: the agent calls the section during a dialog and receives the result defined in Return Schema. You can bind from Scenario Builder or from the agent card — the state stays in sync in both places.

When you need this

  • A Fast Line Pro agent must run logic you already built in a scenario MCP Tool section.
  • You need to give one agent several MCP Tool sections without manually copying MCP URLs.
  • While creating a new MCP Tool section, you want to pick agents immediately.

What to know

  • Create an MCP Tool section with trigger MCP Tool and fill in Return Schema (the description helps the agent decide when to call the tool).
  • After binding, the tool appears in Tools on the agent card, but dialog behavior changes only after Publish.
  • External MCP servers added via Add MCP server are not replaced by this flow — they remain separate.
  • If Connect to Fast Line Pro or Add MCP Tool from scenario is missing, ask a root administrator to enable Scenario MCP ↔ FLP agent binding under Settings → Instance settings (platform feature toggles).

Before you start

Option A — from Scenario Builder

  1. Open the scenario in Scenario Builder and select the section with the start node.
  2. In Node Inspector, set Trigger type to MCP Tool.
  3. Fill Input Schema and Return Schema (see Configure MCP Tool for the start node).
  4. Save the section or scenario — until then, agent selection stays disabled.
  5. In Connect to Fast Line Pro, pick one or more agents in Select agents.
  6. Save the scenario. If you see a warning that the section was saved but the tool was not added to agents, try selecting agents again.
  7. Open Fast Line Pro, open the agent card, and check Tools.
  8. Click Publish on the agent card.

Option B — from the Fast Line Pro agent card

  1. Open Fast Line Pro → Agents → the target agent.
  2. In Tools, click Add MCP Tool from scenario (next to the Tools catalog button).
  3. In the modal, find the section using search or the bot filter.
  4. Select the MCP Tool sections you need (already bound rows stay checked).
  5. Click Add selected tools.
  6. Click Publish on the agent card.

If the list is empty, create an MCP Tool section in Scenario Builder first (trigger MCP Tool).

What happens next

  • Selected agents show the tool under Tools; Scenario Builder shows the same agents under Connect to Fast Line Pro.
  • The platform creates the MCP connection for the scenario bot automatically — you do not need a separate MCP URL for Fast Line Pro.
  • Until you publish the agent, clients in dialogs keep the previous configuration.

How to verify

  • The tool appears under the agent Tools with the section name.
  • Scenario Builder Connect to Fast Line Pro lists the same agents.
  • After Publish, a test dialog via action_fastline_pro or another scenario can invoke the tool when the prompt and Return Schema description allow it.

Common situations

Situation What to do
No agents in the list Create an agent in Fast Line Pro, or bind later from the agent card.
Missing tool description warning Add a description in the section Return Schema.
MCP provider error Ensure the section is saved; retry binding. Contact your administrator if needed.
Tool removed after editing in FLP If you removed the tool manually from Tools, Scenario Builder reflects that — re-bind if needed.
Using your own AI agent?Install the open skill so your AI agent can work with current official ConnectiveOne documentation.Get the skillNeed support?Couldn’t find the answer or need help from the ConnectiveOne team? Create a request in Client Portal.Create a request