메뉴
Official ElevenLabs MCP server for Text-to-Speech and Audio generation.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | ElevenLabs MCP Server |
| description | Official ElevenLabs MCP server for Text-to-Speech and Audio generation. |
This skill enables the agent to interact with ElevenLabs' powerful audio capabilities directly through the Model Context Protocol.
For the Conversational AI Strategy (Intake Clerk, Voice Cloning), please refer to:
pip install uvAdd this to your MCP User Settings (e.g., claude_desktop_config.json or VS Code settings.json):
{
"mcpServers": {
"elevenlabs": {
"command": "uvx",
"args": [
"elevenlabs-mcp"
],
"env": {
"ELEVENLABS_API_KEY": "YOUR_ELEVENLABS_API_KEY"
}
}
}
}
Once configured, you can ask the agent to:
For the Web Voice Agent and Inbound Calls, we rely on webhooks to process conversation data.
The Google Apps Script (GAS) backend exposes a single endpoint for all ElevenLabs events:
[GAS_WEB_APP_URL]?source=elevenlabsPOSTbackend-gas/ElevenLabs_WebhookHandler.jsConfigure these in the ElevenLabs Developer Console:
post_call_transcription#ai-conversations) and saves archive to Google Drive.call_initiation_failure#alerts).elevenlabs-signature header.ELEVENLABS_WEBHOOK_SECRET.Dynamically manage MCP server limits by toggling disabled states in mcp_config.json. Use when hitting the 100-tool limit, or when needing a specific MCP server that is currently disabled.
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema-markup.
Wix Design System component reference. Use when building UI with @wix/design-system, choosing components, or checking props and examples. Triggers on "what component", "how do I make", "WDS", "show me props", or component names like Button, Card, Modal, Box, Text.
Creates HTTP endpoints for Wix CLI apps. Use only when the user specifically asks for a backend endpoint. Use when building REST API endpoints, backend HTTP handlers, or server-side logic. Triggers include backend API, HTTP endpoint, HTTP methods, form handling, file uploads.