Retell AI MCP server integration for AI agents.
Connect AI agents to Retell AI through 8 structured actions, including get call, get phone number, and get voice. Review authentication, inputs, workflows, a…
- ACTION CONTRACTS
- 8
- 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 Retell AI integration exposes
The Retell AI Agent App exposes 8 provider-backed actions for ai and communication work. Its current contract lets an authorized agent retrieve details for a specific retell ai call, retrieve details for a specific retell ai phone number, and retrieve details for a specific retell ai voice. 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 Retell AI account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Retell AI capabilities.
Showing 8 of 8 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_callREADRetrieve details for a specific Retell AI call.
INPUTS: callId
get_phone_numberREADRetrieve details for a specific Retell AI phone number.
INPUTS: phoneNumber
get_voiceREADRetrieve details for a specific Retell AI voice.
INPUTS: voiceId
get_voice_agentREADRetrieve details for a specific Retell AI voice agent.
INPUTS: agentId / version
list_callsREADList Retell AI calls with pagination and optional simple filters.
INPUTS: limit / paginationKey / skip / sortOrder / includeTotal
list_phone_numbersREADList Retell AI phone numbers with cursor pagination.
INPUTS: limit / paginationKey / sortOrder
list_voice_agentsREADList Retell AI voice agents with optional pagination filters.
INPUTS: limit / paginationKey / paginationKeyVersion / isLatest
list_voicesREADList all Retell AI voices available to the authenticated workspace.
INPUT CONTRACTS
Know what the action needs before it runs.
get_call
callIdOPTIONAL- The call id to retrieve call history for.
get_phone_number
phoneNumberOPTIONAL- E.164 phone number to retrieve.
get_voice
voiceIdOPTIONAL- Unique id for the voice.
get_voice_agent
agentIdREQUIRED- Unique id of the voice agent to retrieve.
versionOPTIONAL- Agent version reference.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Call
Retrieve details for a specific Retell AI call. 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 Phone Number
Retrieve details for a specific Retell AI phone number. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_phone_numberSAFETY BOUNDARY
Operate Retell AI with explicit limits
- Authorize Retell AI with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Retell AI 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 Retell AI rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Retell AI task completed successfully.
CONNECTION MODEL
API key
Retell AI API key sent in the Authorization Bearer header. Create and manage API keys in the Retell dashboard Settings > API Keys.
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
- 8
- 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 Retell AI.