Hermes_WorldKit_MCP
Related Servers
Alternatives to Hermes_WorldKit_MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides a secure, authenticated MCP bridge to control a local Godot editor from Cursor, enabling scene/node management, script validation, editor diagnostics, and runtime inspection through a whitelisted set of tools.MIT
- AlicenseBqualityCmaintenanceConnects MCP-capable AI clients to a running Godot 4 editor for scene, node, project, and debug runtime operations via a local-first architecture.361MIT
- AlicenseAqualityBmaintenanceConnects MCP clients directly to a live Godot editor, enabling AI assistants to build scenes, edit nodes, and control the editor through over 120 operations.4730,790 PyPI3,482MIT
- AlicenseAqualityCmaintenanceMCP bridge between an AI assistant and the Godot editor, enabling control via 6 tools (call methods, run GDScript, screenshots, etc.) over WebSocket.1011 npm3MIT
- AlicenseDqualityCmaintenanceEnables AI clients to control and inspect a Unity Editor through MCP tools for scene and play-mode operations, logs, screenshots, assertions, Lua execution, UI interaction, world observation, and bridge management; advanced UI/Lua/world features require project-specific adapters.41MIT
- AlicenseCqualityCmaintenanceEnables MCP clients to inspect, validate, test, export, and query Godot projects, including live state from an open editor via a bridge addon.2012 npmMIT
TDQS
Scored across 5 tools
Each tool addresses a distinct concern: connection status, capability discovery, scene content, current selection, and changing selection. The two node-related tools are separated by summary versus selected state, and the action verb in select_node makes its purpose clear.
All tools share a consistent worldkit_ prefix and snake_case style, which makes them predictable. However, most names are noun-like while select_node is the only verb-led name, so the pattern is not perfectly uniform.
Five tools is a tight, well-scoped set for a safe editor bridge. Each tool covers a necessary operation without redundancy.
The surface covers the core read-only workflow: verify connection, discover capabilities, summarize the scene, inspect selected nodes, and change selection. Minor gaps like deselecting or retrieving a specific node's full details are absent but are not fatal for the apparent safe-introspection purpose.