# Summer Engine [Health: Active]

**Category:** 🎮 Gaming  
**Repository:** https://github.com/SummerEngine/summer  
**GitHub Stars:** 88  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/summer-2

## Description
MCP server, CLI and skills that let AI agents build, test and publish games with the Summer Engine game engine.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "summer-engine": {
    "command": "npx",
    "args": ["-y","summer-engine@latest"]
  }
}
```

## Documentation

## What Summer Engine does

Summer Engine combines an MCP server, a command-line interface, and game-development skills for agents working with the Summer Engine game engine. The local server lets an agent operate the running editor: it can construct scenes, create scripts, launch the game, press real keys, capture screenshots, and inspect debugger errors.

The platform also supports multiplayer features such as matchmaking, parties, leaderboards, player data, and world saves. Cloud operations cover asset generation and library search, game planning, store management, publishing, pricing, analytics, team administration, and Studio operations. Projects retain memory in a `.summer/` directory so a new agent can continue work.

## How it works

There are two main connection paths. The hosted MCP endpoint at `https://mcp.summerengine.com/mcp` provides cloud operations and requires signing in to a Summer account. It does not drive the local engine editor. The local setup writes `summer mcp` into an agent's configuration and controls the Summer Engine app on the developer's machine. After `summer login`, the local server can also run cloud operations.

The package includes skills covering areas such as movement, combat, multiplayer, visual effects, audio, interface design, and level design. Templates, references, and operations can be searched through the available Summer tooling. Agent permissions in Studio determine which actions can proceed without approval, including building, spending credits, publishing, changing prices, deleting resources, and contacting people.

## Setup and configuration

The CLI requires Node.js 22 or newer. To start a project and install the Summer Engine app when needed, run:

```bash
npx -y summer-engine@latest dev
```

The CLI can also be installed globally with `npm install -g summer-engine`, or through Homebrew with `brew install summerengine/tap/summer`. The `summer setup --cli` path installs skills and command-line support without adding an MCP server. For MCP-based engine work, use `npx -y summer-engine@latest setup <agent> --yes`; the setup command writes the local server and skills into the selected agent's configuration.

The hosted endpoint can be added directly to clients that support remote MCP connections. Claude Code and Codex provide command-line setup commands, while Cursor, VS Code, Devin Desktop, Claude Desktop, and claude.ai have their own configuration or connector flows. Sign in with `summer login` for local cloud access. Generation and paid builds use Summer credits, and automatic top-up is configured in Studio Billing rather than by the agent.

## Tools and capabilities

- Build scenes, scripts, physics, and user interfaces through live editor tools.
- Run games, send real key input, take screenshots, and read debugger errors for iterative testing.
- Create or find images, 3D models, motion, sound effects, music, voices, and video through cloud operations.
- Build multiplayer games using Summer networking features, including matchmaking, parties, leaderboards, player data, and world saves.
- Prepare store pages, artwork, builds, preview links, and releases for summer.games.
- Read store views, launches, sessions, play time, and custom analytics events.
- Search skills, templates, references, and operations for reusable game-development guidance.

## Limitations and notes

The repository supplies the MCP server, CLI, and skills; it is not the Summer Engine application itself. The CLI downloads the app when required, and the initial installation is about 660 MB. Local engine operations require the app to run on the developer's machine, while the hosted endpoint is intended for cloud work.

Publishing and other account-affecting actions are governed by Studio permissions and approval prompts. Deletion and contacting people are off by default, and Summer can require owner approval before publishing. Asset generation and paid builds consume Summer credits. ChatGPT and Claude's connector directory entries expose fixed subsets of tools rather than the complete `/mcp` endpoint.

_Full upstream README: https://allmcps.com/mcp/summer-2/readme_