> ## Documentation Index
> Fetch the complete documentation index at: https://docs.summerengine.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Run Summer Grow with your AI agent

> The Summer Studio assistant, or your own agent through the Summer Engine MCP, runs Summer Grow: reads numbers, sets prices, runs A/B tests and applies for growth.

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](https://docs.summerengine.com/mcp/chatgpt-and-claude.md).

## 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

| You say | It does |
| - | - |
| "How is my game doing?" | Reads your numbers for the window you mean, finds the weakest step from store page to play, and gives one next step. |
| "Publish my game" | Opens **Publish a game**, fills the title and targets, and walks the store page with you. |
| "Enter my game in the jam" | Picks the open jam on **Publish a game**. |
| "Set my price in Germany to 9.99" | Sets a price by country. |
| "Test a darker key art" | Creates a store page A/B test as a draft, and starts it when you say so. |
| "Invite [sam@example.com](mailto:sam@example.com) as a developer" | Invites them to the game. |
| "I want ads on TikTok in the US" | Fills and sends a paid growth application. |
| "Apply for New and noteworthy" | Sends a featured placement application with your pitch. |
| "Make a dashboard called Morning check" | Creates the dashboard. |
| "Raise my events limit to 2 million" | Changes your monthly custom events limit. |

## From your own agent (MCP)

[Connect your agent](https://docs.summerengine.com/publishing/connect-your-agent.md) 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`.

| Operations | What they do | Asks you first (default) |
| - | - | - |
| [`analytics.overview`](https://docs.summerengine.com/mcp/operations/analytics#overview) | All your games: store page views, launches, play sessions and play time against the days before. Add `include` for prices, interest, readiness or earnings. | Never: reads |
| [`analytics.summary`](https://docs.summerengine.com/mcp/operations/analytics#summary), `analytics.events`, `analytics.trend`, `analytics.funnel` | One game by day, its custom events, trends and funnels. | Never: reads |
| `analytics.event_limit`, [`analytics.set_event_limit`](https://docs.summerengine.com/mcp/operations/analytics#set_event_limit) | Read, or change, your monthly custom events limit. | A change always asks |
| [`pricing.get`](https://docs.summerengine.com/mcp/operations/pricing), `pricing.set_base`, `pricing.set_country`, `pricing.clear_country`, `pricing.schedule_discount`, `pricing.clear_discount` | Read prices; set the base price, country prices and sales. | Changes: yes, for now (later: Prices and live changes) |
| [`experiments.list`](https://docs.summerengine.com/mcp/operations/experiments), `experiments.results`, `experiments.create`, `experiments.start`, `experiments.stop` | Store page A/B tests. | Start and stop: yes, for now (later: Prices and live changes) |
| [`games.members`](https://docs.summerengine.com/mcp/operations/games#members), `games.set_member_role` | A game's team, and member roles. | Role changes: yes, for now (later: Prices and live changes) |
| `games.invite_member`, `games.remove_member`, `games.withdraw_invite` | Invite, remove, withdraw an invite. | Yes (Contact people, Delete for good) |
| [`marketing.apply`](https://docs.summerengine.com/mcp/operations/marketing#apply), `marketing.applications` | Apply for a promotion, ads, email outreach, creator introductions, a featured place or an A/B test run; read the status. Nothing is charged. | Applying asks (Contact people) |

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](https://docs.summerengine.com/publishing/mcp-tools.md). 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](https://docs.summerengine.com/mcp/permissions.md) (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`:

| Operation | What it does |
| - | - |
| [`studio.map`](https://docs.summerengine.com/mcp/operations/studio#map) | Every Studio page, with its id and path. Grow pages start with `grow`. |
| [`studio.open`](https://docs.summerengine.com/mcp/operations/studio#open) | Opens a page in your tab, such as `grow-promotions`. |
| [`studio.page`](https://docs.summerengine.com/mcp/operations/studio#page) | Reads the open page: its fields and buttons. |
| [`studio.use_page`](https://docs.summerengine.com/mcp/operations/studio#use_page) | Fills fields and presses one button. A button that has its own operation (a price, a test, an application) answers `moved` with the exact call to make. Buttons that publish, upload, pay or delete stay yours to click. |

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

Use the Summer Engine MCP. Read how my game did on Summer Games over the last
28 days with the analytics.overview operation, including prices, interest and readiness.
Don't change anything.

Name each number with its window. Tell me the weakest step from store page to
play, and the one thing in Summer Grow I should do next: a store page fix, a
sale, an A/B test, or an application for a featured place.

## What your agent asks first

With the default [Agent permissions](https://docs.summerengine.com/mcp/permissions.md), 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!](https://discord.gg/summerengine)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.