Integrations » Automations » MCP
MCP
Extend Bonnie with your own tools, systems, and business logic.
Model Context Protocol (MCP) is an open standard that lets developers expose callable tools over a lightweight API. It’s the fastest way to connect Bonnie to any system, without waiting for a native integration.
Bonnie acts as the MCP client. Connect your own MCP server and Bonnie discovers your tools automatically, calling them live during voice and WhatsApp conversations. Whether that’s a CRM lookup, a custom booking system, a loyalty check, or any other business logic, your tools become part of Bonnie’s brain.
Supported features
- Connect any system via a lightweight MCP server
- Tools called live during voice and WhatsApp conversations
- Scope tools by call state and channel
- Pre-call setup tools that load customer context before the conversation starts
- Structured responses fed directly into Bonnie’s conversation flow
- Full developer docs and a Python example server included
Integration details
WEBSITE
LOCATIONS OPERATED IN
- Operates globally
Explore other integrations
See what else Bonnie connects to.
WHO IS THIS FOR?
Built for developers who want to extend Bonnie with their own tools and systems.
Whether you build on a custom CRM, proprietary system, or any other tool, Bonnie calls it live during every conversation
Frequently asked questions
Everything you need to know about Bonnie. And more.
What is the Bonnie MCP integration and who is it for?
The Bonnie MCP integration is built for developers and technical teams who want to connect Bonnie to custom systems, third-party platforms, or proprietary business logic. If you have a system Bonnie doesn’t natively support, MCP is how you build the bridge.
How does it work?
Bonnie acts as the MCP client. You build a lightweight MCP server that exposes callable tools via JSON-RPC. At the start of every call or WhatsApp conversation, Bonnie discovers your tools automatically and invokes the right one at the right moment.
What kinds of tools can I expose to Bonnie?
Anything your business needs. Common examples include CRM lookups, custom reservation systems, loyalty checks, payment actions, delivery status, or any other business logic you want Bonnie to execute during a conversation.
Can I scope tools to specific channels or call states?
Yes. Tools can be scoped to phone, WhatsApp, or both, and to specific call states: setup, in-progress, or completed. This means the right tool is only available at the right moment in the conversation.
Can Bonnie load customer context before a call starts?
Yes. Tools scoped to the setup state are executed automatically before the conversation begins. They can return prompt variables, such as a caller’s name or account details, which Bonnie uses to personalise the conversation from the first word.
Is there an example server to get started?
Yes. A fully working Python example server is included in the documentation, covering tools like CRM lookups, structured responses, channel scoping, and pre-call setup. Full docs are available via the link on the top of this page.