overte-mcp
Related Servers
Alternatives to overte-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceOpen-source, engine-agnostic MCP server shared by Unity-MCP, Godot-MCP, and Unreal-MCP.13Apache 2.0
- FlicenseCqualityBmaintenanceCustom MCP server for automating Godot Engine 4.x, enabling direct scene manipulation, node inspection, GDScript injection, and runtime testing via a WebSocket bridge.63-
- FlicenseAqualityCmaintenanceAn MCP server that lets an LLM agent drive a TeleportXR headless client: connect to Teleport servers, move an avatar, send input, and inspect geometry.12-
- 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.-
- AlicenseAqualityBmaintenanceMCP 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
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.