[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup) # Aircall API and MCP server > Aircall has a full public REST API and an official MCP server in beta (checked 23 Oct 2026). The API needs a key that a company Admin creates under Company Settings > API Keys, and it reads and writes calls, tags, comments, contacts and messages. The MCP server at mcp.aircall.io is read-only: it searches calls and call intelligence, and it cannot tag calls, send messages or change data. Cloud phone system for sales and support teams: calls and SMS in one inbox, shared lines, call tags and notes, contacts, a CRM sync and AI call summaries. ## What is the Aircall API? Cotlet's Aircall API exposes 11 endpoints for your own Aircall account: list calls, get call, get call summary, list conversations, get conversation, search contacts, list tags, set call tags, add call note, send SMS and create contact. The list_calls endpoint returns calls on your lines, newest first, with caller, line, outcome and tags. Each endpoint takes simple JSON inputs like call_id, limit or cursor and works both as an operation of the aircall_read or aircall_write MCP tool for agents and as a REST call for scripts. - **Category:** [Customer support](https://cotlet.dev/integrations/category/customer-support.md) - **Endpoints:** 11 (7 read, 4 write) - **Updated:** 2026-10-20 Aircall has a full public REST API and an official MCP server in beta (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Aircall with 11 endpoints (7 read, 4 write): you sign in once in your own cloud browser, your AI agent does the work. ## Does Aircall have an official API? Aircall has a full public REST API and an official MCP server in beta (checked 23 Oct 2026). The API needs a key that a company Admin creates under Company Settings > API Keys, and it reads and writes calls, tags, comments, contacts and messages. The MCP server at mcp.aircall.io is read-only: it searches calls and call intelligence, and it cannot tag calls, send messages or change data. | Task | Aircall official | Cotlet | |---|---|---| | Search and read calls | Yes: REST API, and the beta MCP server read-only | Yes | | Read summaries, mood and action items | Partly: API and beta MCP, both need the AI add-on; MCP only through the beta | Yes | | Read conversations and SMS threads | Partly: API sends messages and delivers them by webhook; official MCP leaves messaging out | Yes | | Tag a call | Partly: REST API with an admin-made key; official MCP cannot tag calls | Yes | | Add a call note | Partly: REST API comments, 5 per call; official MCP cannot write | Yes | | Send an SMS | Partly: Messaging API, not open to every plan; official MCP cannot send messages | Yes | | Search and create contacts | Partly: REST API with an admin-made key; official MCP lists no contact tools | Yes | | Work from your own seat without an API key | No: Both API and MCP need a person who can create API keys | Yes | Sources: [Aircall Help: Aircall MCP (Beta)](https://support.aircall.io/en-gb/articles/39677926959517), [Aircall for Developers: API references](https://developers.aircall.io/api-references), [Aircall for Developers: Messaging API overview](https://developer.aircall.io/docs/sms), [Zapier: Aircall integrations](https://zapier.com/apps/aircall/integrations) ## Quick reference ```text Aircall has a full public REST API and an official MCP server in beta (checked 23 Oct 2026). The API needs a key that a company Admin creates under Company Settings > API Keys, and it reads and writes calls, tags, comments, contacts and messages. The MCP server at mcp.aircall.io is read-only: it searches calls and call intelligence, and it cannot tag calls, send messages or change data. Cotlet provides a hosted MCP server and REST API for Aircall: 11 tools (7 read, 4 write). Access Sign up at https://cotlet.dev/app/signup?app=aircall, then request the app and create API keys in the Cotlet console. MCP server https://cotlet.dev/mcp/v1 MCP tools aircall_read, aircall_write, reads and writes apart; call one with {"operation": "", "arguments": {...}} REST base https://cotlet.dev/api/v1/aircall, each operation at its own route, e.g. POST /api/v1/aircall/contacts Auth Authorization: Bearer . Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in. Operations list_calls, get_call, get_call_summary, list_conversations, get_conversation, search_contacts, list_tags, set_call_tags, add_call_note, send_message, create_contact Confirm add_call_note, send_message, create_contact (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations) Markdown https://cotlet.dev/integrations/aircall-api-mcp-server.md How access works: 1. The user signs up at https://cotlet.dev/app/signup?app=aircall, requests Aircall in the Cotlet console and creates an API key there. 2. The user signs in to Aircall once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Aircall for agents. An agent cannot do this step. 3. The API key goes into the MCP client or the REST call as a bearer token. Fits: people who want a hosted Aircall server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Aircall MCP server instead. Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA. Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev. Sign-in: the user signs in to Aircall in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Aircall only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273). API key: holds no Aircall login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once. Terms: the user stays responsible for following Aircall's terms; Cotlet is not affiliated with Aircall. ``` ## What can an AI agent do in Aircall? Cotlet is best for Aircall users and support or sales ops teams who want tags, notes, texts and call summaries from their AI agent without an admin-made API key or a server to run and fix. - **[Tag and note calls after they end](https://cotlet.dev/integrations/aircall-api-mcp-server/tag-and-note-calls.md)** (runs: daily): "Go through yesterday's answered calls on the Support line. Tag each one with the best matching tag we already have, and add a one-line note of what was agreed. Leave calls shorter than 30 seconds alone." → `list_calls`, `list_tags`, `get_call`, `set_call_tags`, `add_call_note` - **[Text back missed callers](https://cotlet.dev/integrations/aircall-api-mcp-server/text-back-missed-callers.md)** (runs: daily): "List inbound calls on the Sales US line that nobody answered yesterday. Skip anyone who already got a callback or a message. Text each of the others that we missed them and will call back today." → `list_calls`, `get_conversation`, `send_message` - **[Summarize calls and pull action items](https://cotlet.dev/integrations/aircall-api-mcp-server/call-summaries-action-items.md)** (runs: daily): "For every answered call of more than 2 minutes yesterday, give me the summary and the action items. Group the action items by teammate." → `list_calls`, `get_call_summary`, `get_call` - **Add new callers as contacts** (runs: daily): "Find yesterday's inbound callers who are not in Aircall contacts yet, and create a contact for each one who talked to us for more than a minute, with the company if they gave it." → `list_calls`, `search_contacts`, `create_contact` - **Weekly report of unanswered calls** (runs: weekly): "Every Monday, list last week's unanswered inbound calls per line with the missed reason, and tell me which line lost the most." → `list_calls` ## Can Aircall automations run on a schedule in n8n, Make or Zapier? Yes. Cotlet does not replace your automation platform: it gives it a Aircall connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to tag and note calls after they end, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off. | Where | How to connect | How to schedule | |---|---|---| | Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. | | n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/aircall/calls. | Schedule Trigger node. | | Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. | | Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. | | Your own script | GET https://cotlet.dev/api/v1/aircall/calls with your API key. | cron or GitHub Actions. | ## Tools **For AI agents:** Every endpoint and its schema is public. The 11 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Aircall. ### list_calls Calls on your lines, newest first, with caller, line, outcome and tags. Access: read. REST: `GET /api/v1/aircall/calls`. MCP: `aircall_read → list_calls`. | Parameter | Type | Required | Description | |---|---|---|---| | `since` | date | no | Calls from this date. | | `until` | date | no | Calls up to this date. | | `direction` | enum | no | inbound or outbound. | | `missed` | boolean | no | true: only calls nobody answered. | | `line` | string | no | Aircall line, by name or number. | | `user` | string | no | Teammate, by name as Aircall shows it. | | `tag` | string | no | Only calls with this tag label. | | `limit` | integer | no | Page size. | | `cursor` | string | no | next_cursor from the previous call. | Lists calls as the Calls view of Aircall Workspace shows them, newest first. Each row has the caller, the Aircall line, the teammate, direction, duration, the missed reason for unanswered calls, the tags and whether a note exists. Missed reasons use the values of Aircall Call History, such as agents_did_not_answer, no_available_agent or out_of_opening_hours. Filter by date range, direction, missed, line, teammate or tag. Page with next_cursor. Example response: ```json { "calls": [ { "call_id": "1437759201", "direction": "inbound", "status": "missed", "missed_call_reason": "agents_did_not_answer", "caller": { "name": "Priya Raman", "number": "+14155550142" }, "line": "Sales US", "user": null, "duration_seconds": 0, "started_at": "2026-10-22T16:41:08Z", "tags": [ "Callback Request" ], "has_note": false }, { "call_id": "1437758774", "direction": "inbound", "status": "answered", "missed_call_reason": null, "caller": { "name": "Luis Ortega", "number": "+14155550177" }, "line": "Support", "user": "Ana Silva", "duration_seconds": 412, "started_at": "2026-10-22T15:02:51Z", "tags": [], "has_note": false } ], "next_cursor": null } ``` ### get_call One call with its tags, notes, voicemail transcript and recording link. Access: read. REST: `GET /api/v1/aircall/calls/{call_id}`. MCP: `aircall_read → get_call`. | Parameter | Type | Required | Description | |---|---|---|---| | `call_id` | string | yes | Call ID from list_calls. | Reads the call details view: the caller, line, teammate, timing, tags, the notes, and the voicemail transcript when the caller left one. The recording link and transcript appear only if your Aircall user has recording access; without it the fields come back empty. Use get_call_summary for the AI insights. Example response: ```json { "call_id": "1437758774", "direction": "inbound", "status": "answered", "caller": { "name": "Luis Ortega", "number": "+14155550177" }, "line": "Support", "user": "Ana Silva", "duration_seconds": 412, "started_at": "2026-10-22T15:02:51Z", "tags": [], "notes": null, "voicemail_transcript": null, "recording_url": null } ``` ### get_call_summary AI summary, customer mood, key topics and action items of one call. Access: read. REST: `GET /api/v1/aircall/calls/{call_id}/summary`. MCP: `aircall_read → get_call_summary`. | Parameter | Type | Required | Description | |---|---|---|---| | `call_id` | string | yes | Call ID from list_calls. | Returns what Aircall shows under the call: the call summary, customer mood, key topics and the action items, whether generated by AI or added by hand. Aircall shows these only to users with the AI Assist add-on. It generates them for a transcribed call longer than 1 minute with an Aircall user on it. For any other call the tool returns available: false and a reason instead of an error. Custom summaries are not part of this tool. Example response: ```json { "call_id": "1437758774", "available": true, "summary": "Luis asked why his October invoice shows two seats. Ana found a duplicate and promised a corrected invoice by Friday.", "customer_mood": "neutral", "key_topics": [ "invoice", "duplicate seat" ], "action_items": [ { "text": "Send corrected October invoice by Friday", "done": false } ] } ``` ### list_conversations Conversations in your inbox: calls and SMS threads, newest activity first. Access: read. REST: `GET /api/v1/aircall/conversations`. MCP: `aircall_read → list_conversations`. | Parameter | Type | Required | Description | |---|---|---|---| | `query` | string | no | Contact name or phone number. | | `limit` | integer | no | Page size. | | `cursor` | string | no | next_cursor from the previous call. | Lists the Conversations tab of the Aircall Inbox, where calls and messages of one contact sit together. Each row has the contact or number, the line, the last activity, the type of the last item and a short preview of a message. Search by name or number. Page with next_cursor. Example response: ```json { "conversations": [ { "conversation_id": "conv_5521", "contact": { "name": "Priya Raman", "number": "+14155550142" }, "line": "Sales US", "last_item": "call", "last_activity_at": "2026-10-22T16:41:08Z", "preview": null } ], "next_cursor": null } ``` ### get_conversation The calls and SMS messages of one conversation, oldest first. Access: read. REST: `GET /api/v1/aircall/conversations/{conversation_id}`. MCP: `aircall_read → get_conversation`. | Parameter | Type | Required | Description | |---|---|---|---| | `conversation_id` | string | yes | Conversation ID from list_conversations. | Reads one conversation thread: every call bubble with its direction and outcome, and every SMS with its text, sender and time. Voicemails appear as call items. Use it before send_message so your agent sees what was already said. Example response: ```json { "conversation_id": "conv_5521", "contact": { "name": "Priya Raman", "number": "+14155550142" }, "items": [ { "type": "call", "call_id": "1437759201", "direction": "inbound", "status": "missed", "at": "2026-10-22T16:41:08Z" } ] } ``` ### search_contacts Contacts in Aircall by name, phone number, email or company. Access: read. REST: `GET /api/v1/aircall/contacts/search`. MCP: `aircall_read → search_contacts`. | Parameter | Type | Required | Description | |---|---|---|---| | `query` | string | yes | Name, phone number, email or company. | | `limit` | integer | no | Page size. | | `cursor` | string | no | next_cursor from the previous call. | Searches the Contacts section of Aircall Workspace. Each row has the name, company, phone numbers, emails and whether the contact is an Aircall contact or synced from a connected CRM. Page with next_cursor. Example response: ```json { "contacts": [ { "contact_id": "ct_90112", "name": "Mei Tanaka", "company": "Tanaka Studio", "phones": [ "+14155550163" ], "emails": [ "mei@example.com" ], "source": "aircall" } ], "next_cursor": null } ``` ### list_tags Every call tag of the company, with the default tags marked. Access: read. REST: `GET /api/v1/aircall/tags`. MCP: `aircall_read → list_tags`. No parameters. Lists the tags Aircall shows in the tag menu. All tags are visible to every user and are not tied to a line or team. Default tags (Conference, Callback Request, Called Back, Follow Up, Voicemail Drop, Voice Virtual Agent) come with default: true. Only Admins and Supervisors create tags in the Aircall Dashboard, so this tool lists what set_call_tags can use. Example response: ```json { "tags": [ { "label": "Follow Up", "default": true }, { "label": "Callback Request", "default": true }, { "label": "Pricing", "default": false } ] } ``` ### set_call_tags Set the tags of one call to exactly the list you pass. Access: write. REST: `PUT /api/v1/aircall/calls/{call_id}/tags`. MCP: `aircall_write → set_call_tags`. | Parameter | Type | Required | Description | |---|---|---|---| | `call_id` | string | yes | Call ID from list_calls. | | `tags` | string[] | yes | Tag labels from list_tags. | Replaces the call tags with the labels you pass; an empty list removes them all. A label that is not in list_tags fails with a message naming it, because only Admins and Supervisors create tags. Tags reach no customer and one more call undoes the change, so this tool does not wait for your OK. Tags sync to a CRM connected to the line after the call ends, and a number with mandatory call tagging expects a tag on every connected call. Example response: ```json { "call_id": "1437758774", "tags": [ "Follow Up", "Pricing" ], "updated_at": "2026-10-23T08:15:02Z" } ``` ### add_call_note Add text to the Notes field of one call. Access: write, asks the user first. REST: `POST /api/v1/aircall/calls/{call_id}/note`. MCP: `aircall_write → add_call_note`. | Parameter | Type | Required | Description | |---|---|---|---| | `call_id` | string | yes | Call ID from list_calls. | | `body` | string | yes | Note text. | Adds the text to the call's Notes field, after any note already there. Teammates on the same line can read the note. A note syncs to a connected CRM after the call ends, and once synced it cannot be edited from Aircall. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "call_id": "1437758774", "note": "Duplicate seat on October invoice. Corrected invoice promised by Friday.", "updated_at": "2026-10-23T08:16:40Z" } ``` ### send_message Send one SMS from an Aircall line to a phone number. Access: write, asks the user first. REST: `POST /api/v1/aircall/messages`. MCP: `aircall_write → send_message`. | Parameter | Type | Required | Description | |---|---|---|---| | `line` | string | yes | Aircall line to send from, by name or number, as in list_calls. | | `to` | string | yes | Recipient phone number in international format. | | `body` | string | yes | Message text. | Sends a one-to-one SMS from the line you name, as Aircall Workspace does after Start conversation and Send message. Aircall allows SMS only for numbers in the US, Canada, UK, France, Australia, Germany, Austria, Belgium, Denmark, Finland, the Netherlands, Sweden, Poland and Ireland. Sender and recipient must be in the same country, except US to Canada. In the UK, France, Australia and Germany the line must be a mobile number. A line that cannot send SMS fails with that reason. Text only, no MMS. The message reaches a customer. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "message_id": "msg_30417", "conversation_id": "conv_5521", "line": "Sales US", "to": "+14155550142", "status": "sent", "sent_at": "2026-10-23T08:20:11Z" } ``` ### create_contact Create a new contact in Aircall. Access: write, asks the user first. REST: `POST /api/v1/aircall/contacts`. MCP: `aircall_write → create_contact`. | Parameter | Type | Required | Description | |---|---|---|---| | `phone` | string | yes | Phone number in international format. | | `first_name` | string | no | First name. | | `last_name` | string | no | Last name. | | `company` | string | no | Company name. | | `email` | string | no | Email address. | | `notes` | string | no | Notes, up to 30,000 characters. | Creates a contact as Contacts > Add > Create new contact does. Aircall checks for a contact with the same name or phone number; on a match the tool creates nothing and returns the existing contact. Emojis are removed on save, a contact holds up to 20 extra phone numbers and emails, and notes take up to 30,000 characters. Deleting a contact is an admin action in Aircall, so a wrong one is not undone by a second call. By default you confirm each call; you can switch that off for this tool. Example response: ```json { "contact_id": "ct_90118", "created": true, "name": "Priya Raman", "company": "Raman Dental", "phones": [ "+14155550142" ], "emails": [ "priya@example.com" ] } ``` ## How do I connect Aircall to Claude Code, Codex or Cursor? Connecting Aircall takes three steps: sign up, sign in to Aircall once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key. ### Connect Aircall to your agent. 1. **Create an account** Sign up and add Aircall in the console. Your API key is there too. 2. **Sign in to Aircall in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Aircall there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off. 3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once. Claude Code: ``` claude mcp add --transport http cotlet \ https://cotlet.dev/mcp/v1 \ --header "Authorization: Bearer $COTLET_API_KEY" ``` Cursor: ``` { "mcpServers": { "cotlet": { "url": "https://cotlet.dev/mcp/v1", "headers": { "Authorization": "Bearer ${COTLET_API_KEY}" } } } } ``` Codex: ``` # ~/.codex/config.toml [mcp_servers.cotlet] url = "https://cotlet.dev/mcp/v1" bearer_token_env_var = "COTLET_API_KEY" ``` 4. **Ask your agent** Ask in plain words. Your agent finds the Aircall tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool. ``` Go through yesterday's answered calls on the Support line. Tag each one with the best matching tag we already have, and add a one-line note of what was agreed. Leave calls shorter than 30 seconds alone. ``` ### Call Aircall from your scripts. 1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code. ``` export COTLET_API_KEY="cotlet_..." ``` 2. **Call a tool** Every tool is an endpoint under /api/v1/aircall with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise. ``` curl -X POST https://cotlet.dev/api/v1/aircall/contacts \ -H "Authorization: Bearer $COTLET_API_KEY" \ -H "Content-Type: application/json" \ -d '{"phone":"+14155550142","first_name":"Priya","last_name":"Raman","company":"Raman Dental","email":"priya@example.com"}' ``` 3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing. ``` { "contact_id": "ct_90118", "created": true, "name": "Priya Raman", "company": "Raman Dental", "phones": [ "+14155550142" ], "emails": [ "priya@example.com" ] } ``` ## Why use Cotlet for Aircall? **Built for agents** - One MCP server for every app you connect. - The same tools as a REST API for scripts and cron jobs. - Works with Claude Code, Codex and Cursor. **Your login stays yours** - You sign in to Aircall yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses. - A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory. - The model never sees a login. - No stored passwords, no CAPTCHA solving, no MFA bypass. **You stay in control** - Scope each API key: its apps, its tools, read only or read and write. - Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you. - Every background request listed in your Background activity. Disable for agents in one click. **Kept working for you** - We test every integration every 6 hours. - When Aircall changes, the tool pauses until we fix it. - Failed calls cost nothing. ## Is it safe to connect Aircall to Cotlet? Yes. You sign in to Aircall yourself, in your own Cloud Browser, and we never save your password. Your agents only get Aircall once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself. - **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev) - **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on) - **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev) - **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev) [How Cotlet protects your access](https://cotlet.dev/security.md) ### Common concerns **Who runs Cotlet?** Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet. **Is this an official Aircall integration?** No, Cotlet is independent of Aircall. Aircall's own API is too limited for this work. Cotlet works through your own Aircall account, the way you use Aircall in the browser, so you need no partner approval and no developer setup. **What about client data and GDPR?** Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it. **Can I start with read only?** Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool. **Is it reliable?** Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev. **How do I stop?** Press Disable for agents next to Aircall in your console: your agents lose access at once and you stay signed in. Signing out of Aircall in the browser works too, and Reset browser deletes the whole profile. ## Is there a Aircall MCP server on GitHub? Yes. Community Aircall MCP servers exist on GitHub, usually maintained by one person. The ones we checked call the Aircall REST API with an API key. You install one yourself, an admin makes the key, and you fix it when it breaks. Cotlet hosts the same kind of server for you, works from your own signed-in seat and needs no API key, and our team keeps it working. | | GitHub MCP server | Cotlet | |---|---|---| | Setup | Clone the repo, install it, add an API key, add it to each MCP client | Sign up, sign in to Aircall once, add one MCP server or API key | | Who can set it up | An Aircall Admin who can create API keys | Any user who can sign in to Aircall; the tools follow your role | | When Aircall changes | It breaks until you or the maintainer fix it | Our team runs automatic checks and fixes it for you; failed calls are free | | Your Aircall access | An API key in a file or environment variable on your computer | Your own session in your Cloud Browser in the EU, profile encrypted, disabled for agents in one click | | Upkeep | You update, monitor and debug it yourself | Nothing to host or update | | Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule | | Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription | ### Which one fits you **Pick Cotlet if** - you are not a developer, or you do not want to maintain a server - you need it to keep working when Aircall changes, without checking it yourself - your agent or a script should run it on a schedule, also while your computer is off **Pick an open-source server if** - you are comfortable installing, updating and fixing it yourself - you want your sign-in to stay on your own computer - you only need it now and then, from one MCP client ## How much does the Aircall API cost? Free 7-day trial with 2,000 credits, no card needed. After that, the Aircall API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over. | Credits | Price, one time | Calls at 10 credits | Per 1,000 credits | |---|---|---|---| | 5,000 | $29 | 500 | $5.80 | | 15,000 | $79 | 1,500 | $5.27 | | 32,000 | $149 | 3,200 | $4.66 | | 60,000 | $249 | 6,000 | $4.15 | Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md) ## How Cotlet holds your access Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Aircall account. - **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms) - **Your sign-in:** You sign in to Aircall yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Aircall only after you enable it. When Aircall signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md) - **Revoking access:** Press Disable for agents next to Aircall, sign out of Aircall in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool. - **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA. - **Aircall's terms:** You use your own Aircall account and stay responsible for following Aircall's terms. Cotlet is independent and not affiliated with Aircall. [Terms](https://cotlet.dev/terms) - **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev) ## Frequently asked questions **How do I get access?** Sign up free, open Aircall in the console and press Request access. Then you create your API key and connect Aircall there. **Do I need to be technical?** No. You sign in to Aircall once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix. **Is it safe to connect Aircall to Cotlet?** Yes. You sign in to Aircall yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Aircall once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security. **Is a hosted server safer than a local one? My Aircall sign-in would leave my computer.** On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Aircall cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off. **Why does Cotlet send requests instead of clicking in my browser?** To be fast, Cotlet doesn't click through Aircall's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Aircall sees the same browser and IP you signed in with, and every request is listed in your Background activity. **What if someone gets my Cotlet API key?** The key holds no Aircall login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once. **Why a signed-in browser and not OAuth, like other integration platforms?** Aircall offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273). **Do I need an Aircall admin or an API key?** No. Cotlet works from your own signed-in Aircall Workspace seat, so it needs no API key and no Admin to make one. Your role still counts: only Admins and Supervisors create tags, the Dashboard Call History is for Admins and Supervisors, and summaries need an AI Assist add-on on your seat. **Can my agent make or answer calls?** No. The tools read call history and conversations, tag calls, add notes, send SMS and manage contacts. Calls are made and answered by people in Aircall Workspace. **When is the Aircall API the better choice?** For high volume and live events. The API allows 120 requests a minute per company and pushes call, message and contact events by webhook, while a signed-in session works at the speed of the app and polls. If you have an Admin and want that, use the API. If you do not, or want one agent tool without the build, use Cotlet. **Can my agent post or send messages in Aircall without asking me?** No. Every call to add_call_note, send_message or create_contact waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. set_call_tags runs without asking, because it sends nothing to anyone and one call undoes it. **Can I use the Aircall API in n8n?** Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/aircall from the HTTP Request node. --- Give your AI agents your signed-in browser. **Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) **Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet) **Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) **Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md) **Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors) **Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet) Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md) Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.