Create a scoped key
Use a workspace key for the LLM app so billing, permissions, and rotation are easy to manage.
Guide
This guide shows the simplest path from account to generated speech: create a scoped key, install the MCP tool, pick a voice template, and ask your LLM app to generate audio with readable expression tags.
The LLM text-to-speech setup guide explains how to connect TextToSpeechSkills to an LLM app without writing a custom integration first. The basic flow is to choose a paid plan, create a scoped workspace key, copy the MCP install command, pick voice templates the agent may use, and ask the LLM app to generate speech with readable expression tags. The same setup can validate markup, check credit use, create speech jobs, and return audio URLs while keeping billing and credentials controlled.
Easy LLM setup
You do not need to build an integration first. Copy the MCP install command, paste it into your LLM app settings, and use the included skill instructions as your starting prompt.
Start test planUse a workspace key for the LLM app so billing, permissions, and rotation are easy to manage.
Copy the install command from the dashboard into your LLM app. The agent receives approved speech tools immediately.
Tell the agent which voice template to use and let it add tags like [quiet], [excited], or [loud and angry].
Non-technical users and teams setting up speech generation inside LLM apps usually need a repeatable path for writing, review, generation, billing, and reuse. The most important jobs here are create a scoped key, install the mcp tool, use templates and tags. Those are the moments where voice becomes part of real work instead of a one-off export.
Start with readable text, add expression tags when tone matters, choose an approved voice template, and create a speech job through the UI, API, or MCP. The same pattern works for LLM text-to-speech setup, MCP TTS guide, connect text-to-speech to LLM, which makes it easier for humans and LLM apps to share one process without exposing internal routing or credentials.
Decide which templates are approved, which expression tags are allowed, 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.
Non-technical users and teams setting up speech generation inside LLM apps 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 expression tags, voice templates, credit previews, and job-based generation.
You do not need to build an integration first. Copy the MCP install command, paste it into your LLM app settings, and use the included skill instructions as your starting prompt. 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",
"generation_mode": "instant",
"format": "mp3"
}MCP install
pnpm --package texttospeechskills dlx tts-skills-mcppnpm --package texttospeechskills dlx tts-skills-mcppnpm --package texttospeechskills dlx tts-skills-mcppnpm --package texttospeechskills dlx tts-skills tags