A
licenseA
qualityC
maintenanceEnables 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.
3
MIT
Glitch MCP
OfficialRelated Servers
Alternatives to Glitch MCP
No user-submitted related servers found.
Related Servers
Dovetail MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceConnects AI tools to the Dovetail API, enabling them to interact with Dovetail features.1,026 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.215MIT
spritecook-mcpofficial
AlicenseNot gradedqualityDmaintenanceConnects AI agents to SpriteCook for AI-powered pixel art and game asset generation, enabling natural language creation of sprites, character sheets, icons, and animations.199 npm5MIT- AlicenseAqualityDmaintenanceEnables AI agents to connect and interact with common business platforms like Shopify, WordPress, and Calendly via pre-built connectors for tasks such as product management, content operations, and scheduling.13MIT
- AlicenseNot gradedqualityAmaintenanceConnects AI agents to The Agents Hub, visualizing them as pixel characters on a tile-based property with tools for state, assets, inboxes, and multi-agent orchestration.4 npm1MIT
TDQS
A3.5/5.0
Scored across 20 tools
Disambiguation5/5
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.
Naming Consistency4/5
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.
Tool Count4/5
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.
Completeness3/5
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.
Maintenance
ActivityMaintained
ResponsivenessNo issues