AssemblyAI MCP integration for AI agents.
Connect AI agents to AssemblyAI through 6 structured actions, including get transcript, create transcript, and delete transcript. Review authentication, inpu…
- ACTION CONTRACTS
- 6
- 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 AssemblyAI integration exposes
The AssemblyAI Agent App exposes 6 provider-backed actions for ai and developer tools work. Its current contract lets an authorized agent get one assemblyai transcript by id, create an assemblyai transcript from an audio or video file url, and delete one assemblyai transcript by id. 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 AssemblyAI account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real AssemblyAI capabilities.
Showing 6 of 6 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_transcriptREADGet one AssemblyAI transcript by ID.
INPUTS: transcriptId
create_transcriptWRITECreate an AssemblyAI transcript from an audio or video file URL.
INPUTS: audioUrl / speechModel / languageCode / languageDetection / punctuate
delete_transcriptHIGH IMPACTDelete one AssemblyAI transcript by ID.
INPUTS: transcriptId
get_transcript_paragraphsREADGet an AssemblyAI transcript split into paragraphs.
INPUTS: transcriptId
get_transcript_sentencesREADGet an AssemblyAI transcript split into sentences.
INPUTS: transcriptId
list_transcriptsREADList AssemblyAI transcripts created by the current API key.
INPUTS: limit / status / createdOn / beforeId / afterId
INPUT CONTRACTS
Know what the action needs before it runs.
get_transcript
transcriptIdOPTIONAL- The unique identifier of the AssemblyAI transcript.
create_transcript
audioUrlREQUIRED- The URL of the audio or video file to transcribe.
speechModelOPTIONAL- The AssemblyAI speech model to use for transcription.
languageCodeOPTIONAL- The language code of the audio file, such as en_us or es.
languageDetectionOPTIONAL- Whether AssemblyAI should detect the spoken language.
punctuateOPTIONAL- Whether AssemblyAI should add punctuation to the transcript.
delete_transcript
transcriptIdOPTIONAL- The unique identifier of the AssemblyAI transcript.
get_transcript_paragraphs
transcriptIdOPTIONAL- The unique identifier of the AssemblyAI transcript.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Transcript
Get one AssemblyAI transcript 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_transcriptControl Create Transcript
Create an AssemblyAI transcript from an audio or video file URL. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_transcriptVerify with Get Transcript Paragraphs
Get an AssemblyAI transcript split into paragraphs. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_transcript_paragraphsSAFETY BOUNDARY
Operate AssemblyAI with explicit limits
- Authorize AssemblyAI with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_transcript` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in AssemblyAI rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the AssemblyAI task completed successfully.
CONNECTION MODEL
API key
AssemblyAI API key sent in the Authorization header. Create or manage API keys in the AssemblyAI Dashboard: https://www.assemblyai.com/dashboard.
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
- 4
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- 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 AssemblyAI.