MCP tools
Connect MCP servers so the realtime agent can look up and change data in your systems during a call.
A realtime agent works with your systems – a CRM, a billing system, an order database – through MCP servers (Model Context Protocol). Each server offers tools, for example find_contract or create_ticket. During the call, the model decides when to call a tool, based on the tool's description and your prompt.
Connect an MCP server
Click Agent in the left column, then + MCP server below Identity.
In Connection, enter the URL of the server.
If the server needs credentials, turn on Authentication, choose API Key, Bearer or Basic and enter the Token.
Click Connect. The MCP tools of the server appear.
Turn on Enable MCP server and choose the tools the agent may use.
The model provider calls the MCP server directly, so the server must be reachable from the internet. (The choice between Cloud and Local exists only in the AI node of a Digital Agent.)

A server – and the same server URL – can be added only once.
MCP servers in skills
Each skill has its own MCP servers card. A skill can use only servers and tools that are configured on the agent. Tools enabled for the whole agent are available in every skill. If an option cannot be changed in a skill, see Why aren't some MCP server options configurable? in the editor.
Built-in behaviour
Ending the call – the agent can hang up by itself after saying goodbye. Tell it in the prompt when the conversation is over.
An MCP tool can also end a phone call after the agent's next answer: when the tool result carries
ai.borndigital/hangup_after_replyset totruein its_meta, the agent says its reply to the tool output in full and then hangs up. Use it for closings that must be said word for word. If the caller speaks again before the end, the hang-up is cancelled.
Switching skills – the agent switches between skills on its own.
No transfer to an operator – a realtime agent cannot transfer the call. If callers must be able to reach a person, give them a phone number in the prompt, or use a Digital Agent with a Transfer or Redirect node.
Last updated
Was this helpful?