ReverseMCP

See Through Any Roblox Game — Your AI Agent's X-Ray Lens Dex exploring + SimpleSpy netcode reading, merged into one headless agent runtime. You keep a single mini window; your AI agent gets thirteen probe tools over a zero-install local file channel (no Node, no server, no studio, no exporting) and turns any live game into a readable structure — places, instances, remotes, script sources, players — while you simply play. The pitch Play the game. Your agent reads it while you play. The script runs client-side through your executor and serves the live game state through the executor's own workspace files: the agent drops a command JSON, the game answers. OpenCode, Claude Code, Codex CLI, Cursor, Windsurf, Cline or any terminal-capable agent can chain from "what is this game" to "which remote fires the item upgrade" in minutes — with plain PowerShell. Zero install. Zero Node. Zero server. Executing the script is the whole setup. No npm, no stdio bridge, no mcpServers config files. The only network call the script makes is fetching the pinned Silk UI build from GitHub raw. Dex, but like a JSON feed. The instance tree (explore, search_instances, get_properties) returns flat paths the agent can resolve directly — no window, no treeview instance-class spam, no copy-paste marathon. SimpleSpy, but an API. Namecall-hook interception (FireServer, InvokeServer, FireAllClients, …) plus incoming-event listeners, stored in a ring buffer with serialized args and calling-script attribution. The agent reads it with remote_calls, understands it with get_properties/get_source, and replays it with call_remote — replay is a deliberate user gate. Parallel games, addressed by uuid. Every run gets a uuid shortened to an 8-hex filename suffix, so multiple Roblox windows live side by side and the agent addresses a specific run by its session files. Answers always echo which run replied. Survives teleports by itself. In-experience place changes re-execute the script automatically (per-r