AiVOOV MCP integration for AI agents.
Connect AI agents to AiVOOV through 2 structured actions, including list voices and create audio. Review authentication, inputs, workflows, and safety guidan…
- ACTION CONTRACTS
- 2
- 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 AiVOOV integration exposes
The AiVOOV Agent App exposes 2 provider-backed actions for ai and design & media work. Its current contract lets an authorized agent list available aivoov voices, optionally filtered by language code and generate base64 audio from one or more voice/text segments. 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 AiVOOV account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real AiVOOV capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
list_voicesREADList available AiVOOV voices, optionally filtered by language code.
INPUTS: languageCode
create_audioWRITEGenerate base64 audio from one or more voice/text segments.
INPUTS: segments
INPUT CONTRACTS
Know what the action needs before it runs.
list_voices
languageCodeOPTIONAL- The language code used to filter voices.
create_audio
segmentsOPTIONAL- Voice/text segments to render into one audio payload.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect List Voices
List available AiVOOV voices, optionally filtered by language code. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
list_voicesControl Create Audio
Generate base64 audio from one or more voice/text segments. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_audioVerify with Create Audio
Generate base64 audio from one or more voice/text segments. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_audioSAFETY BOUNDARY
Operate AiVOOV with explicit limits
- Authorize AiVOOV with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- 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 AiVOOV rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the AiVOOV task completed successfully.
CONNECTION MODEL
API key
AiVOOV API key sent with the x-api-key header. Get it from your AiVOOV account while setting up the Text-to-Speech API: https://aivoov.com/text-to-speech-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
- 1
- WRITE SIGNALS
- 1
- 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 AiVOOV.