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_speechA | Create a Gemini TTS 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 gemini-tts task. |
| check_pricingA | 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 has a clearly distinct purpose: authentication, creating a TTS task, fetching task status, and checking pricing. No overlap or ambiguity between them.
Most tools follow a verb_noun pattern (get_task, check_pricing), and login is a simple verb. text_to_speech is a compound noun phrase rather than verb_noun, but all are lowercase with underscores and readable.
With only 4 tools, the server is tightly scoped to the essential operations for RunAPI Gemini TTS. Each tool earns its place and the count is appropriate for the narrow domain.
Core lifecycle is covered: auth, create task, poll for results, and check pricing. Missing features like task cancellation or listing historical tasks are minor gaps that don't break the primary workflow.