Small tool surface
Agents get focused speech tools instead of broad account access, which makes reviews and permissions easier.
MCP for speech generation
The TextToSpeechSkills MCP server lets agents prepare speech without guessing your billing rules or voice settings. They can validate markup, pick approved templates, preview credit use, create jobs, and return audio URLs through a narrow tool surface.
The TextToSpeechSkills MCP server gives LLM apps a controlled way to create speech. Instead of asking an agent to improvise API calls, you install a focused tool surface for validating expression markup, listing approved voice templates, previewing credit use, creating speech jobs, and retrieving audio URLs. The workflow is useful for non-technical users because setup is mostly copy and paste: create a scoped key, install the MCP command, choose allowed templates, and ask the LLM app to generate audio. Billing controls and keys remain separate from the prompt.
Easy LLM setup
Connect it by copying one MCP command into your LLM app settings. The agent gets speech tools immediately, while keys and billing controls stay scoped.
Read setup guideAgents get focused speech tools instead of broad account access, which makes reviews and permissions easier.
Approved templates keep brand voices steady while still letting agents add local expression tags.
Usage previews and workspace permissions help teams keep automated audio generation under control.
People connecting LLM apps to speech generation with MCP usually need a repeatable path for writing, review, generation, billing, and reuse. The most important jobs here are small tool surface, templates over prompts, credit-aware generation. 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 TTS MCP server, MCP voice tools, LLM text-to-speech, 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.
People connecting LLM apps to speech generation with MCP 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.
Connect it by copying one MCP command into your LLM app settings. The agent gets speech tools immediately, while keys and billing controls stay scoped. 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