Compatible with every major AI agent and IDE
What is the Play.ht (Voice Cloning) MCP Server?
Connect Play.ht to your AI agent to generate high-quality Text-to-Speech (TTS) and create instant voice clones through natural conversation.
What you can do
- Text-to-Speech Generation — Convert text into lifelike audio using various engines like Play3.0-mini and PlayHT2.0-turbo.
- Instant Voice Cloning — Create a digital twin of any voice by simply providing a short audio sample.
- Fine-grained Control — Adjust speed, quality, emotion, and temperature to get the perfect vocal performance.
- Multi-language Support — Generate speech in multiple languages including English, French, Spanish, and more.
How it works
- Subscribe to this server
- Enter your Play.ht User ID and API Key
- Start generating audio and cloning voices from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Content Creators — automate voiceovers for videos and podcasts without manual recording
- Developers — integrate realistic voice interactions into applications and games
- Marketers — create personalized audio messages and localized content at scale
Built-in capabilities (2)
Provide the audio file as a base64 encoded string. Create an instant voice clone from an audio sample
Generate audio from text using Play.ht TTS
Why CrewAI?
When paired with CrewAI, Play.ht (Voice Cloning) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Play.ht (Voice Cloning) tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Play.ht (Voice Cloning) in CrewAI
Play.ht (Voice Cloning) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Play.ht (Voice Cloning) to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Play.ht (Voice Cloning) in CrewAI
The Play.ht (Voice Cloning) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 2 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
Play.ht (Voice Cloning) for CrewAI
Every tool call from CrewAI to the Play.ht (Voice Cloning) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How can I generate audio from text using a specific voice?
Use the generate_tts_stream tool. Provide the text and the unique voice ID. You can also customize the voice_engine (like Play3.0-mini) and emotion for better results.
Can I create a new voice clone with this server?
Yes! Use the create_instant_voice_clone tool. You'll need to provide a name for the voice and a base64 encoded audio sample of the voice you want to clone.
What audio formats are supported for generation?
When using generate_tts_stream, you can specify the output_format as mp3, wav, ogg, flac, or mulaw.
How does CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
SAP Concur
9 toolsEnable your AI agent to manage corporate expenses, track report statuses, and retrieve user profiles via the SAP Concur API.

NeverBounce
10 toolsVerify and clean email addresses via NeverBounce — track single checks and bulk jobs directly from your AI agent.

Bilflo
10 toolsManage your staffing operations via Bilflo — list clients, contractors, and timecards directly from any AI agent.

U.S. EIA Energy Data
10 toolsEquip your AI agent to access official U.S. energy statistics, track electricity generation, and monitor fuel prices via the EIA API.
