About overte-mcp
overte-mcp connects Overte domain administration and in-world entity operations to MCP for Overte administrators and creators. It combines domain status queries, entity spawning, and script injection with a React web dashboard.
Key features
- 01Query domain status and nodes
- 02Spawn persistent world entities
- 03Inject entity behavior scripts
- 04View domain and entities in a web dashboard
- 05Label live or simulated results
Use cases
- 01Check Overte domain and node status
- 02Spawn a box entity at the origin
- 03Attach JavaScript behavior to an entity
- 04Inspect entities and inject scripts in the dashboard
MCP support
It provides MCP tools to query Overte domain status, spawn entities, and inject scripts. Entity spawning and script injection require a running Interface client with the bridge script loaded.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEoverte-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.
What You Can Do
How it runs: Overte (domain-server + Interface) is a separate
application you install yourself — never bundled. overte_domain_status
works against just the domain-server (no GUI needed). overte_entity_spawn
and overte_script_inject need a running Interface client with
scripts/overte-mcp-bridge.js loaded, because Overte's entity-server has no
plain HTTP "create entity" endpoint — only Interface's JavaScript API can do
that. See docs/ONBOARDING.md for first-time setup.
| 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 | Every response labeled source: "live" or source: "simulated" — never a silent fake success |
Tools — all three core tools verified live against Overte 2026.04.1 (2026-07-30):
| Tool | Status |
|---|---|
overte_domain_status | Verified live — real domain-server /nodes.json + /settings.json admin API on port 40100 |
overte_entity_spawn | Verified live — in-world entity spawning via WebSocket bridge; permanent=True for cross-restart persistence |
overte_script_inject | Verified live — in-world JS behavior injection via WebSocket bridge |
overte_sampling_assist | Multi-step planning via ctx.sample() when host supports it |
Dashboard pages:
| Page | Route | Features |
|---|---|---|
| Dashboard | / | Domain status, node list, settings viewer |
| Avatars | /avatars | Connected avatar-mixer/agent nodes |
| Entities | /entities | Spawn form + entity explorer |
| Scripting | /scripting | JS code editor + script injection |
| Chat | /chat | Skill-first LLM chat with 4 personalities |
| Settings | /settings | Backend health + LLM provider detection |
| Tools | /tools | Dynamic tool discovery + search |
| Skills | /skills | Skill content viewer (markdown) |
| Logs | /logs | Ring-buffer log viewer with level filter |
| Help | /help | Domain setup + JS API reference |
Quick Install
Claude Desktop (.mcpb)
- Build:
just mcpb-pack→dist/overte-mcp.mcpb - Drag the
.mcpbinto Claude Desktop (needs Python 3.12+ anduvon PATH).
Stdio without MCPB: uv run overte-mcp. Full install paths: INSTALL.md.
Full stack (dashboard + bridge)
./start.ps1
Syncs deps, starts FastAPI backend (11110) and Vite dashboard (11111),
opens the browser. Then start Overte domain-server.exe, open Interface,
load scripts/overte-mcp-bridge.js for live spawn/inject — 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 bundle
Documentation
- 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
uv - Bun (webapp + Biome)
- Overte Client + Server installed separately for live domain + bridge features
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.