serious-editor
Related Servers
Alternatives to serious-editor
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceConnects MCP clients to a running hx-multianim game via DevBridge for scene inspection, state manipulation, input injection, and diagnostics.3845 npmBSD 3-Clause
- AlicenseBqualityDmaintenanceConnects MCP clients to a local browser-based map editor, enabling session discovery, map state inspection, item and actor queries, actor placement and movement, selection changes, deletion, and undo/redo operations. Supports STDIO, Streamable HTTP, and legacy HTTP+SSE transports through a local WebSocket bridge.10MIT
- AlicenseAqualityAmaintenanceConnects MCP clients directly to a live Godot editor, enabling AI assistants to build scenes, edit nodes, and control the editor through over 120 operations.4717,600 PyPI3,202MIT
- AlicenseBqualityCmaintenanceEnables MCP clients to control a running Unreal editor through its local bridge socket, exposing world, blueprint, material, media, vision, pipeline, and status tools. It resolves class names, verifies writes by reading them back, caps ordered pipelines, and reports unreachable or partial results instead of silently succeeding.7Business Source 1.1
- 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
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI agents to connect to a Unity/Tuanjie editor's Codely Bridge to inspect project state and perform editor operations such as managing GameObjects and assets, executing C# snippets, reading the console, and taking screenshots.26 npm7MIT
TDQS
Scored across 14 tools
Each tool targets a distinct lifecycle or resource: local status vs live ping, package listing vs entry reading, property existence vs property reading, and preview/apply/undo/status are clearly separated. Overlaps are explicitly clarified in the descriptions.
All tools use a consistent snake_case editor_ prefix, making the set predictable. A few names are noun phrases (editor_status, editor_selection, editor_edit_status) rather than strict verb_noun, but the convention is still coherent.
14 tools is within a reasonable range for a specialized editor bridge, and each tool maps to a distinct part of the inspection, connection, editing, or package-reading workflow. The surface does not feel padded or thin.
The set covers bridge setup/status, live connectivity, property inspection and safe edit lifecycle, package entry inspection, and logs. The main gap is persistence: edits are explicitly not saved, and broader entity CRUD or document discovery is absent, but core workflows are mostly covered.