Prepare 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
Text-to-speech MCP tools for LLM apps
TextToSpeechSkills is preparing a focused MCP and skills workflow for npm release. After publication, an agent will be able to validate natural-language expression markup, read speech resources, use prompts, choose approved voice templates, check credit use, create jobs, and return audio links without broad account access.
Who is this for?
TextToSpeechSkills is preparing a text-to-speech MCP package for teams that want LLM apps to create audio safely. The package source exposes narrow speech tools, resources, and prompts for validating natural-language expression markup, listing approved voice templates, previewing credit use, creating async speech jobs, and returning audio URLs. Teams can use the browser studio or API now; copy-and-paste MCP setup will become available after npm publication.
Easy LLM setup
LLM-ready even for non-technical teams
The MCP package is prepared for release but is not published yet. Teams can use the browser studio or API now, then connect a scoped key and approved templates when the npm package becomes available.
Read setup guide01Create a scoped key
02Use the studio or API
03Choose a voice template
04Generate and review audio
Validate text before audio
Agents can check bracket syntax, preview credit use, and refine vague delivery directions before a speech job uses credits.
Use approved voice templates
Template names keep narrators, characters, and support voices consistent while letting the LLM handle each script.
When this helps
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 prepare 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.
How the workflow works
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 or API. After npm publication, MCP will use the same pattern for text-to-speech MCP, text to speech MCP, MCP text-to-speech, LLM speech tools, helping humans and LLM apps share one process without exposing internal routing or credentials.
Before you roll it out
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
What teams usually ask before starting
These are the practical details that matter before a team adds speech generation to a real workflow.
Who should use Text-to-Speech MCP for LLM Apps?
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 natural expression markup, voice templates, credit previews, and job-based generation.
Can a non-technical user connect this to an LLM app?
The MCP package is prepared for release but is not published yet. Teams can use the browser studio or API now, then connect a scoped key and approved templates when the npm package becomes available. The setup guide keeps the first path short while still giving developers a clean API when the workflow moves into a product backend.
How does pricing stay predictable?
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
Plain JSON in, speech job out
{
"text": "[quiet] hello. [loud and angry] how are you?",
"voice_template": "vt_calm_narrator_v1",
"format": "wav"
}Job created200 audio ready
MCP package
MCP package release pending
npm release status
Install commands are not available yetThe package is prepared for release but is not published. Use the browser studio or API today; MCP commands will appear here after npm publication.
Read API docs