RunAPI Gemini TTS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | API key for RunAPI. Required for text_to_speech and get_task operations. Optional if you have logged in via the login tool, but recommended for headless environments. |
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_speechB | Create a Gemini TTS 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 gemini-tts task. |
| check_pricingC | Look up RunAPI pricing for the gemini-tts 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 4 tools
Each tool targets a clearly distinct action: authentication, task creation, task status retrieval, and pricing lookup. There is no overlap between text_to_speech (create) and get_task (poll), so an agent can select the right tool without ambiguity.
The set predominantly uses snake_case verb_noun names (text_to_speech, get_task, check_pricing). The lone 'login' is a minor deviation because it omits a noun, but it remains readable and predictable.
Four tools is well-scoped for an API wrapper focused on Gemini TTS. Authentication, task creation, task polling, and pricing lookup each earn their place without unnecessary bloat.
The core workflow of authenticating, creating a TTS task, polling its result, and checking pricing is covered. Minor gaps such as task cancellation, deletion, or listing are absent but can likely be worked around for the stated purpose.