Install one focused speech tool
The LLM app gets purpose-built speech actions instead of broad account access, so setup feels simple and permissions stay easy to explain.
Text-to-speech MCP
TextToSpeechSkills gives LLM apps a focused MCP toolset for turning scripts into speech. The agent can validate expression tags, choose approved voice templates, check credit use, create jobs, and return audio links without touching broad account settings.
TextToSpeechSkills is a text-to-speech MCP platform for teams that want LLM apps to create audio safely. The MCP server exposes narrow speech tools for validating readable expression tags, listing approved voice templates, previewing credit use, creating async speech jobs, and returning audio URLs. Non-technical users can connect it with a copy-and-paste setup, while developers still get a clean API when the same workflow moves into a product backend. The domain texttospeechskills.com also matches the workflow: text-to-speech skills, MCP tools, reusable voices, and simple setup for LLM users.
Easy LLM setup
Setup is intentionally short: create a scoped key, copy the MCP install command, choose which voice templates the LLM may use, and ask for audio from chat.
Read setup guideThe LLM app gets purpose-built speech actions instead of broad account access, so setup feels simple and permissions stay easy to explain.
Agents can check expression tags, preview credit use, and correct unsupported directions before a speech job uses credits.
Template names keep narrators, characters, and support voices consistent while letting the LLM handle each script.
Teams connecting LLM apps, desktop agents, and AI workspaces to text-to-speech usually need a repeatable path for writing, review, generation, billing, and reuse. The most important jobs here are install one focused speech tool, validate text before audio, use approved voice templates. 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 text-to-speech MCP, text to speech MCP, MCP text-to-speech, LLM speech tools, 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.
Teams connecting LLM apps, desktop agents, and AI workspaces to text-to-speech 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.
Setup is intentionally short: create a scoped key, copy the MCP install command, choose which voice templates the LLM may use, and ask for audio from chat. 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