Skip to main content
Summer is the game engine built for AI, and Grow is built for agents too. Every Grow page can be read, opened and filled in by the Studio assistant, or by your own agent through the full Summer MCP at https://mcp.summerengine.com/mcp (Claude Code, Codex, Cursor, or Claude and ChatGPT as a custom connector). The versions of Summer made for the ChatGPT and Claude app directories do less: the ChatGPT one has no Grow tools, and the Claude one reads your numbers and sends applications but cannot change prices, tests or members. See Summer in ChatGPT and Claude.

In Studio

Open the chat in Studio and ask in your own words. The assistant:
  • takes you there: “open Promotions”, “show me my A/B tests”;
  • reads your numbers: “how is my game doing this month?”, “what did I earn?”, “how many wishlists?”;
  • fills the page with you: you see each field fill in, and you can undo it from the chat;
  • does the job: sets prices by country, creates A/B tests, invites people, sends growth applications.
It never presses a button that publishes, uploads, pays or deletes unless you asked for exactly that. Your numbers are always your real ones; when a page shows example data, the assistant says so.

Things to ask

From your own agent (MCP)

Connect your agent to the full Summer Engine MCP, https://mcp.summerengine.com/mcp. These operations cover Grow. Two have their own tool (summer_analytics_summary, summer_pricing_get); run the others with summer_call ({"op": "pricing.set_base", "input": {...}}). summer_search finds any of them from the job in plain words. 3.x names such as summer_grow_prices still work through summer_call. Publishing has its own operations (store.*; tools summer_store_get_listing, summer_store_update_listing, summer_store_status and summer_store_publish): see Publishing operations. Your agent publishes with summer_store_publish, and Summer’s store review still runs before players see it. For now Summer Games still asks the game’s owner to approve an agent’s publish: the answer is needs_approval with the owner’s approval link. Soon, with Publish on in Agent permissions (the default), it publishes at once.

Drive your Studio tab

Your agent can also move and fill your open Studio tab, the same way the Studio assistant does. It runs these operations with summer_call:

Grow my game. Your agent reads your numbers and proposes one next step. No changes.

What your agent asks first

With the default Agent permissions, your agent asks you before it deletes for good (members, invites), contacts people (team invites, growth applications), raises your custom events limit, enters a jam, or changes auto top-up or Agent permissions. For now it also asks before price, A/B test and member changes, because Summer Games still asks; you can change the switches soon. It asks with a link (https://www.summerengine.com/studio/approvals/<id>) and a card in your open Studio tab. Studio > Settings > Agent activity lists what agents changed, with Undo for prices, sales, country prices, member roles and the event limit.

What agents do not do

  • Connect your payouts: that is your click in Stripe.
  • Promise that an application is accepted, or that alerts email you.
  • Present example data as your numbers.

Does this not help you? Reach out on Discord!