Realtime Avatar

io.github.theinfluencecompanyv0.27.0Updated Oct 5, 2026

Read your Realtime Avatar avatars, credit balance and session bill from a coding agent.

VerifiedSTDIODesktop onlyAI & MLFinanceMedia & Design

Overview

AI-generated overview

Lets a coding agent read Realtime Avatar avatars, credit balance and session bills, and optionally create avatars and start billed calls.

What it does
An MCP server for the Realtime Avatar platform. Read-only tools list avatars and mark which are usable live, fetch one avatar's detail, report credit balance and reserved amounts, itemise past sessions with duration and cost, and show an avatar's clip library. With writes enabled it can set a resting loop, declare a full clip library, upload a local file or register a remote asset, build an avatar from one still image, and mint a live session to verify an integration.
When to use it
Use it when an agent needs real avatar ids, balances or billing data instead of guessing them from documentation, or when you want an agent to create avatars and clip libraries and to verify a live integration. It is a desktop-only local process, so it suits a developer machine rather than a hosted environment.
Requirements
Runs locally over stdio via npx from the npm package realtime-avatar-mcp, so Node.js is needed. Requires a Realtime Avatar API key in REALTIME_AVATAR_API_KEY; a free sandbox key is available. Write tools stay off unless REALTIME_AVATAR_ALLOW_WRITES is set to 1. Network access to the Realtime Avatar service is required.
Before you install
REALTIME_AVATAR_API_KEY is a secret and should not be shared. Write tools are gated behind REALTIME_AVATAR_ALLOW_WRITES=1; start_call bills per second and refuses tic_live_ keys, so a production key cannot be used for it. upload_asset reads any absolute path on the machine running the server. set_clip_library replaces the whole clip set, so anything omitted stops being served.

Installation

In SourceWeft

  1. Open Realtime Avatar in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

realtime-avatar-mcp

Published on npm as realtime-avatar-mcp — run it with npx, never installed into an app.

An MCP server for Realtime Avatar. AGENTS.md tells a coding agent what the API is; this lets it look — at your avatars, your balance, your bill — instead of guessing ids and inventing shapes.

jsonc
{  "mcpServers": {    "realtime-avatar": {      "command": "npx",      "args": ["-y", "realtime-avatar-mcp"],      "env": { "REALTIME_AVATAR_API_KEY": "tic_test_…" }    }  }}

Full page, including the write tools and what they cost: https://realtimeavatar.ai/docs/mcp. You need an API key first — a sandbox key is free and needs no card.

Working on it in this repo? npm run build, then point command at node with args: ["/abs/path/to/realtime-avatar-sdk/libs/mcp/dist/bin.js"].

Tools

Tool
list_avatarsEvery avatar with the id you pass to startCall, and which are usable live
get_avatarFull detail for one
credit_balanceBalance, and what in-flight calls have reserved
list_sessionsThe itemised bill — when each session ran, how long, what it cost
list_clipsAn avatar's clip library: every clip, its status, the revision and rest pose

With REALTIME_AVATAR_ALLOW_WRITES=1:

ToolBills?
set_loopRe-direct her resting loop from a new descriptionno
set_clip_libraryDeclare an avatar's full clip set as JSON — the platform renders itno
upload_assetUpload a file from this machine's disk, get a public URLno
create_remote_assetRegister a file already on the internet — no local copyno
create_avatar_from_imageBuild an avatar from ONE still — the loop is generatedno
create_avatar_from_videoDeprecated. Closed to new callers (422). Use the image toolno
start_callMint a live session to verify an integrationyes, per second

Spending money is opt-in, and twice gated

The five tools above are read-only, and each carries readOnlyHint so a host can gate on the annotation rather than on a name it has to recognise. Pointed at a production key, this server is no more dangerous than a dashboard you left open.

REALTIME_AVATAR_ALLOW_WRITES=1 enables the write tools. Only start_call costs credits, and it refuses a tic_live_ key outright — an operator who armed writes against a test key and later swapped in a production one should not discover it by being billed. Two independent gates, because one is a single mistake away from being none.

Two things to understand before arming writes:

  • upload_asset reads local disk. It opens whatever absolute path the agent names, on the machine running the server. Relative paths are refused rather than resolved against whatever directory the host spawned it in.
  • The clip declaration retires by omission. set_clip_library takes the COMPLETE set; anything missing from it stops being served. Its plan reports kept/queued/retired clips. Declare source.motionPrompt or source.assetId; the platform hosts and prepares media. The avatar's stored source is the implicit rest state — never declared, so the id primary is reserved.

Why an MCP server at all

An agent that reads docs still guesses. ava_… ids cannot be inferred, and the failures that cost the most time here are invisible in a type signature: a reshaped connection payload is rejected by the browser client; a 429 on a call is the queue, not an error; the resting loop is the avatar's source rather than a library clip, so no declaration changes it.

list_avatars marks which avatars are actually usable. The server's instructions carry the relay rule and the per-second billing model. That is context an agent cannot derive, delivered where it is about to act.

Source: libs/mcp/README.md at commit 9e56486

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v0.27.0LatestOct 5, 2026