REA
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Description from the maker (original English)
Read your Realtime Avatar avatars, credit balance and session bill from a coding agent.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
REALTIME_AVATAR_API_KEY, REALTIME_AVATAR_ALLOW_WRITESValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"realtime-avatar": {
"command": "npx",
"args": [
"-y",
"realtime-avatar-mcp"
],
"env": {
"REALTIME_AVATAR_API_KEY": "your-value",
"REALTIME_AVATAR_ALLOW_WRITES": "your-value"
}
}
}
}Run this in your terminal
claude mcp add realtime-avatar --env REALTIME_AVATAR_API_KEY=your-value --env REALTIME_AVATAR_ALLOW_WRITES=your-value -- npx -y realtime-avatar-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"realtime-avatar": {
"command": "npx",
"args": [
"-y",
"realtime-avatar-mcp"
],
"env": {
"REALTIME_AVATAR_API_KEY": "your-value",
"REALTIME_AVATAR_ALLOW_WRITES": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"realtime-avatar": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"realtime-avatar-mcp"
],
"env": {
"REALTIME_AVATAR_API_KEY": "your-value",
"REALTIME_AVATAR_ALLOW_WRITES": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
REALTIME_AVATAR_ALLOW_WRITES envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 10, 2026
The registry name was verified with the GitHub account theinfluencecompany, which owns the repo
Code last changed yesterday
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 of 2 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: REALTIME_AVATAR_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (0.37.0) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: REA, Netdata, Front-End Checklist
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Real-time infrastructure monitoring with metrics, logs, alerts, and ML-based anomaly detection.
Review frontend code and live pages against 386 quality-gated web development rules.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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.
{
"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"].
| Tool | |
|---|---|
list_avatars | Every avatar with the id you pass to startCall, and which are usable live |
get_avatar | Full detail for one |
credit_balance | Balance, and what in-flight calls have reserved |
list_sessions | The itemised bill — when each session ran, how long, what it cost |
list_clips | An avatar's clip library: every clip, its status, the revision and rest pose |
With REALTIME_AVATAR_ALLOW_WRITES=1:
| Tool | Bills? | |
|---|---|---|
set_loop | Re-direct her resting loop from a new description | no |
set_clip_library | Declare an avatar's full clip set as JSON — the platform renders it | no |
upload_asset | Upload a file from this machine's disk, get a public URL | no |
create_remote_asset | Register a file already on the internet — no local copy | no |
create_avatar_from_image | Build an avatar from ONE still — the loop is generated | no |
create_avatar_from_video | Deprecated. Closed to new callers (422). Use the image tool | no |
start_call | Mint a live session to verify an integration | yes, per second |
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:
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.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.