Model Context Protocol
Connect BlueSales to Claude, or any assistant that speaks MCP, and it can do the work instead of explaining it — set up an agent, buy a number, load a lead list, place calls, read the transcripts back to you.
https://bluesales.ai/mcp
In practice
The assistant works through the same steps you would in the dashboard, in the right order, and stops to ask before anything costs you money. When it finishes, the agent is live on a real phone number.
54 tools, covering everything the dashboard does and a little it doesn’t.
Set up a receptionist for my plumbing company and put it on a Denver number.
I found four Denver numbers. +1 303 555 0142 is the cleanest — want me to buy it? It bills monthly.
Yes, and use a female voice.
Front Desk is live on +1 303 555 0142. Want me to ring your mobile so you can hear it?
Coverage
Everything you can do in BlueSales, an assistant can do too — including the parts that only ever existed as buttons.
Blues
Create an agent, write its script and identity, wire it to a number, change how it handles a call, retire it.
Knowledge
Build a knowledge base from a website, pasted text or uploaded files — then ask it questions to check what your agent actually knows.
Phone numbers
Search what is available, buy a number, bring your own from Twilio, assign it to an agent, release it.
Leads
Build lead lists and import thousands of leads in one go, ready for an outbound campaign.
Calls
Place a call, read the transcript and summary, pull the recording, and get performance broken down by agent and by day.
Calendar
Read real availability from a connected Google or Outlook calendar and book appointments on it.
Compliance
Read and change how calls are handled under GDPR, CPRA and HIPAA.
Account
Plan, usage balance, and an inventory of everything the account holds.
Setup
One endpoint, whichever client you use. No package to install, nothing to run on your machine.
Add it as a custom connector and sign in with your BlueSales account. Nothing to paste, nothing to rotate.
Control
Handing an assistant the keys to a phone system is only reasonable if the keys open exactly what you meant them to.
Each key carries its own permissions. A read-only key produces a read-only server — the tools that spend money are not merely blocked, the assistant never sees them.
Buying a number, dialling a person and writing to a calendar are marked as what they are. The assistant is instructed to name the exact number or record and ask you first.
Connectors authorise through a normal browser sign-in with OAuth and PKCE. No key ever touches the chat window.
Every connected client is listed in your dashboard with when it last ran. Disconnect one and its access dies immediately.
The Model Context Protocol is an open standard for giving an AI assistant real tools instead of a text box. BlueSales runs an MCP server, so an assistant that speaks the protocol can operate your account directly rather than telling you which buttons to press.
Same platform, same permissions, different shape. The REST API is for code you write. The MCP server is the same capabilities described so an AI assistant can pick the right one on its own — and it covers a few things the REST API does not, like buying a phone number or querying a knowledge base.
Buying a phone number and placing a call cost money, and those tools say so in the description the assistant reads, which is what makes it confirm with you first. If you would rather remove the possibility entirely, connect it with a key that has no write permissions.
Any MCP client that speaks streamable HTTP. Claude works over OAuth with no key at all; Claude Code, Cursor, Windsurf and custom agents connect with an API key header.
Nothing on top of your plan. MCP access is included with the Business and Agency plans, the same ones that include API access.
Included with the Business and Agency plans. Connect it in a minute, disconnect it in a click.
Get started free