Who is this for?

TextToSpeechSkills helps support teams add controlled voice output to help centers, onboarding flows, product updates, and customer support agents. Teams can approve voice templates for calm, clear replies and use scoped workspace keys so LLM apps only get the speech tools they need. Expression tags let teams adjust tone without rewriting the whole prompt. Credit visibility, workspace permissions, and async jobs make automated audio easier to manage as usage grows across support workflows.

Easy LLM setup

LLM-ready even for non-technical teams

The setup guide walks non-technical teams through creating a scoped key and connecting the MCP tool to their LLM app in a few minutes.

Read setup guide

01Create a scoped key

02Install MCP

03Choose a voice template

04Generate audio from chat

Approved support tone

Templates keep replies calm, clear, and consistent across high-volume customer interactions.

Fast previews for teams

Support leads can test a response in the studio before moving the flow into automation.

Scoped workspace access

Workspace keys and credit limits keep agent-generated audio under team control.

When this helps

Support teams, customer success teams, and voice agent builders usually need a repeatable path for writing, review, generation, billing, and reuse. The most important jobs here are approved support tone, fast previews for teams, scoped workspace access. 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 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 voice agents text-to-speech, support TTS API, customer support voice automation, which makes it easier for humans and LLM apps to share one process without exposing internal routing or credentials.

Before you roll it out

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

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 for Customer Support Voice Agents?

Support teams, customer success teams, and voice agent builders 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.

Can a non-technical user connect this to an LLM app?

The setup guide walks non-technical teams through creating a scoped key and connecting the MCP tool to their LLM app in a few minutes. 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.

Keep exploring TextToSpeechSkills

Use these guides to move from a first audio test to a repeatable workflow for your team.

API playground

Plain JSON in, speech job out

{
  "text": "[quiet] hello. [loud and angry] how are you?",
  "voice_template": "vt_calm_narrator_v1",
  "generation_mode": "instant",
  "format": "mp3"
}

202 queued for polling200 audio ready

MCP install

Agent tools included at launch

Claude Desktoppnpm --package texttospeechskills dlx tts-skills-mcp

Codexpnpm --package texttospeechskills dlx tts-skills-mcp

Cursorpnpm --package texttospeechskills dlx tts-skills-mcp

Skills helperpnpm --package texttospeechskills dlx tts-skills tags

Give support agents a voice that stays on brand