Glitchless

glitchless-mcp

The Glitchless MCP server. It lets any coding agent (Claude Code, Codex, Cursor or another MCP client) read how your game runs for real players, from a Glitchless server: ranked findings, frame-time breakdowns, errors, level funnels, death hotspots and version comparisons. It can also run playtest bots before and after a change, to check a fix.

It's a stdio server. Run it with npx, no install needed:

npx -y glitchless-mcp

Apps that connect to a URL instead of starting a process (claude.ai, ChatGPT, Claude Code's HTTP servers) use Glitchless Cloud's hosted copy at https://api.glitchless.gg/mcp and sign in with OAuth: see Glitchless by URL. It has the same tools, less the ones that act on your own computer.

Sign in to a workspace (Glitchless Cloud)

npx -y glitchless-mcp login

It prints a link and a code; you approve the code in the Glitchless dashboard, and it saves a workspace key in ~/.config/glitchless/credentials.json (readable only by you). From then on the server reaches every game in that workspace: glitchless_list_games lists them, glitchless_create_game makes one and returns its client token, and every tool takes game (a name or id). The key acts as you, with your role in the workspace, and never deletes data or touches billing or people. npx -y glitchless-mcp whoami shows where you're signed in, logout deletes the saved key, and Settings → Keys & access in the dashboard lists and revokes keys. An agent can also sign in from inside a chat with the glitchless_sign_in tool: it shows the link and code, and the running server switches over once you approve. The saved key is only ever sent to the server it was saved for: point GLITCHLESS_URL at another one (a meetup's own box) and the MCP server connects without it, so set GLITCHLESS_API_KEY if that server has a key.

Serve it over HTTP yourself

npx -y glitchless-mcp serve [--port 3001] [--host 127.0.0.1]

The tools that work from a server (all but sign-in, playtests and the Steam Deck) at http://127.0.0.1:3001/mcp, over Streamable HTTP, for clients of the 2026-07-28 protocol and older ones alike. It reads with the same settings as the stdio server (below), for a self-hosted server or a signed-in workspace. It answers this computer only, and checks Host and Origin so web pages can't reach it; to listen on another address, set GLITCHLESS_MCP_TOKEN and have clients send it as Authorization: Bearer.

Settings

Add it to your agent

Claude Code:

claude mcp add glitchless -e GLITCHLESS_URL=http://localhost:7777 -e GLITCHLESS_API_KEY=gl_sk_… -- npx -y glitchless-mcp

Codex, in ~/.codex/config.toml:

[mcp_servers.glitchless]

command = "npx" args = ["-y", "glitchless-mcp"] env = { GLITCHLESS_URL = "http://localhost:7777", GLITCHLESS_API_KEY = "gl_sk_…" }

Cursor, in .cursor/mcp.json (add the file to .gitignore if it holds the key):

{

"mcpServers": { "glitchless": { "command": "npx", "args": ["-y", "glitchless-mcp"], "env": { "GLITCHLESS_URL": "http://localhost:7777", "GLITCHLESS_API_KEY": "gl_sk_…" } } } }

Any other MCP client: the command is npx, the arguments are -y glitchless-mcp, and the settings above go in its environment.

Tools

The reads take hours, version, env (e.g. prod), session_type (user for players only, tester for people on TestFlight and other test builds, synthetic for bots, playtests and store test devices, all) and props, the session properties the game sets ({ rank: "diamond" }, or a list of values). Unless env or session_type is given, findings read the production sessions of players and say so; the other numbers count every session in the window.

To let the agent drive the running game as well (measure frame times, inspect the scene, load a level), add the WebMCP server beside this one: npx -y @jason.today/webmcp@latest --mcp.

License

MIT