Glitch MCP
OfficialRelated Servers
Alternatives to Glitch MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to audit Steam store pages for algorithmic health, forecast sales cones with P10/P50/P90 scenarios, and retrieve genre benchmarks for indie game market analysis.3MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and coding assistants to access live Steam market intelligence, including app search, store details, player-count trends, review mining, and news digests.23 npm1MIT
- 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

Dovetail MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceConnects AI tools to the Dovetail API, enabling them to interact with Dovetail features.1,439 npm8MIT
glade-mcpofficial
AlicenseNot gradedqualityAmaintenanceConnect any MCP-compatible AI client (Claude Code, Cursor, Windsurf) to Unity or Godot. 300+ granular tools, an editor aware system prompt, game design document project context, script semantic search, and skill calibration.225MIT- AlicenseAqualityAmaintenanceEnables AI coding assistants to access documentation, live API tools, and workflow prompts for integrating a game/app backend service into Godot, Unity, and Unreal Engine projects, including auth, leaderboards, cloud saves, remote config, localization, news, gift codes, feedback, logs, crash reporting, email, and admin dashboard management.34433 npmMIT
TDQS
Scored across 20 tools
Each tool targets a distinct resource or action (e.g., guidance, actions, runs, files). Even closely related tools like approve vs. execute vs. reject action have clearly different purposes, and descriptions further disambiguate them.
Most tools follow a consistent 'verb_noun' pattern (e.g., glitch_list_titles, glitch_start_agent_run). One exception is glitch_auth_status, which lacks a verb, and glitch_wait_for_agent_run uses a phrasal verb. Overall, the pattern is largely predictable.
With 20 tools, the set is slightly above the ideal 3-15 range but still well-scoped for the multi-faceted domain (authentication, billing, title management, agent runs, actions, files, guidance). No tool feels redundant.
The tool surface covers core workflows (start/wait/get runs, actions, guidance, files) but lacks basic lifecycle operations like listing all runs, canceling a run, or deleting artifacts. This creates notable gaps that an agent may need to work around.