three.ws Assistant Widget runs on your own machine — the client starts it, so there is no endpoint to ping. 83 installs a week from npm. Last commit 1 Nov 2026.
Generate a paste-ready embed for a floating 3D avatar chatbot on any website.
We read the source, 3 h ago · rules 995398eba69f
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
'http://metadata.google.internal/computeMetadata/v1/instance/service-accounts/default/token',
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const r = await redis.eval(
filePath = path.join(ROOT_PUBLIC, url);
const proc = spawn(ffmpegPath(), ['-hide_banner', '-loglevel', 'error', '-i', 'pipe:0', ...args, 'pipe:1']);
const [row] = await sql`SELECT voice_provider, voice_id FROM agent_identities WHERE id = ${agentId}`.catch(() => []);
return subprocess.run(
exec(compile(job["code"], "<three-ws-blender-mcp>", "exec"), namespace)
if (reset) { state.cursor = null; state.total = 0; grid.innerHTML = skeletons(); stateEl.hidden = true; }
'UklGRmQBAABXQVZFZm10IBAAAAABAAEAQB8AAIA+AAACABAAZGF0YUABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA…
const TELEGRAM_API = 'https://api.telegram.org';
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch three.ws Assistant Widget and you get told the day something new turns up.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add assistant-widget -- npx -y @three-ws/assistant-mcp
{
"mcpServers": {
"assistant-widget": {
"command": "npx",
"args": [
"-y",
"@three-ws/assistant-mcp"
]
}
}
}
[mcp_servers.assistant-widget]
command = "npx"
args = ["-y", "@three-ws/assistant-mcp"]
{
"mcpServers": {
"assistant-widget": {
"command": "npx",
"args": [
"-y",
"@three-ws/assistant-mcp"
]
}
}
}
{
"servers": {
"assistant-widget": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@three-ws/assistant-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
THREE_WS_BASE (Origin used in the generated embed URLs (script src, frame URL, builder link). Override only when targeting a preview or self-hosted three.ws deployment).
Ask any website's AI concierge a grounded question, and generate the embed to add one to a site.
three.ws 3D avatars in your agent: render a live, interactive 3D avatar inline, or get an embed.
Embed an AI chat widget on your website from your coding agent: provision, configure, get snippet.
3D avatars, embeds, glTF tools, agent memory, and on-chain agent identity from three.ws.
Gets a website ready for AI assistants: robots.txt fixed, llms.txt drafted, citable gaps listed.
Instant fence quotes for contractor websites: create the account, set pricing, get the embed.
Writing Assistant Ai tools for AI agents. Capabilities: generate headlines, score readability
Free text/image → 3D: generate, rig, avatar-ify, and refine GLB models. No auth, no payment.
Answers built from our own checks of this server.