aircall-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AIRCALL_API_ID | Yes | Your Aircall API ID (from Aircall Dashboard → Integrations → API keys). | |
| AIRCALL_API_TOKEN | Yes | Your Aircall API token (from Aircall Dashboard → Integrations → API keys). Aircall shows the API token only once. | |
| AIRCALL_TIMEOUT_MS | No | Optional. Override the default 30-second request timeout. Set to a positive integer as a string. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aircall_pingA | Verify that Aircall is reachable and the configured API credentials are valid. |
| aircall_get_companyA | Get basic information about the authenticated Aircall company. |
| aircall_list_usersB | List Aircall users/agents using the current v2 Users API. |
| aircall_get_userA | Get one Aircall user by numeric ID or email address using the v2 Users API. |
| aircall_list_callsA | List calls from Aircall's available six-month history. Results default to compact newest-first metadata; retrieve a call by ID for complete details. |
| aircall_get_callB | Get full metadata for one Aircall call. |
| aircall_search_callsA | Search calls by date, direction, user, phone number, and tag IDs. Aircall applies multiple tags as an AND condition. |
| aircall_get_transcriptionA | Get an AI-generated call transcription. Utterances are paginated locally to keep responses bounded. |
| aircall_get_sentimentsA | Get sentiment analysis for one Aircall call. Requires the applicable Aircall AI feature. |
| aircall_get_topicsB | Get AI-detected topics for one Aircall call. Requires the applicable Aircall AI feature. |
| aircall_get_summaryA | Get AI-generated summary for one Aircall call. Requires the applicable Aircall AI feature. |
| aircall_get_action_itemsA | Get AI-extracted action items for one Aircall call. Requires the applicable Aircall AI feature. |
| aircall_list_numbersB | List phone numbers owned by the Aircall company. |
| aircall_get_numberA | Get one Aircall phone number and its assigned users. |
| aircall_list_contactsA | List shared Aircall contacts. |
| aircall_get_contactA | Get one shared Aircall contact. |
| aircall_search_contactsA | Search shared Aircall contacts by phone number or email address. |
| aircall_list_teamsA | List Aircall teams and their members. |
| aircall_get_teamA | Get one Aircall team and its members. |
| aircall_list_tagsA | List call tags configured for the Aircall company. |
| aircall_get_tagA | Get one Aircall call tag. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 21 tools
Each tool targets a distinct resource and action combination (ping, get_company, list/get users, teams, calls, numbers, contacts, tags, and separate AI analytics for calls). The AI-related tools (transcription, sentiments, topics, summary, action_items) are clearly differentiated by name and description, leaving no ambiguity about what each returns.
All tools follow a consistent 'aircall_<verb>_<resource>' pattern using lowercase snake_case. Verbs are limited to ping, get, list, and search, and nouns are uniformly singular or plural as appropriate. This is a model of consistent naming.
With 21 tools, the set is on the heavier side but still well-scoped for the Aircall domain. It covers company, users, teams, calls, AI features, numbers, contacts, and tags without feeling bloated. The count is appropriate for a comprehensive read-focused API wrapper.
The tool surface is almost entirely read-only: it provides list/get/search for all resources but lacks create, update, or delete operations for users, contacts, numbers, tags, or teams. This is a significant gap for a domain where management actions are expected, limiting the server to analytics and lookup use cases.