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_taskB | Fetch the current status and latest result payload for a infinitetalk task. |
| check_pricingC | 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 targets a clearly distinct action: task creation (audio_to_video), task polling (get_task), pricing lookup (check_pricing), and authentication (login). There is no overlap or risk of misselection between any pair.
Three tools follow a clean verb_noun snake_case pattern (audio_to_video, get_task, check_pricing), and login is a single verb that still reads naturally. Minor deviation but overall predictable.
Four tools is slightly thin but well-matched to a single-model wrapper: submit a job, poll it, check cost, authenticate. Nothing extraneous, though the surface is minimal.
The create-and-poll lifecycle plus auth and pricing is covered, but there is no way to list tasks, cancel/delete a task, or retrieve results separately from status. For a task-based async API, missing cancellation and enumeration are notable gaps.