Voice output, not transcription
This workflow creates spoken replies from text. If your agent also needs to hear users, use a separate speech-to-text layer for input, then pass approved response text into TextToSpeechSkills for output.
For agent builders
TextToSpeechSkills gives LLM agents a narrow, reviewable speech workflow: validate markup, choose an approved voice template, check credit use, create a job, and return an audio URL.
TextToSpeechSkills gives AI agents a safe way to create voice output without broad account access. The MCP server exposes focused tools for validating natural expression markup, selecting approved voice templates, checking credit use, creating speech jobs, and returning audio URLs. This is the speech-output side of a voice agent workflow, not a speech-to-text or transcription API. Teams can start with a no-code LLM app setup, then use the same API from production systems when voice output becomes part of customer-facing workflows.
Easy LLM setup
Install the MCP server, add a scoped key, and tell your LLM app which template names it may use. No custom integration is needed for first tests.
Read setup guideThis workflow creates spoken replies from text. If your agent also needs to hear users, use a separate speech-to-text layer for input, then pass approved response text into TextToSpeechSkills for output.
Agents use clear speech tools instead of improvising HTTP calls or handling hidden settings.
Approved voice templates keep agent output consistent across users and workflows.
Credit previews, job states, and workspace billing make automated audio easier to manage.
Agent builders, automation teams, and AI product teams usually need a repeatable path for writing, review, generation, billing, and reuse. The most important jobs here are voice output, not transcription, tool calls you can review, templates protect quality, usage stays visible. Those are the moments where voice becomes part of real work instead of a one-off export.
Start with readable text, add natural-language expression directions when tone matters, choose an approved voice template, and create a speech job through the UI, API, or MCP. The same pattern works for AI agent voice output, voice agent text-to-speech, speech output for voice agents, which makes it easier for humans and LLM apps to share one process without exposing internal routing or credentials.
Decide which templates are approved, how natural expression markup should be reviewed, who can create workspace keys, and which usage limits are acceptable. Those choices keep automated voice generation useful without letting it sprawl from the first paid Test plan through Pro, Scale, and Business usage.
Common questions
These are the practical details that matter before a team adds speech generation to a real workflow.
Agent builders, automation teams, and AI product teams should use this page when they want generated speech that is easy to review, consistent across prompts, and simple to connect to LLM tools. The core workflow combines natural expression markup, voice templates, credit previews, and job-based generation.
Install the MCP server, add a scoped key, and tell your LLM app which template names it may use. No custom integration is needed for first tests. The setup guide keeps the first path short while still giving developers a clean API when the workflow moves into a product backend.
Every paid plan uses credits. Teams can add credit packs when needed, and workspaces on Pro and higher add central billing for $2 per user per month.
API playground
{
"text": "[quiet] hello. [loud and angry] how are you?",
"voice_template": "vt_calm_narrator_v1",
"format": "wav"
}MCP install
npx --yes --package texttospeechskills tts-skills-mcpnpx --yes --package texttospeechskills tts-skills-mcpnpx --yes --package texttospeechskills tts-skills-mcpnpx --yes --package texttospeechskills tts-skills tagsThe public package includes the MCP server, skill instructions, SDK, CLI, OpenAPI file, resources, and prompts.