Try it free, unlimited with Pro
Gamedexy inside your AI coding agent
Search real mobile game screens and flows from Claude Code, Codex or Cursor. Connect your coding agent to Gamedexy over MCP. Your agent searches real captured screens and reads complete player flows from top mobile games while it helps you design and build, instead of guessing what other games do.
Free accounts can try it. Pro opens the whole library to your agent, $120/year or $14.99/month.
What you can ask it
Gamedexy is built around the systems that surround a core mechanic: how a game teaches itself, paces progression, introduces currencies, and brings players back. Ask in plain language and your agent pulls the evidence.
- Show me how mobile puzzle games introduce energy.
- Find first-session starter offers.
- Show onboarding sequences that introduce upgrades after the first level.
- Compare how games handle level-complete rewards.
- Find examples of failure → revive → return flows.
- Show how games introduce their first currency.
- Compare daily reward structures across games.
- Find screens related to shops, upgrades, collections, or missions.
Answers come from Gamedexy’s own recordings: real screens, in the order a real player saw them, with the on-screen text indexed.
What it can do
Search real screens
Find UI by on-screen text, category, tag, or game.
Inspect complete flows
Read a whole player journey step by step, in order.
Retrieve game context
Pull a game's flows, categories, and screen counts.
Inspect onboarding
Get normalized first-session steps with what each one teaches.
Compare structures
Align several games side by side on the same dimension.
Query the taxonomy
Discover the exact vocabulary to filter with.
Look up design terms
Get a plain-language definition, the filters that find it, and real examples.
Eleven tools in total: search_screens, search_flows, get_flow, get_screen, get_game, list_games, get_taxonomy, get_onboarding_sequence, compare_flows, list_terms, define_term. Your agent picks them for you; you never call them by hand.
Set it up
There is no API key to copy. You add the address below, your browser opens, you sign in to Gamedexy and authorize. That is the whole flow.
MCP endpoint
https://www.gamedexy.com/api/mcpClaude Code
Add the server, then sign in. Use --scope user if you want it available in every project.
claude mcp add --transport http gamedexy https://www.gamedexy.com/api/mcp claude mcp login gamedexy
Codex
Codex detects OAuth and starts the browser flow as soon as you add it.
codex mcp add gamedexy --url https://www.gamedexy.com/api/mcp
To sign in again later: codex mcp login gamedexy
Other clients
The endpoint is a standard MCP server over streamable HTTP using OAuth 2.1 with dynamic client registration, so other compliant clients such as Cursor and the Claude apps may work: add the address and sign in. Claude Code and Codex are the two we have tested end to end.
Map your own game
With Pro, the same agent can play a simulator or emulator build of your own game and send a private map to your account: every screen, the first week, prices and ads, bugs, and how it compares with top games. See Game Map
Step 1: In your game's folder, run
npx gamedexy initConnects Claude Code or Codex for you and prints the setup for Cursor and other agents. Checks this computer too: a Mac maps iOS and Android, Windows and Linux map Android. Needs Node 20.
Step 2: Ask your agent
Map my game with GamedexyIt asks which run you want first and suggests a capture run: every screen opened from your code, no playing. It never buys anything: price and ad buttons are refused in code.
Who can connect
Any Gamedexy account can connect. Free includes 15 calls a month, the first 3 steps of each flow and thumbnails; flow comparisons are Pro only. Pro has no monthly cap, full flows and full-size images, within a daily fair-use ceiling. Your plan is checked on every request, so access follows your subscription automatically.
Get ProWhat the evidence is, and isn't
Gamedexy shows captured evidence from real gameplay. It is useful for analyzing observed UI, flows, progression surfaces, monetization surfaces, retention surfaces, and recurring patterns across games.
It does not establish that a design is fun, that a monetization system caused anyone’s revenue, that an economy is balanced, or that a capture covers every state a game can reach. It is not the source implementation, and it is not permission to copy protected expression. Treat it as reference, the way you would treat a competitor teardown: evidence to reason from, not a specification to ship.

