Skip to main content
Glama
Sign In
Glitch MCP

Glitch MCP

Official
by Glitch-Gaming-Platform
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Glitch MCP

No user-submitted related servers found.

    Related Servers

    • wishlistdoc-mcp

      xiongxingzhe
      A
      license
      A
      quality
      C
      maintenance
      Enables 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
    • tin

      tinofficial

      tin-computer
      A
      license
      Not graded
      quality
      A
      maintenance
      Connects coding agents to a hosted agentic marketing system so they can run marketing workflows, share project files, research and context, and review or approve deliverables across organic search, content, social, outreach, paid ads, and product QA. Every call is scoped to the user's project membership and connected services such as GitHub, Search Console, Google Ads, Stripe, PostHog, and X.
      266
      Apache 2.0
    • glade-mcp

      glade-mcpofficial

      Glade-tool
      A
      license
      Not graded
      quality
      A
      maintenance
      Connect 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.
      213
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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

    ActivityActive
    ResponsivenessNo issues

    Resources