@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. |
| text_to_dialogueB | Create a ElevenLabs task on RunAPI (text to dialogue). Returns a task id, status, and output URLs. |
| text_to_speechB | Create a ElevenLabs task on RunAPI (text to speech). Returns a task id, status, and output URLs. |
| get_taskB | Fetch the current status and latest result payload for a elevenlabs task. |
| check_pricingC | 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 5 tools
Each tool has a largely distinct purpose: login and check_pricing are unrelated to generation, get_task polls results, and the two creation tools differ by single- vs multi-speaker output. The main risk is text_to_speech vs text_to_dialogue, since both 'create a task' and an agent could pick the wrong one, but the descriptions make the distinction clear enough.
All names use snake_case, and most follow a verb_noun pattern (check_pricing, get_task). The exceptions are the bare verb 'login' and the noun-phrase style text_to_speech/text_to_dialogue, which read more like resource names than actions, but the set is still predictable and readable.
Five tools is a tight, focused surface for an ElevenLabs wrapper (auth, pricing, generation x2, task lookup). It is on the thin side but each tool clearly earns its place; no bloat.
Core generation, auth, and result polling are covered, but there is no list_tasks or cancel/delete operation, so once a task id is lost the agent has no way to recover or enumerate work. Voice/model listing and any voice-selection capability are also absent, which are natural parts of a text-to-speech domain.