How to Make Real Phone Calls from Claude (and Other AI Assistants) with MCP

Short answer: AI assistants like Claude can't dial a phone by themselves. You need to connect them to a phone-calling MCP server: a service that exposes "place a call", "buy a number" and "read the transcript" as tools the assistant can use. With the BlueSales MCP server:

• In Claude: add https://bluesales.ai/mcp as a custom connector and sign in.
• In Claude Code: run one claude mcp add command.

After that you can ask, "Call Sarah at 555-0142 and confirm her Thursday appointment," and a real AI voice agent places the call.

What MCP is, in one paragraph

The Model Context Protocol (MCP) is an open standard that lets AI assistants use external tools. An MCP server describes its tools, such as start_call or list_calls, and the assistant decides when to call them. A phone-calling MCP server gives your assistant the ability to act on the phone network, not just write text about it.

What you can do once it's connected

The BlueSales MCP server exposes the whole product, more than 50 tools, so your assistant can:

• Place outbound calls with an AI voice agent and read back the transcript, summary and recording.
• Set up an AI receptionist for your business: business profile, knowledge base, voice and phone number.
• Search for and buy phone numbers in any U.S. area code.
• Load leads and run outbound campaigns for reminders, follow-ups and appointment booking.
• Check calendar availability and book appointments on a connected Google or Outlook calendar.
• Report on calls: volume, outcomes and performance by agent and by day.
• Change compliance settings for calling windows, consent and recording.

Setup: Claude (claude.ai and Claude desktop)

1. In Claude, open Settings → Connectors → Add custom connector.
2. Paste the server URL: https://bluesales.ai/mcp
3. Click connect. A BlueSales sign-in window opens. Approve access with OAuth.
4. Start a new chat and ask: "What BlueSales tools do you have?"

No API key is pasted into the chat. Access uses a normal browser sign-in, and you can disconnect it at any time from Dashboard → API → AI Access.

Setup: Claude Code

Create an API key in Dashboard → API → API Keys, then run:

claude mcp add --transport http bluesales https://bluesales.ai/mcp \
  --header "X-API-Key: bsk_your_key_here"

The key's permissions decide which tools Claude Code can see. A read-only key produces a read-only server.

Setup: Cursor, Windsurf and other MCP clients

Any client that supports remote MCP servers over HTTP uses the same endpoint and an API key header:

{
  "bluesales": {
    "type": "http",
    "url": "https://bluesales.ai/mcp",
    "headers": { "X-API-Key": "bsk_your_key_here" }
  }
}

Example prompts

• "Set up a receptionist for my plumbing company in Denver and put it on a 303 number."
• "Call +1 512 555 0123 and remind them about tomorrow's 10am appointment. Tell me what they said."
• "Import this CSV of leads into a new list called 'October webinar' and call everyone who opted in."
• "Which calls last week asked about pricing but didn't book? Summarize them."
• "What times am I free on Friday? Book Jane Doe at 2pm for a consultation."

Safety: what stops the assistant from going rogue?

Giving an AI assistant a phone line is powerful, so guardrails matter:

• Confirmation before real-world actions. Tools that cost money or reach a person, such as buying a number, placing a call or writing to a calendar, say so in their description. The assistant is instructed to name the exact number or record and ask you first.
• Scoped permissions. Each API key carries its own permissions. Tools a key isn't allowed to use are hidden from the assistant entirely.
• Calling windows. Outbound calls outside an agent's configured calling hours are refused unless explicitly overridden.
• Revocable access. Every connected client is listed in your dashboard. Disconnect it and access ends immediately.

Outbound calls are still subject to calling laws. Read are AI phone calls legal? before calling anyone who hasn't asked to hear from you.

Other ways to give an AI phone abilities

• Build it yourself with a telephony provider and a realtime speech model. This gives you full control, but you'll be building call handling, voices, transcripts, compliance and billing from scratch.
• Voice-agent developer platforms with MCP servers. These are great for engineers building custom agents, but you still assemble the business logic around them.
• A business phone-agent platform like BlueSales. Agents, numbers, calendar booking, lead lists, compliance tooling and transcripts are already built, and the MCP server just lets your assistant drive them.

Frequently asked questions

Can Claude make phone calls?

Not on its own, but it can when connected to a phone-calling MCP server. Add a server such as BlueSales (https://bluesales.ai/mcp) as a custom connector in Claude, and Claude can place real calls through an AI voice agent and read you the transcript.

Which AI assistants can use the BlueSales MCP server?

Any MCP client that supports remote servers over streamable HTTP. Claude connects with OAuth sign-in. Claude Code, Cursor, Windsurf and custom agents connect with an API key header.

Do I need a paid plan to use MCP?

MCP access uses the same permissions as the BlueSales API, which is included with the Business and Agency plans.

Will the AI place calls without asking me?

The tools that place calls, buy numbers or write to calendars are marked as real-world actions, and the assistant is instructed to confirm the exact number or record with you first. For zero risk, connect with a read-only API key.

Can the assistant answer my business phone too?

Yes. The assistant can set up an inbound AI receptionist on a number you own or buy. Callers then talk to the voice agent directly, 24/7, and the assistant can read the transcripts later.