infinitetalk-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RUNAPI_API_KEY | No | Your RunAPI API key. Alternatively, can 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. |
| audio_to_videoB | Create a InfiniteTalk task on RunAPI (audio to video). Returns a task id, status, and output URLs. |
| get_taskA | Fetch the current status and latest result payload for a infinitetalk task. |
| check_pricingB | Look up RunAPI pricing for the infinitetalk 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 role: authentication, task creation, task status retrieval, and pricing lookup. No overlap or ambiguity between them.
Most tools follow a verb_noun pattern (audio_to_video, get_task, check_pricing), but 'login' is a standalone verb, creating a minor inconsistency. Still, the naming is clean and predictable overall.
With only 4 tools, the server is tightly scoped to its purpose of managing InfiniteTalk tasks via RunAPI. Every tool serves a necessary function without bloat.
Core lifecycle is covered: create task, check status, and get pricing. Missing cancellation or task listing, but those are minor gaps for a simple workflow.