What can you do with this server?

This server provides an MCP interface for the RunAPI InfiniteTalk model, allowing AI agents to create audio-to-video tasks, monitor their status, and check pricing. * audio_to_video: Submit a task to generate a video from an audio source using the infinitetalk-from-audio model. Supports an optional source image URL, output resolution (480p or 720p), and can either wait for completion or return immediately with a task ID. * get_task: Poll the current status and result payload (including output URLs) for a previously created task using its ID. * check_pricing: Retrieve the current pricing snapshot for the InfiniteTalk model and endpoints — no API key required.

How do I use infinitetalk-mcp?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@infinitetalk-mcp Turn this audio file into a video using the InfiniteTalk model" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

infinitetalk-mcp

by runapi-ai

Overview Schema Related Servers Score Discussions

TypeScript

Remote

Why This Package?

@runapi.ai/infinitetalk-mcp is a focused Model Context Protocol server for the InfiniteTalk model line on RunAPI. It gives MCP-compatible assistants direct access to 1 endpoint and 1 model variant without loading the full RunAPI catalog.

Use this per-model server when an agent should stay scoped to InfiniteTalk. Use @runapi.ai/mcp when one assistant should discover every RunAPI model line.

Related MCP server: @runapi.ai/gpt-4o-image-mcp

Install

Add it to Claude Code:

claude mcp add infinitetalk -s user -- npx -y @runapi.ai/infinitetalk-mcp

Use project scope when the server should be shared with a repository:

claude mcp add infinitetalk -s project -- npx -y @runapi.ai/infinitetalk-mcp

Codex, Cursor, Windsurf, VS Code, Roo Code, and other MCP hosts can use the same stdio command:

{
  "mcpServers": {
    "infinitetalk": {
      "command": "npx",
      "args": ["-y", "@runapi.ai/infinitetalk-mcp"]
    }
  }
}

check_pricing works before sign-in. For task creation and status polling, ask your assistant to call the login tool. It opens a browser login and saves credentials to ~/.config/runapi/config.json, the same file used by runapi login. Headless and CI hosts can still set RUNAPI_API_KEY before starting the MCP host.

Ready-made examples are in examples/ for Claude, Cursor, Windsurf, VS Code, and Roo Code.

Tools

Tool	Auth	Purpose
`audio_to_video`	Yes	Create an InfiniteTalk audio to video task and optionally wait for a terminal status. Returns the task id, status, and output URLs.
`get_task`	Yes	Fetch the current status and latest payload for an existing task.
`check_pricing`	No	Look up current pricing for a InfiniteTalk model and endpoint.

Models

InfiniteTalk covers 1 model variant across 1 endpoint. Each tool accepts the models listed for it:

Tool	Models
`audio_to_video`	`infinitetalk-from-audio`

Model availability can change between releases. Use check_pricing or the InfiniteTalk model page for the current catalog view.

Agent Prompts

Ask your assistant in natural language; it can inspect pricing, create the task, and return the task id plus output URLs.

Create a task

Run an InfiniteTalk audio to video task with RunAPI.

The assistant can call check_pricing, then audio_to_video, and return the task id, status, and output URLs.

Submit without waiting

Create the task but don't wait for it to finish.

The assistant calls the create tool with wait: false and returns the task id. Check on it later with get_task.

Check pricing before creating

Check current InfiniteTalk pricing, then create the task if it matches my request.

The assistant calls check_pricing and can link to the InfiniteTalk model page for the canonical catalog entry.

Configuration

The server resolves auth in this order:

RUNAPI_API_KEY environment variable, useful for headless and CI hosts
~/.config/runapi/config.json, created by the MCP login tool or runapi login
No key, which still allows check_pricing

The config file is normally managed by login. A pre-provisioned headless config can use:

{
  "apiKey": "your_runapi_key"
}

Do not commit real API keys.

Links

Resource	URL
InfiniteTalk model page	https://runapi.ai/models/infinitetalk
npm package	@runapi.ai/infinitetalk-mcp
GitHub repository	runapi-ai/infinitetalk-mcp
RunAPI MCP overview	runapi.ai/mcp
RunAPI docs	runapi.ai/docs

License

Licensed under the Apache License, Version 2.0.

Available Tools

4 tools

audio_to_videoB

Create a InfiniteTalk task on RunAPI (audio to video). Returns a task id, status, and output URLs.

ParametersJSON Schema

Name	Required	Description
`seed`	No
`wait`	No	Poll until the task reaches a terminal status.
`model`	No	RunAPI model slug for this model line.
`prompt`	No
`timeout_ms`	No
`callback_url`	No
`poll_interval_ms`	No
`source_audio_url`	Yes
`source_image_url`	Yes
`output_resolution`	No

TDQS

B3.2/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions return values (task id, status, output URLs) but does not disclose that this is an asynchronous task creation that may require polling or cost implications, nor how 'wait' and timeouts behave.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that is front-loaded and to the point, but it contains a minor grammatical error ('a InfiniteTalk') and omits details that would require additional sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 10 parameters, no annotations, and no output schema, the description is significantly under-specified. It provides a high-level purpose but lacks guidance on parameter usage, task lifecycle, error handling, or how to retrieve results via sibling tools.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 20% (only 'model' and 'wait' have descriptions). The description does not explain any parameters beyond the 'audio to video' phrase, which hints at the purpose but not the exact param formats or meanings.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates an InfiniteTalk task on RunAPI for audio-to-video conversion, and specifies return values. This clearly differentiates it from sibling tools like get_task and check_pricing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage by naming the operation and resource, but it does not explicitly state when to use this tool versus alternatives, nor does it mention any prerequisites or conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

check_pricingB

Look up RunAPI pricing for the infinitetalk model line.

ParametersJSON Schema

Name	Required	Description	Default
`model`	No	Model slug. Defaults to the line's primary model.
`action`	No	Endpoint name. Defaults to the endpoint that offers the model.

TDQS

B3.1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description is the sole source for behavioral traits. It only states the function without disclosing any side effects, return format, or permissions needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that efficiently communicates the tool's primary purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple lookup tool with optional parameters and no output schema, the description is adequate but could improve by hinting at the output structure or units.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with all parameters described and enumerated. The description adds no additional meaning beyond the schema, meeting the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('look up') and resource ('RunAPI pricing for the infinitetalk model line'), distinguishing it from sibling tools like audio_to_video (a different action) and get_task.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide any guidance on when to use this tool vs alternatives, nor does it mention prerequisites or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_taskA

Fetch the current status and latest result payload for a infinitetalk task.

ParametersJSON Schema

Name	Required	Description	Default
`action`	No	Asynchronous endpoint the task was created on. Defaults to the line's only asynchronous endpoint.
`task_id`	Yes	Task id returned when the task was created.

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses that the tool fetches status and result payload, adding basic return-info context. However, it does not describe error behavior, whether the call blocks, authentication needs, or rate limits. The added context is useful but not comprehensive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, focused sentence with no redundant information. It begins with the action and clearly states the object, making it easy to parse. No filler or unnecessary clauses.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two parameters, no output schema, and a simple retrieval function, the description adequately conveys the return contents (status and payload). It does not elaborate on error scenarios or edge cases, but given the tool's simplicity, this is a reasonable level of completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with clear descriptions for both task_id and action. The tool description adds no additional parameter meaning beyond what the schema already provides, so the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Fetch') and the resource ('current status and latest result payload for a infinitetask task'), which distinguishes it from sibling tools like audio_to_video (which creates tasks) and check_pricing. It is specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The purpose implies usage for checking task status, and siblings like audio_to_video suggest a create-then-fetch flow, but the description does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it. Guidance is minimal.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

loginA

Authenticate RunAPI by opening a browser PKCE login flow and saving the API key to ~/.config/runapi/config.json.

ParametersJSON Schema

Name	Required	Description	Default
`force`	No	Re-run browser login when the current credential comes from the local config file.

TDQS

A3.7/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses the interactive browser flow and config file writing, which is adequate. However, it omits potential failure modes (e.g., no browser available), side effects (overwrites existing config), or that user interaction is required.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-structured sentence conveys the core purpose and method. Every word adds value with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple login tool with one parameter and no output schema, the description covers the main behavior. However, it could be more complete by mentioning the expected outcome (e.g., 'returns a success message') or what happens if already authenticated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds no parameter information. The `force` parameter's meaning is already clear from its schema description. Baseline 3 is appropriate since the description does not need to repeat it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (authenticate), the target system (RunAPI), and the specific method (PKCE login flow with config file saving). It unambiguously differentiates from sibling tools (audio_to_video, check_pricing, get_task) which are unrelated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies this is the tool to use for authentication but does not explicitly state when to use it or when alternatives might be better. It lacks guidance on prerequisites or context (e.g., 'use this if you need an API key').

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

2 tool updatesv0.1.7Aug 5, 2026

Changedaudio_to_video6 fields changed
- addedInput schema / properties / callback_url
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / prompt
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / seed
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / source_audio_url / type
```
Added value: +"string"
```
- addedInput schema / properties / source_image_url / type
```
Added value: +"string"
```
- addedInput schema / required
```
Added value: +[
+  "source_image_url",
+  "source_audio_url"
+]
```

Changedget_task1 field changed

changedInput schema / properties / action / description

Previous value: -"Endpoint the task was created on. Defaults to the line's only endpoint."New value: +"Asynchronous endpoint the task was created on. Defaults to the line's only asynchronous endpoint."

1 tool updatev0.1.6Jul 13, 2026
- Addedlogin
3 tool updatesv0.1.0Jun 24, 2026
- First observedaudio_to_video
- First observedcheck_pricing
- First observedget_task

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.7/5.0

Disambiguation5/5

Each tool has a clearly distinct role: authentication, task creation, task status retrieval, and pricing lookup. No overlap or ambiguity between them.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivitySlowing

ResponsivenessSyncing

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

mcp-klingOAuth
io.github.AceDataCloud
MCP server for Kling AI video generation
Image & Video Processing AI & Machine Learning
21
mcp-wanOAuth
io.github.AceDataCloud
MCP server for Wan AI video generation
AI & Machine Learning Image & Video Processing
21
mcp-hailuoOAuth
io.github.AceDataCloud
MCP server for Hailuo (MiniMax) AI video generation
AI & Machine Learning Image & Video Processing
21
mcp-veoOAuth
io.github.AceDataCloud
MCP server for Google Veo AI video generation
Multimedia Processing Image & Video Processing Entertainment & Media
23

Related MCP Servers

@runapi.ai/gemini-omni-mcp
AI & Machine Learning Multimedia Processing
runapi-ai
A
license
A
quality
A
maintenance
MCP server for the Gemini Omni model line, enabling task creation (audio, character, text-to-video) and pricing checks through RunAPI.
Updated a month ago (2026-07-31 09:32 UTC)
6
70
Apache 2.0
@runapi.ai/gpt-4o-image-mcpofficial
AI & Machine Learning Image & Video Processing
runapi-ai
A
license
A
quality
A
maintenance
MCP server for GPT-4o Image model line, enabling text-to-image task creation, status polling, and pricing checks via RunAPI.
Updated a month ago (2026-07-31 09:32 UTC)
4
110
Apache 2.0
imagen-4-mcp
AI & Machine Learning Image & Video Processing
runapi-ai
A
license
A
quality
A
maintenance
RunAPI MCP server for the Imagen 4 model line. Create tasks, poll their status, and check pricing through a single RunAPI API key.
Updated a month ago (2026-07-31 09:34 UTC)
5
65
Apache 2.0
@runapi.ai/runway-aleph-mcpofficial
AI & Machine Learning Multimedia Processing
runapi-ai
A
license
A
quality
A
maintenance
MCP server for the Runway Aleph model line. Enables creating edit video tasks, polling status, and checking pricing through a single RunAPI API key.
Updated a month ago (2026-07-31 09:39 UTC)
4
66
Apache 2.0

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/runapi-ai/infinitetalk-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

Why This Package?

Install

Tools

Models

Agent Prompts

Create a task

Submit without waiting

Check pricing before creating

Configuration

Links

License

Available Tools

TDQS

TDQS

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

@runapi.ai/gemini-omni-mcp

@runapi.ai/gpt-4o-image-mcpofficial

imagen-4-mcp

@runapi.ai/runway-aleph-mcpofficial

Latest Blog Posts

MCP directory API