Connect Claude, ChatGPT and other apps
Glitchless Cloud · Last updated 25 October 2026
Ask Claude or ChatGPT what's wrong with your game and it answers from what your players actually hit: the findings, frame times, crashes, sessions, bug reports, store reviews and revenue Glitchless measured. Connect it once to the Glitchless MCP server, sign in, and it works with every game in the workspace you pick.
The server's address
https://api.glitchless.gg/mcp
Coding agents that start a local process can use glitchless-mcp instead. It has the same tools, and it can also run playtests and send builds to a Steam Deck.
Connect
Claude: claude.ai, Claude Desktop and the mobile apps
Go to Customize → Connectors → Add → Add custom connector. Name it Glitchless, paste the address and press Add. Claude opens Glitchless so you can sign in.
Claude Code
In a terminal
claude mcp add --transport http glitchless https://api.glitchless.gg/mcp
Then run /mcp in Claude Code and choose Glitchless to sign in.
ChatGPT
Go to Plugins → + → Add custom MCP server, paste the address and choose OAuth.
Other apps
Give the app the address. If it supports MCP's OAuth sign-in, it finds Glitchless's sign-in by itself. If it can only send a fixed header, make a workspace key in Settings → Keys & access and send it as Authorization: Bearer gl_ws_….
Signing in
The app sends you to Glitchless. Sign in with Google or GitHub, pick the workspace, and choose what the app may do:
| Permission | What the app may do |
|---|---|
| Read every game's data | Read findings, frame times, errors, players, events, dashboards, store reviews and revenue. Always given. |
| Design and save dashboards | Lay out a game's dashboard pages and save them. |
| Create games and share links | Create a game, and make or revoke read-only links to a board. |
The last two are ticked unless you untick them, and only a workspace's Owners, Admins and Developers can give them. A Viewer's connection can only read.
What an app can and can't do
- It acts as you, with your role in the workspace, and sees only the tools its permissions allow.
- It can't delete your games' data, change your billing or change who's in the workspace.
- It can't run playtests or reach a Steam Deck. Those tools work on the computer they run on, so only the local glitchless-mcp has them.
- The app's provider gets what the app reads, under that provider's terms. The privacy policy lists what that can include.
Disconnect
Each connection shows in Settings → Keys & access under the app's name. Revoke it there to disconnect. Connecting the same app again replaces its old connection.
Tools
Every tool takes the game, by name or ID.
| Tool | Needs | Changes anything |
|---|---|---|
List games glitchless_list_games | Read | No |
Triage glitchless_triage | Read | No |
Overview glitchless_overview | Read | No |
Performance glitchless_performance | Read | No |
Get error glitchless_get_error | Read | No |
Player funnel glitchless_player_funnel | Read | No |
Death hotspots glitchless_death_hotspots | Read | No |
Session glitchless_session | Read | No |
Events glitchless_events | Read | No |
Compare versions glitchless_compare_versions | Read | No |
Dashboard glitchless_dashboard | Read | No |
Bug reports glitchless_bug_reports | Read | No |
Store reviews glitchless_store_reviews | Read | No |
Store vitals glitchless_store_vitals | Read | No |
Revenue glitchless_revenue | Read | No |
Save dashboard glitchless_set_dashboard | Dashboards | Yes: replaces the game's saved dashboard pages |
Create game glitchless_create_game | Games, share links | Yes: creates a game |
Share board glitchless_share_board | Games, share links | Yes: makes a public, read-only link to a board |
List share links glitchless_list_share_links | Games, share links | No |
Revoke share link glitchless_revoke_share_link | Games, share links | Yes: ends a share link |
For client developers
| Transport | Streamable HTTP, stateless: POST only (GET answers 405). Clients of 2026-07-28 get a JSON body; older ones get the answer as a one-event SSE stream. |
|---|---|
| Protocol versions | 2026-07-28, and 2025-11-25 and earlier through initialize. |
| Protected resource metadata | https://api.glitchless.gg/.well-known/oauth-protected-resource/mcp (RFC 9728), also at the root path. A request without a token gets 401 with WWW-Authenticate: Bearer resource_metadata="…", scope="read dashboard manage". |
| Authorization server | https://api.glitchless.gg/.well-known/oauth-authorization-server (RFC 8414), issuer https://api.glitchless.gg. |
| Clients | Client ID Metadata Documents (an HTTPS client_id, 5 KB at most), or Dynamic Client Registration at /oauth/register (RFC 7591). |
| Flow | Authorization code with PKCE, S256 only, at https://app.glitchless.gg/oauth/authorize. Send resource (RFC 8707); the response carries iss (RFC 9207). |
| Redirect URIs | Exact match, except loopback redirects (localhost, 127.0.0.1, [::1]), which match on any port. |
| Tokens | Access tokens last an hour and work only at /mcp. Refresh tokens last 30 days and rotate on every use; presenting a used one again ends the connection. |
| Revocation | /oauth/revoke (RFC 7009): an access token ends alone, a refresh token ends the connection. |
| CORS | Any https origin or localhost page may call /mcp, the metadata and the OAuth endpoints. No cookies are involved. |
Trouble connecting? Email support@glitchless.gg with the app you used and any error it showed.