GameDev MCP Hub
Related Servers
Alternatives to GameDev MCP Hub
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceSelf-hosted MCP gateway that aggregates many MCP servers into a single endpoint for AI clients, supporting hosted, local stdio, and Git-sourced MCPs.2MIT
- FlicenseNot gradedqualityDmaintenanceAggregates multiple MCP servers and custom Python tools behind a single endpoint, with intelligent context and tool discovery for AI agents.-

MetaMCPofficial
AlicenseAqualityCmaintenanceAggregates multiple MCP servers into a single interface, reducing token overhead and simplifying tool management for LLMs.674 npm18Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable AI coding tools to dispatch tasks in parallel to multiple installed AI CLIs with automatic failover, plus run multi-AI discussions and cross-reviews, hand code off between tools, manage shared workspaces, and inspect token usage, traffic, clients, and task memory. Also exposes image recognition (OCR/vision), tool and client administration, and log access through a single local hub.7 npmMIT
- AlicenseNot gradedqualityAmaintenanceThe most advanced MCP server for Godot Editor that lets AI assistants operate directly inside your running Godot project for scene creation, script generation, UI authoring, and more.46MIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server that connects AI coding agents (Claude Code, Codex, Cursor, etc.) on the same machine via a shared message bus, enabling them to chat, delegate tasks, and collaborate privately without cloud or internet.73 npmMIT
TDQS
Scored across 5 tools
The tools are mostly distinct: search vs list vs analytics vs token check vs routing all have clear purposes. The only slight overlap is between 'search_tools' and 'route_task' (both help find tools), though route_task takes natural-language and adds routing logic, so the boundary is mostly clear.
All tools follow a consistent verb_noun snake_case pattern: search_tools, list_servers, get_analytics, check_tokens, route_task. Every name uses a clear action verb followed by a noun, with no style mixing.
Five tools is a reasonable, well-scoped count for a hub/meta-coordination server. Each tool addresses a distinct purpose (discovery, listing, analytics, token management, task routing). It sits slightly on the sparse side but is appropriate for the coordination-focused role with no apparent need for more.
The surface covers discovery, listing, analytics, token monitoring, and routing, which forms a coherent hub workflow. However, there's no tool to register/disconnect a server, no way to inspect a specific tool's detail beyond search, and no configuration or error-reporting capability, leaving some operational gaps for a hub that manages connected servers.