ElevenLabs MCP Server

Created By
mamertofabiana year ago
Overview

what is ElevenLabs MCP Server?

ElevenLabs MCP Server is a Model Context Protocol (MCP) server that integrates with the ElevenLabs text-to-speech API, providing a server component and a sample web-based MCP Client for managing voice generation tasks.

how to use ElevenLabs MCP Server?

To use the ElevenLabs MCP Server, you can either install it using the recommended uvx tool or set it up for development by cloning the repository and installing dependencies. You can also use the sample SvelteKit MCP Client to interact with the server.

key features of ElevenLabs MCP Server?

  • Generate audio from text using ElevenLabs API
  • Support for multiple voices and script parts
  • SQLite database for persistent history storage
  • Sample SvelteKit MCP Client for text-to-speech conversion and voice management

use cases of ElevenLabs MCP Server?

  1. Creating audio content from written scripts
  2. Managing voiceover tasks for multimedia projects
  3. Tracking and playing back voice generation history

FAQ from ElevenLabs MCP Server?

  • Can I use multiple voices in my audio generation?

Yes! The server supports multiple voices and script parts for diverse audio outputs.

  • Is there a web interface available?

Yes! A sample SvelteKit MCP Client is provided for easy interaction with the server.

  • What do I need to run the server?

You need to have your ElevenLabs API key and voice ID configured in the settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mamertofabian
Star
-
Language
-
License
-

Recommend Servers

View All
Payai X402 Tools

8 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago