Aircall MCP integration for AI agents.
Connect AI agents to Aircall through 10 structured actions, including get call, get contact, and get number. Review authentication, inputs, workflows, and sa…
- ACTION CONTRACTS
- 10
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Aircall integration exposes
The Aircall Agent App exposes 10 provider-backed actions for communication and productivity work. Its current contract lets an authorized agent retrieve one aircall call by id, retrieve one aircall contact, and retrieve one aircall phone number. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Aircall account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Aircall capabilities.
Showing 10 of 10 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_callREADRetrieve one Aircall call by ID.
INPUTS: id / fetchContact / fetchShortUrls / fetchCallTimeline
get_contactREADRetrieve one Aircall contact.
INPUTS: id
get_numberREADRetrieve one Aircall phone number.
INPUTS: id
get_teamREADRetrieve one Aircall team.
INPUTS: id
get_userREADRetrieve one Aircall user with the current V2 Users API.
INPUTS: id
list_callsREADList Aircall calls with optional date and payload expansion filters.
INPUTS: page / perPage / from / to / order
list_contactsREADList Aircall contacts.
INPUTS: page / perPage / order
list_numbersREADList Aircall phone numbers.
INPUTS: page / perPage
list_teamsREADList Aircall teams.
INPUTS: page / perPage
list_usersREADList Aircall users with the current V2 Users API.
INPUTS: page / perPage
INPUT CONTRACTS
Know what the action needs before it runs.
get_call
idREQUIRED- The Aircall numeric resource ID.
fetchContactOPTIONAL- Whether Aircall should include contact details for the call.
fetchShortUrlsOPTIONAL- Whether Aircall should include shortened recording URLs.
fetchCallTimelineOPTIONAL- Whether Aircall should include call timeline details.
get_contact
idREQUIRED- The Aircall numeric resource ID.
get_number
idREQUIRED- The Aircall numeric resource ID.
get_team
idREQUIRED- The Aircall numeric resource ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Call
Retrieve one Aircall call by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_callVerify with Get Contact
Retrieve one Aircall contact. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_contactSAFETY BOUNDARY
Operate Aircall with explicit limits
- Authorize Aircall with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Aircall data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Aircall rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Aircall task completed successfully.
CONNECTION MODEL
API key
Aircall API token used as the Basic Auth password. Generate or view API credentials in Aircall Dashboard integrations: https://dashboard.aircall.io/integrations/api.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 10
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Aircall.