@runapi.ai/elevenlabs-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Your RunAPI API key. Can also be set in ~/.config/runapi/config.json |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| loginA | Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json. |
| isolate_audioB | Create a ElevenLabs task on RunAPI (isolate audio). Returns a task id, status, and output URLs. |
| speech_to_textB | Create a ElevenLabs task on RunAPI (speech to text). Returns a task id, status, and output URLs. |
| text_to_dialogueC | Create a ElevenLabs task on RunAPI (text to dialogue). Returns a task id, status, and output URLs. |
| text_to_soundC | Create a ElevenLabs task on RunAPI (text to sound). Returns a task id, status, and output URLs. |
| text_to_speechC | Create a ElevenLabs task on RunAPI (text to speech). Returns a task id, status, and output URLs. |
| get_taskA | Fetch the current status and latest result payload for a elevenlabs task. |
| check_pricingB | Look up RunAPI pricing for the elevenlabs model line. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: authentication, pricing, task status, and five different ElevenLabs task types (speech, sound, dialogue, transcription, source isolation). No overlap or ambiguity between tools.
The tool names mix two patterns: verb_noun (get_task, login, isolate_audio, check_pricing) and noun_to_noun (speech_to_text, text_to_dialogue, text_to_sound, text_to_speech). While each group is internally consistent, the coexistence of two patterns reduces predictability.
With 8 tools, the server is well-scoped for its purpose: covering authentication, pricing, status polling, and five core ElevenLabs task types. No redundant or unnecessary tools; the count fits the ideal range.
The set covers the main lifecycle: creating various task types, fetching status/results, authenticating, and checking pricing. Missing a cancel or list operation is a minor gap that agents can work around, but the core workflow is complete.