Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Aircall to Claude Code

Make Claude tag calls, add notes, and update contacts in Aircall. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Aircall to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Aircall, you add a Aircall MCP server: a small hosted service that exposes Aircall's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Aircall account. No API keys pasted into config files.

claude mcp add --transport http aircall https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Aircall once connected?

Full read-write Aircall access lets Claude tag a call, add a note or comment to a call record, create or update a contact, assign tags for routing, and start an outbound call from a connected number once you approve. The after-call logging and contact upkeep that used to mean console clicks happen where the call already lives.

  • Add a note or comment to a specific call record after a conversation
  • Apply or remove tags on a call to drive triage and reporting
  • Create or update a contact with the right phone numbers and details
  • Start an outbound call from a connected Aircall number once you approve
  • Look up a contact's recent calls and propose follow-up notes
  • Insert or update a tag definition your team uses for routing

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Aircall access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Aircall API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Aircall changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Aircall connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Aircall connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Aircall account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Aircall's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Aircall?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Aircall account it signs in with. Revoking access is one click in Aircall.

More on the Aircall connector

Aircall connector for claude.aiTelegram + Claude CodeWhatsApp Business + Claude CodeWebex + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us