Register a Public MCP

Overview

Registering an MCP with Aircall makes your tools and resources available to every Aircall AI customer, so it can call them directly instead of relying on a custom, hardcoded integration. The process has three steps on your side:

Build a compliant MCP.
Apply to the tech partner program.
Share the details we need to connect to it.

From there, the work shifts to Aircall. Our team reviews your submission, registers the connector, and runs it through an evaluation loop with our own AI agents before it goes live. If anything needs adjusting on your end, we'll tell you specifically what and why.

Prerequisites

An MCP server reachable over HTTPS that implements the Model Context Protocol specification.
You must be an approved technology partner or submit an application. Only technology partners can publish public integrations. See how to publish an app for more information.
Tools and resources with descriptive names, input schemas, and descriptions — this is what Aircall AI reasons over when deciding what to call.
If your MCP requires authentication: an OAuth 2.1 authorization server, ideally with Dynamic Client Registration (DCR) support. Whether you support DCR determines what you'll provide in Step 3.

Step 1 — Build your MCP to the standard

Your MCP server needs to conform to the Model Context Protocol before we can connect to it. There's no Aircall-specific dialect — a standards-compliant server is all we need.

🚧
Tool definitions are what we evaluate first
Aircall AI selects and sequences tools based on their names, descriptions, and input schemas. Ambiguous descriptions, overlapping tool names, or missing parameter descriptions are the most common reasons a submission needs revision — get these right up front and the review moves faster.

A few things worth checking before you apply:

Each tool does one thing, with a description that explains what it does and when to use it.
Error responses are clear and structured, not generic failures.
Your server responds within a reasonable time for a live voice conversation — slow tools affect the caller experience directly.

Step 2 — Sign up as an Aircall tech partner

Once your MCP is built, apply to become an Aircall tech partner. This is required if you want Aircall AI agents to connect to your MCP — it's how we track who we're connecting to and route your submission for review.

In the application, tell us about your company, the use case your MCP supports, and the upstream URL where your MCP is hosted. Our ecosystem team reviews applications and follows up with next steps

Step 3 — Give us your connection details

What we need from you here depends entirely on whether your MCP's authorization server supports Dynamic Client Registration (DCR).

	DCR supported	DCR not supported
What you provide	Your MCP's upstream URL	Your MCP's upstream URL, plus a pre-registered OAuth client or a demo account for us to manage it and test.
What that includes	Nothing further — we register a client with your authorization server automatically	Client ID, client secret, authorization endpoint, token endpoint, redirect URI, and required scopes
Who does the work	Us — registration happens on connection	You and us — a one-time setup of a client for Aircall in your own system

📘
Don't have an OAuth layer at all?
If your MCP doesn't require authentication, we only need the upstream URL — there's no client to provision either way.

What happens after you submit

From here, the remaining work is on our side.

We review your submission — our team checks your MCP against the standard and registers the connection using the details from Step 3.
We run evaluation loops — we test your MCP with our own AI agents across a set of realistic conversational scenarios, checking whether the right tools get selected, whether responses come back correctly, and how the integration holds up in practice.
We share feedback, if there is any — if evaluation surfaces friction (a tool description that's easy to misread, a missing parameter, an edge case that isn't handled), we'll tell you exactly what we found and ask you to update the relevant tool definitions. This can take more than one round before everything checks out.
Your MCP goes live — once evaluation passes, Aircall AI can start calling your tools in production.

👍
This is a feedback loop, not a one-time check
Evaluation isn't pass/fail on the first attempt. Expect a conversation with our team if adjustments are needed, rather than a rejection.