Log inSubmit server
Summer Engine logo

Summer Engine

Build, test, publish, and analyze Summer Engine games through MCP tools, a CLI, and agent-ready game-development skills.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Summer Engine

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "summer-2": {
      "command": "npx",
      "args": [
        "-y",
        "summer-engine@latest"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

Summer Engine MCP server connects AI coding agents to the Summer Engine editor and its cloud services. Local MCP tools build scenes, write scripts, run games, capture screenshots, and inspect errors; after login, the same setup can access assets, publishing, store, and analytics operations. Use the hosted endpoint for cloud work without installation, or install the CLI and app when an agent needs to drive the local engine. It fits agents building complete single-player or multiplayer games and iterating through playtests.

Use cases

  • Build a game from scenes, scripts, physics, and UI
  • Test gameplay with key input, screenshots, and debugger output
  • Create and search game assets through Summer cloud operations
  • Publish a finished game to the summer.games store
  • Read player engagement and custom game analytics

Key features

  • Local editor control through MCP
  • Cloud asset generation and library search
  • Multiplayer game support
  • Game publishing and store management
  • Analytics reads and custom events
  • Agent-ready game-development skills

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · summer-engine@latest (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars88Stargazers on the source repository.
Last commitTodayMost recent push to the default branch.

How Summer Engine works

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:

Terminal
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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Summer Engine

Summer Engine is an MCP server that connects AI agents to the Summer Engine editor and cloud services. Its main tools build scenes, write scripts, run games, capture screenshots, inspect errors, manage assets, publish games, and read analytics. A local setup drives the editor, while the hosted endpoint handles cloud operations.

Run `npx -y summer-engine@latest setup <agent> --yes` with Node.js 22 or newer. The command installs the skills and writes the local `summer mcp` server into the selected agent's configuration. For cloud-only work, add `https://mcp.summerengine.com/mcp` directly and sign in.

Yes, Summer Engine supports multiplayer game development with matchmaking, parties, leaderboards, player data, and world saves through its networking features. Agents can build these games through the engine workflow and use the related cloud operations after signing in.

Yes, Summer Engine works with Cursor. Add the hosted MCP URL to Cursor's MCP configuration for cloud operations, or run the setup command for local engine control and the included skills.

Summer Engine can publish store pages, versions, and releases to summer.games, but publishing is controlled by Studio permissions. Automatic checks run before a release goes live, and an owner approval can be required depending on the configured agent permissions.

Related MCP servers

All in Gaming All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSummer Engine AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/summer-2?style=directory)](https://allmcps.com/mcp/summer-2)
HTML Embed
<a href="https://allmcps.com/mcp/summer-2"><img src="https://allmcps.com/api/badge/summer-2?style=directory" alt="Summer Engine on AllMCPs" /></a>