Skip to main content
Glama
finasteos

GameDev MCP Hub

by finasteos

Related Servers

Alternatives to GameDev MCP Hub

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Self-hosted MCP gateway that aggregates many MCP servers into a single endpoint for AI clients, supporting hosted, local stdio, and Git-sourced MCPs.
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Aggregates multiple MCP servers and custom Python tools behind a single endpoint, with intelligent context and tool discovery for AI agents.
      -
    • A
      license
      A
      quality
      C
      maintenance
      Aggregates multiple MCP servers into a single interface, reducing token overhead and simplifying tool management for LLMs.
      6
      74 npm
      18
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      The 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.
      46
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues