Overte Mcp

io.github.sandraschiPublished by GitHub account sandraschiv0.2.1Updated Oct 24, 2026

Overte (open-source Vircadia-lineage metaverse) Model Context Protocol server for domain administ...

VerifiedSTDIODesktop onlyDeveloper Tools Media & Design

Server details

Identifier: io.github.sandraschi/overte-mcp
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account sandraschi for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.sandraschi%2Foverte-mcp.svg)](https://sourceweft.com/mcp/io.github.sandraschi%2Foverte-mcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

An MCP server for Overte, the open-source social-VR platform, letting an assistant check domain status and spawn or script in-world entities.

What you can do: Check a running Overte domain-server's status, nodes and settings through its admin API on port 40100. Spawn in-world entities with position, scale and type, optionally made permanent across restarts. Inject JavaScript behavior scripts into entities through a WebSocket bridge. Request multi-step planning through the host's sampling support when available. A companion web dashboard adds entity, scripting, avatar, chat and log pages.
When to use it: Use it when you run an Overte domain and want an assistant to inspect its telemetry or create and script entities in the world, rather than editing them by hand in the client.
Requirements: Local process run with Python 3.12+ and uv; Bun for the web dashboard. Overte domain-server and Interface client must be installed separately. Entity spawning and script injection need a running Interface with the bridge script loaded; domain status needs only the domain-server.

Before you install

Entity spawning and script injection write to a live world and can persist across restarts when made permanent. Injected JavaScript runs inside the Overte client, so only inject scripts you trust. Responses are labeled live or simulated, so check that label before relying on results.

Installation

In SourceWeft

Open Overte Mcp in the dashboard and add it to a workspace.
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

overte-mcp

[License: MIT] [Python 3.12+] [Status: beta, core tools verified live]

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.

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-server on 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 (`bridge_not_connected`, `domain_unreachable`, ...); no simulated mode

Tools — 12 MCP tools (verified live against Overte 2026.04.1 unless noted):

Tool	Status
`overte_domain_status`	Verified live (2026-07-30): domain-server `/nodes.json` + `/settings.json` on port `40100`
`overte_bridge_status` / `overte_bridge_install`	New 2026-10-31: bridge mode (agent/interface) and headless install as a persistent script. See STATUS.md for live verification state.
`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_entity_update` / `delete` / `animate`	Live-only entity lifecycle (move/resize, delete, spin/bob/bounce)
`overte_nearby_entities` / `fixture_spawn`	Live world search + gripper test fixtures (box/cup/ball/table/chair)
`overte_sampling_assist`	Multi-step planning via `ctx.sample()` when host supports it
`overte_shutdown`	Orderly self-termination (`confirm=True`) + `POST /api/shutdown`

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
Inbox	`/inbox`	Server events needing attention (search/filter/sort/paginate)
Help	`/help`	Domain setup, hosting + invites, JS API reference

Quick Install

Claude Desktop (`.mcpb`) — Claude-only one-liner

One 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:

json

{  "mcpServers": {    "overte-mcp": {      "command": "uvx",      "args": ["--from", "git+https://github.com/sandraschi/overte-mcp.git", "overte-mcp"]    }  }}

{  "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)

Syncs 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

powershell

just lint      # Ruff + Biomejust test      # unit + e2ejust mcpb-pack # validate + pack Claude Desktop bundle

just lint      # Ruff + Biomejust test      # unit + e2ejust 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

Source: README.md at commit 1613544

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts