Skip to main content
See how your published game is doing. 2 tools. What each column means, and how to connect: MCP tools reference.
Generated from the tools’ own definitions: the summer-engine npm package 3.3.0 (its MCP server’s tools/list, library/tools/*/resource.yaml and registry/generated/index.json in SummerEngine/summer) and the hosted Summer Engine MCP (src/lib/mcp/hosted at commit 8c4351ee30). If something here is wrong, the tool definition is wrong.

summer_grow_analytics

On the hosted MCP. One game’s analytics on Summer Games for the last 7, 28 or 90 days (UTC): totals (store page views, launches, play sessions, play time, average session), every day of the window, and the game’s top custom events (sent with Summer.client.analytics.capture; counts are approximate). Real data; read-only. gameId comes from summer_store_list_games. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call

summer_grow_overview

On the hosted MCP. Summer Grow across the signed-in owner’s games on Summer Games: store page views, launches, play sessions and play time per game and in total, for the last 7, 28 or 90 days (UTC). Real data from Summer Games; read-only. For one game’s daily numbers and custom events use summer_grow_analytics. Inputs:
Output: MCP text content holding JSON; errors set isError.
Example call