Happy Scribe MCP integration for AI agents.
Connect AI agents to Happy Scribe through 11 structured actions, including create export, create transcription order, delete transcription, and confirm order…
- ACTION CONTRACTS
- 11
- 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 Happy Scribe integration exposes
The Happy Scribe Agent App exposes 11 provider-backed actions for ai and productivity work. Its current contract lets an authorized agent create an asynchronous export for one or more happy scribe transcriptions, submit a transcription or subtitling order from a public media url, and delete one happy scribe transcription 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 Happy Scribe account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Happy Scribe capabilities.
Showing 11 of 11 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
create_exportREADCreate an asynchronous export for one or more Happy Scribe transcriptions.
INPUTS: transcriptionIds / format / showTimestamps / showSpeakers / showComments
create_transcription_orderWRITESubmit a transcription or subtitling order from a public media URL.
INPUTS: mediaUrl / language / service / organizationId / name
delete_transcriptionHIGH IMPACTDelete one Happy Scribe transcription by ID.
INPUTS: transcriptionId / permanent
confirm_orderREVIEWConfirm a previously created Happy Scribe order so processing can begin.
INPUTS: orderId
create_translation_orderWRITESubmit a translation order for an existing Happy Scribe transcription.
INPUTS: sourceTranscriptionId / targetLanguages / service / confirm / webhookUrl
get_exportREADGet the state and download link of a Happy Scribe export.
INPUTS: exportId
get_orderREADGet the current state and details of a Happy Scribe order.
INPUTS: orderId
get_transcriptionREADGet one Happy Scribe transcription by ID.
INPUTS: transcriptionId
list_organizationsREADList the Happy Scribe organizations available to the current API key.
list_transcriptionsREADList transcriptions in a Happy Scribe organization.
INPUTS: organizationId / page / perPage / folderId / tags
update_transcriptionWRITEUpdate editable fields on a Happy Scribe transcription.
INPUTS: transcriptionId / organizationId / name / sharingEnabled / folderId
INPUT CONTRACTS
Know what the action needs before it runs.
create_export
transcriptionIdsREQUIRED- The transcription identifiers included in the export.
formatREQUIRED- The export format, such as txt, srt, vtt, json, csv, or docx.
showTimestampsOPTIONAL- Whether to include timestamps in the export.
showSpeakersOPTIONAL- Whether to include speaker names in the export.
showCommentsOPTIONAL- Whether to include comments in the export.
create_transcription_order
mediaUrlREQUIRED- The public URL of the audio or video file to process.
languageREQUIRED- The spoken language code, such as en-US or es.
serviceREQUIRED- The transcription service level.
organizationIdREQUIRED- The Happy Scribe organization identifier.
nameOPTIONAL- The display name for the order.
delete_transcription
transcriptionIdREQUIRED- The unique identifier of the Happy Scribe transcription.
permanentOPTIONAL- Whether to delete irreversibly instead of moving the transcription to Trash.
confirm_order
orderIdOPTIONAL- The unique identifier of the Happy Scribe order.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Create Export
Create an asynchronous export for one or more Happy Scribe transcriptions. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
create_exportControl Create Transcription Order
Submit a transcription or subtitling order from a public media URL. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_transcription_orderVerify with Get Export
Get the state and download link of a Happy Scribe export. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_exportSAFETY BOUNDARY
Operate Happy Scribe with explicit limits
- Authorize Happy Scribe with API key and grant only the provider access required by the selected actions.
- 4 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_transcription` 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 Happy Scribe rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Happy Scribe task completed successfully.
CONNECTION MODEL
API key
Happy Scribe API key sent as a Bearer token. Get it from the API section of your account at https://www.happyscribe.com/account.
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
- 6
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 1
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 Happy Scribe.