horizOn MCP Server
OfficialRelated Servers
Alternatives to horizOn MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with access to the complete Godot Engine documentation, enabling developers to get answers about Godot classes, tutorials, and features directly in their chat interface.75MIT
- AlicenseAqualityBmaintenancePublish web games on Gamealia from your AI coding assistant: analyze the project, integrate the SDK (or migrate from Poki/CrazyGames), run a desktop and mobile browser autotest, write the listing and upload the build for review. Developers keep 60-70% of the ad revenue, no exclusivity.2262,284 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides a comprehensive integration between LLMs and the Godot Engine, enabling AI assistants to intelligently manipulate project files, scripts, and the live editor. It supports advanced workflows including version-aware documentation querying, automated E2E game testing, and real-time visual context capture.21 npm26MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Godot game projects through real-time error detection, automated testing, code analysis, and safe git-based patching. Provides comprehensive project context and development workflow automation for Godot developers.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding tools to connect and authorize local game projects, then drive source edits, validation, preview, version saving, and mode-based creation workflows.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to build, run, and debug Godot projects by editing scenes and scripts, inspecting live game state, injecting input, capturing viewports, and examining native debugger state through 42 tools.European Union Public 1.2
TDQS
Scored across 120 tools
Most tools map cleanly to a resource+action pair, and the descriptions are unusually explicit about 'Use when'/'Not for'. However, there are real collisions: horizon_get_marketplace and horizon_get_marketplace_limits share literally the same described purpose, and horizon_get_shared_collections vs horizon_get_shared_usage vs horizon_query_shared_objects have near-identical descriptions. With 120 tools, an agent must also distinguish many closely-related lifecycle verbs (e.g. start_match_ranked_run vs start_run vs start_match).
Every tool uses the horizon_namespace with a consistent snake_case verb_noun pattern (get_, create_, update_, delete_, list_, submit_, cancel_, accept_). Singular/plural resource names are used predictably (get_item vs get_items). No camelCase or ad-hoc verb mixing.
120 tools is far beyond what an agent can reliably navigate in one surface, placing it in the extreme-mismatch band. Even though the server legitimately spans many subsystems (accounts, groups, friends, inventory, marketplace, chat, matches, leaderboards, cloud save, stats), each domain could be exposed as a smaller focused endpoint set.
Coverage is remarkably thorough: full CRUD plus lifecycle and reconciliation for social, group, inventory, marketplace, chat, matches, leaderboards, validated runs, inbox, profile, cloud save, crash reporting, localization and email. Minor gaps exist (e.g. no explicit evidence-download/delete, limited chat moderation tooling), but nearly every workflow has a complete path with read-after-write recovery tools.