overte-mcp
Query and control a live Overte social-VR domain through MCP tools, with a companion React dashboard.
Inspect domain status: fetch connected-node telemetry and settings from an Overte domain-server (
/nodes.json,/settings.json), optionally with HTTP Basic Auth.Spawn entities/models: create Box, Sphere, Web, or Model entities at given positions/scales, optionally with GLB/FBX URLs, attached JS scripts, and
permanent=Truefor cross-restart persistence.Inject behavior scripts: attach JavaScript scripts to existing entities by UUID, with optional metadata injected into script scope.
Plan multi-step operations: use MCP sampling (
ctx.sample()) for guidance on complex Overte workflows when the host supports it.Manage live entities (per README): update/delete/animate entities, find nearby entities, spawn test fixtures, check/install the WebSocket bridge, and shut down the server.
Use the dashboard: view domain status, avatars, entities, scripting, chat, settings, tools, skills, logs, inbox, and help pages.
Note: tool descriptions mention clearly labeled simulated fallbacks when no domain-server or bridge is reachable, while the README states there is no simulated mode.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@overte-mcp check my Overte domain status"
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.
overte-mcp
What this wraps
An MCP server for Overte, the open-source social-VR
platform — a C++ desktop client ("Interface") + domain-server + entity-server,
descended from High Fidelity's codebase. Not the same thing as current
"Vircadia" — see docs/WRAPPEE.md for the full
disambiguation and official links (site, docs, community). Complements the
fleet's other virtual-world servers: resonite-mcp, vrchat-mcp,
godot-mcp, unity3d-mcp, gazebo-mcp.
Plus a companion React web dashboard.
Related MCP server: Learn MCP Server
Local sandbox or join a domain
Two ways to be in a world — the dashboard keeps them separate on purpose:
Local sandbox (default): your own
domain-serveron this machine (localhost:40100). Private, free, and the only setup where the dashboard's Start/Stop buttons can launch things for you.Join a domain: point the dashboard's Watching switcher at someone else's domain-server (host + admin port) to monitor it, and join it in Interface with Connect to Domain…. You get admin/scripting power there only if they gave you credentials.
One rule for both: spawning, injecting, and animating always act through the
bridge, which lives in whatever domain your assignment-client or Interface
joined. The Watching switcher changes which domain you look at; your spawns
land where you stand. To flip it around — host a domain others can join,
gate it to specific people, and send hifi:// invites — see
docs/ONBOARDING.md ("Hosting a domain others can join")
and the Help Hub in the dashboard.
What You Can Do
How it runs: Overte (domain-server + assignment-client, optionally Interface) is a
separate application you install yourself, never bundled. Entity work runs through a
bridge script inside Overte's script engine. Since 2026-10-31 the bridge runs headless
as a domain persistent script on an assignment-client: no GUI, no logged-in user
(overte_bridge_install sets it up). Loading it in the desktop Interface client still
works when you want to watch. See docs/ONBOARDING.md.
Direction | Artifacts | Notes |
Hands-in | Entity properties (position, scale, type), JS behavior scripts, GLB/FBX/OBJ model URLs | Via MCP tool calls or the dashboard's Entities/Scripting pages |
Hands-out | Live domain-server telemetry, spawned in-world entities, animated/scripted entities | Real result or an error saying why ( |
Tools — 12 MCP tools (verified live against Overte 2026.04.1 unless noted):
Tool | Status |
| Verified live (2026-07-30): domain-server |
| New 2026-10-31: bridge mode (agent/interface) and headless install as a persistent script. See STATUS.md for live verification state. |
| Verified live — in-world entity spawning via WebSocket bridge; |
| Verified live — in-world JS behavior injection via WebSocket bridge |
| Live-only entity lifecycle (move/resize, delete, spin/bob/bounce) |
| Live world search + gripper test fixtures (box/cup/ball/table/chair) |
| Multi-step planning via |
| Orderly self-termination ( |
Dashboard pages:
Page | Route | Features |
Dashboard |
| Domain status, node list, settings viewer |
Avatars |
| Connected avatar-mixer/agent nodes |
Entities |
| Spawn form + entity explorer |
Scripting |
| JS code editor + script injection |
Chat |
| Skill-first LLM chat with 4 personalities |
Settings |
| Backend health + LLM provider detection |
Tools |
| Dynamic tool discovery + search |
Skills |
| Skill content viewer (markdown) |
Logs |
| Ring-buffer log viewer with level filter |
Inbox |
| Server events needing attention (search/filter/sort/paginate) |
Help |
| Domain setup, hosting + invites, JS API reference |
Quick Install
Claude Desktop (.mcpb) — Claude-only one-liner
irm https://github.com/sandraschi/overte-mcp/releases/latest/download/install.ps1 | iexOne command: downloads the latest .mcpb, installs Python/uv if missing, and registers the bundle. Claude Desktop only.
Other clients (Cursor / VS Code / Codex / Opencode) — no bundle needed:
{
"mcpServers": {
"overte-mcp": {
"command": "uvx",
"args": ["--from", "git+https://github.com/sandraschi/overte-mcp.git", "overte-mcp"]
}
}
}From source: just mcpb-pack → dist/overte-mcp.mcpb, then drag the .mcpb into Claude Desktop. Full install paths: INSTALL.md.
Full stack (dashboard + bridge)
./start.ps1Syncs deps, starts FastAPI backend (11110) and Vite dashboard (11111),
opens the browser. Then start Overte domain-server.exe and
assignment-client.exe -n 9, and run overte_bridge_install once. Or let
just e2e-headless do it all and report pass/fail. See
docs/ONBOARDING.md.
Example Prompts
"What's the status of my Overte domain?"
"Spawn a permanent box entity at the origin"
"Attach the dance script to that entity"
Lint / test
just lint # Ruff + Biome
just test # unit + e2e
just mcpb-pack # validate + pack Claude Desktop bundleDocumentation
docs/WRAPPEE.md — what Overte is, disambiguation from Vircadia, official links
docs/ARCHITECTURE.md — data flow, ports, WebSocket bridge
INSTALL.md — Overte setup, MCPB, Claude Desktop config
STATUS.md — current verification status, remaining work
ASSESSMENT.md — fleet audit findings and improvement plan
PROJECT_PAGE.md — roadmap and task tracker
CHANGELOG.md — release notes
docs/ONBOARDING.md — first-time Overte + bridge setup
docs/CONFIGURATION.md — env vars, ports
docs/DEVELOPMENT.md — dev setup, contributing
docs/TOOLS.md — full MCP tool reference
docs/TROUBLESHOOTING.md — common issues
llms.txt / llms-full.txt — LLM index + full corpus
mcpb/README.md — Claude Desktop bundle layout
Requirements
Python 3.12+ with
uvBun (webapp + Biome)
Overte Client + Server installed separately for live domain + bridge features
License
MIT
Available Tools
4 toolsoverte_domain_statusA
Retrieve connected-node telemetry and settings from an Overte Domain Server.
Real live path against /nodes.json and /settings.json. Falls back to clearly labeled simulated data if no domain-server is reachable.
Return Format
{"success": bool, "message": str, "data": {"source": str, "domain": {...}}}
Examples
overte_domain_status(host="localhost", port=40100) overte_domain_status(host="192.168.1.100", port=40100, username="admin", password="admin")
Inputs: ctx, host, port, password, +1 more. Returns: object
overte_entity_spawnA
Spawn a virtual object or 3D GLB model in-world at the specified coordinates.
Live when scripts/overte-mcp-bridge.js is connected to the FastAPI WS hub; otherwise returns a clearly labeled simulated confirmation.
Return Format
{"success": bool, "message": str, "data": {"source": str, "entity": {...}}}
Examples
overte_entity_spawn(name="MyBox") overte_entity_spawn(name="Tree", entity_type="Model", model_url="https://example.com/tree.glb", position=[10, 0, -5])
Inputs: name (required), ctx, type, scale, +4 more. Returns: object
overte_sampling_assistA
Get multi-step Overte operation guidance via MCP sampling (FastMCP 3.1+).
Uses ctx.sample when the host exposes sampling; returns structured error otherwise. Recommends tool calls and sequencing for complex goals.
Return Format
{"success": bool, "message": str, "data": {"plan": str, "sampling_used": bool}}
Examples
overte_sampling_assist(goal="Set up a domain-server and spawn a welcome entity")
Inputs: goal (required), ctx. Returns: object
overte_script_injectA
Inject a JavaScript script to govern behavior of an in-world entity.
Live when the Overte bridge WebSocket client is connected; otherwise returns a clearly labeled simulated confirmation.
Return Format
{"success": bool, "message": str, "data": {"source": str, "script": {...}}}
Examples
overte_script_inject(entity_id="abc-123-def", script_url="https://example.com/behavior.js") overte_script_inject(entity_id="abc-123-def", script_url="https://example.com/click.js", script_data={"color": "red"})
Inputs: entity_id (required), script_url (required), ctx, script_data. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool targets a distinct concern: script injection, entity spawning, domain status, and sampling-based guidance. No two tools overlap in purpose.
All tools share the overte_ prefix and mostly follow a noun_verb pattern (script_inject, entity_spawn, sampling_assist), with one exception (domain_status being noun_noun). This is a minor deviation from an otherwise consistent scheme.
Four tools is a reasonable, focused scope for an Overte bridge server. Each tool serves a clear function without unnecessary bloat.
The domain is clearly Overte virtual world management, but the surface is notably incomplete: entity spawning exists but there are no tools to list, update, or delete entities, and script injection exists without corresponding script removal or listing. This leaves significant gaps in typical lifecycle workflows.
Maintenance
Related MCP Connectors
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
Official remote MCP server bridge for Muumuu Domain.
MCP server for understanding Javascript internals from ECMAScript specification.
A MCP server built for developers enabling Git based project management with project and personal…
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA minimal WebSocket-based MCP server implementation that enables modern tool integrations with VSCode, Claude, and other applications.6 npmISC
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server designed for learning and experimentation. It provides a foundational setup for developers to build, run, and debug MCP server implementations using Node.js.-
- AlicenseNot gradedqualityBmaintenanceOpen-source, engine-agnostic MCP server shared by Unity-MCP, Godot-MCP, and Unreal-MCP. Additionally you can use AI Game Dev app (https://ai-game.dev) to generate images, video, audio, 3D, rig, animation and much more.19Apache 2.0
- AlicenseAqualityDmaintenanceMCP server that lets an LLM agent drive StableProjectorz, a 3D modeling app, by inspecting the loaded model, app state, viewport screenshots, and triggering UI actions via a loopback socket bridge.11MIT