---
title: "Release 5.7.2"
description: "MCP servers for Fast Line Pro agents; improved user email and phone validation; Help menu Write for support opens Client Portal."
---

# Release 5.7.2

## What Changed

- **Fast Line Pro:** add **MCP servers** from the agent **Tools catalog**, check **connection status**, and attach external tools to agents.
- **Settings — Users:** **international phone numbers** and **email** validate correctly on create; **editing existing users** no longer fails when the login field is read-only.
- **Help menu:** **Write for support** opens the **Client Portal** instead of the previous support desk page.
- **Settings — Quality Assurance:** the heartbeat timeout label now says **AI engine** instead of an internal product name.

## How It Changed

**Before:** Fast Line Pro agents could use tools from the built-in catalog only — there was no way to register your own MCP server from the agent card. User creation required phone numbers in a strict `+XXXXXXXXX` format; saving an existing user could show a validation error on a disabled email field.

The Help menu support link pointed to an external service desk.

**Now:** Integrators open **Tools catalog → Add MCP server**, fill in URL and **Server Identifier**, and see a **status dot** plus **Check connection** for each MCP server. New users accept common international phone formats; numbers are normalized on save. Existing user profiles save without re-validating a locked login. **Write for support** opens the Client Portal in a new tab.

## Why It Matters

Integrators connect external MCP services to AI agents inside ConnectiveOne. Administrators onboard operators with phone numbers from any country without format errors. Everyone reaches support through one Client Portal entry point.

## Product areas in detail

### Fast Line Pro — MCP tools

**New**

- **Add MCP server** in the **Tools catalog** — name, server URL, **Server Identifier** (lowercase, up to 24 characters), timeouts, optional HTTP headers.
- Dedicated **MCP** tab lists servers scoped to your instance.
- **Connection status** dot (green = connected, grey = not connected) and **Check connection** button with a result message above the list.
- After a successful add, server tools appear in the catalog and can be attached to the agent like any other tool — then **Publish**.

**Improved**

- If the AI engine version cannot store custom HTTP headers, the form shows a **warning** and suggests token-based authorization in the server URL instead.

### Help menu — Write for support

**Changed**

- **Help (?) → Write for support** opens **Client Portal** in a new tab.
- Menu label stays localized; the destination URL is the same for all interface languages.

### Settings — Users

**Improved**

- **Email / phone** field accepts valid **international phone numbers** (with or without `+`, spaces, or brackets) and standard **email** addresses.
- On **create**, phone logins are saved in a normalized format without spaces or separators.
- On **edit**, a read-only login field is not re-validated — you can save other profile changes without a false error.
- Validation hints show **locale-appropriate examples** instead of a single rigid format.
- User drawer closes with **Escape**; width adapts on smaller screens.

### Settings — Quality Assurance

**Improved**

- On **Menu → Settings → Instance settings → Quality Assurance**, the **AI engine heartbeat timeout (minutes)** label and hint use **AI engine** wording instead of an internal product name (English and German).

## Please note

- **MCP servers** are visible only on the instance where they were added; other instances do not share your MCP catalog.
- **Custom HTTP headers** for MCP require a recent AI engine version — if headers are unsupported, use a token in the server URL as described in the warning.
- If an MCP server requires **OAuth** on the provider side, tools appear only after authorization — use the status dot and **Check connection** to confirm.
- After adding MCP tools to an agent, click **Publish** so live conversations use the updated configuration.
- **Client Portal** for support opens at a fixed address; to connect the portal to your instance, an administrator can set the client portal URL in **Menu → Settings → Instance settings** (see [Configure instance settings](../settings/how-to/configure-instance.md)).
- **Phone normalization** applies when **creating** a user; existing logins are not reformatted on edit.

## Related documentation

- [Connect and configure agent tools](../fastlinepro/how-to/configure-agent-tools.md)
- [Create agent](../fastlinepro/how-to/create-agent.md)
- [Fast Line Pro integrator hub](../fastlinepro/integrator-hub.md)
- [Create and edit users](../settings/how-to/create-edit-users.md)
- [View users list](../settings/how-to/view-users.md)
- [Configure instance settings](../settings/how-to/configure-instance.md)