GECK MCP
Related Servers
Alternatives to GECK MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA comprehensive MCP server providing 41 tools for complete Roblox Studio control, enabling safe script editing with syntax checking, instance manipulation, and backup features directly from Claude Code or any MCP-compatible AI assistant.1MIT
- AlicenseBqualityDmaintenanceAdvanced MCP server for Godot 4.6+ with 63 professional tools, enabling AI-assisted game development with backup/rollback, deep script validation, and project health diagnostics.63228 npm5MIT
- AlicenseNot gradedqualityBmaintenanceA production MCP integration that lets AI agents control Roblox Studio to autonomously build, test, and debug Roblox games. Provides 39 tools for explorer control, script management, terrain generation, and autonomous testing.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to procedurally generate, transform, inspect, and export 3D meshes and scenes through MCP tools.MIT
- AlicenseNot gradedqualityAmaintenanceEnables ChatGPT to inspect and edit local projects through a secure MCP interface, offering workspace management, file operations, git integration, and safe command execution.5MIT
- FlicenseAqualityDmaintenanceProvides AI assistants with tools to launch the Godot editor, run projects, manipulate scenes, manage scripts, and control node properties through a standardized MCP interface.21-
TDQS
Scored across 46 tools
Several tools have overlapping or near-duplicate purposes, such as geck_esp_patch_ref_to_status_bar and geck_esp_patch_ref_to_status_bar_offset, both legacy planning-only tools, and geck_list_view_rows/geck_find_list_rows plus geck_active_plugin/geck_plugin_status. While the set covers distinct subsystems, an agent would frequently struggle to pick the correct tool among these overlapping refs, status, and planning operations.
Most tools follow a readable geck_ prefix with snake_case, but verb placement is inconsistent: some are verb_noun like geck_list_plugins, while others are subsystem_verb like geck_cell_select or noun phrases like geck_plugin_status, geck_status_bar, and geck_placement_report. The names remain readable, but the mixed conventions make the surface less predictable.
With 46 tools, this server is well beyond the range where each tool clearly earns its place, and it includes legacy planning-only tools plus near-duplicate ref/status operations. It is not quite the 50+ extreme, but it is over-scoped and would benefit from consolidation.
The server covers a full placed-reference lifecycle including list, patch, delete, nearby search, and create via render, alongside plugin management, load order, transactions, UI automation, and Cell/Object window operations. Gaps like direct editing of non-reference records are minor and workable through the included UI automation tools.