Skip to main content
Glama
Sign In
infinitetalk-mcp

infinitetalk-mcp

by runapi-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
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:

  1. RUNAPI_API_KEY environment variable, useful for headless and CI hosts

  2. ~/.config/runapi/config.json, created by the MCP login tool or runapi login

  3. 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.

Inputs: source_audio_url (required), source_image_url (required), seed, wait, +6 more.

check_pricingC

Look up RunAPI pricing for the infinitetalk model line.

Inputs: model, action.

get_taskB

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

Inputs: task_id (required), action.

loginA

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

Inputs: force.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Resources

    Related MCP Connectors

    Related MCP Servers