Neural Cosmology
Answers, essays, experiments and books on consciousness and cosmology: search, read, buy.
Description from the maker (original English)
The game engine built for AI. Any agent makes a multiplayer game and publishes it.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://mcp.summerengine.com/mcpOpen Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"summer": {
"command": "npx",
"args": [
"-y",
"summer-engine",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add --transport http summer https://mcp.summerengine.com/mcpclaude mcp add summer -- npx -y summer-engine mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"summer": {
"url": "https://mcp.summerengine.com/mcp"
}
}
}Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"summer": {
"command": "npx",
"args": [
"-y",
"summer-engine",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"summer": {
"type": "http",
"url": "https://mcp.summerengine.com/mcp"
}
}
}Paste into .vscode/mcp.json in your project
{
"servers": {
"summer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"summer-engine",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://mcp.summerengine.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
The server asks you to sign in before it lists its tools.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account summerengine, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 403 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
Either way works: install it on your computer or connect to the cloud version.
The GitHub repo last changed –, and the latest version (4.5.0) reached the registry 18 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Neural Cosmology, slopped.site, Artsonia MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Answers, essays, experiments and books on consciousness and cosmology: search, read, buy.
Read-only tools over slopped.site: AI-made art, lore, games, sites, the curriculum.
Parent/fan access to Artsonia student-art portfolios, comments, and fans (AI-built).
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Any agent builds, tests and publishes a full multiplayer game. MCP server · game-dev skills · `summer` CLI, in one npm package: `summer-engine`.
Website · Docs · CLI setup · MCP setup
npx -y summer-engine@latest dev. It asks before it installs the Summer Engine app (about 660 MB, free) when it is missing, creates a starter project here (in ./my-game when this folder has other files) and opens it, ready for your agent. No sign-in needed to build.https://mcp.summerengine.com/mcp. Nothing to install.brew install summerengine/tap/summernpm install -g summer-engineCLI only (summer-engine 4.2.0 or newer), no MCP server: summer setup --cli. summer ops search "publish my game" finds any operation, signed in or not.
Cloud work: `https://mcp.summerengine.com/mcp`. Nothing to install. Add the URL to your agent and sign in to your Summer account once. Your agent then makes assets (images, 3D models, motion, sound effects, music, voices, video), searches and downloads your Summer asset library, plans games, and runs your projects, the store, publishing, prices, analytics, A/B tests, your team and Studio. It has no engine tools: for those, use the local server below.
| Agent | Add the hosted server |
|---|---|
| Claude Code | claude mcp add --transport http summer-cloud https://mcp.summerengine.com/mcp, then /mcp to sign in |
| Codex | codex mcp add summer-cloud --url https://mcp.summerengine.com/mcp, then codex mcp login summer-cloud |
| Cursor | Add to Cursor, or add "summer-cloud": {"url": "https://mcp.summerengine.com/mcp"} under mcpServers in ~/.cursor/mcp.json |
| VS Code | Add to VS Code, or code --add-mcp '{"name":"summer-cloud","type":"http","url":"https://mcp.summerengine.com/mcp"}' |
| Devin Desktop (formerly Windsurf) | add "summer-cloud": {"serverUrl": "https://mcp.summerengine.com/mcp"} under mcpServers in ~/.config/devin/mcp_config.json (Windows %APPDATA%\devin\mcp_config.json) |
| Claude Desktop, claude.ai | Settings > Connectors > Add custom connector, then paste the URL |
Engine work: `npx -y summer-engine@latest setup --yes` (needs Node 22+). It writes the local server (summer mcp) into your agent's config with the skills. The local server drives the Summer Engine app on your machine: build scenes, write scripts, play the game, take screenshots, read errors. After summer login it also runs every cloud operation, so your agent needs one server. Or paste the prompt in Get started and your agent does every step.
CLI only (summer-engine 4.2.0 or newer): `npx -y summer-engine@latest setup --cli --yes`. No MCP server: your agent runs Summer as commands in its shell. Setup installs the skills for your agent, with summer-cli, the guide to the commands, and writes no MCP entry. Your agent signs you in with summer login, finds an operation with summer ops search " " and runs it as summer -- , with --dry-run, --wait and --json. Engine commands (summer engine …) drive the Summer Engine app on your machine. Each skill ends with a table of the command for every tool it names. Add --assets-only for only the asset skills. --no-mcp is the same as --cli.
ChatGPT and Claude's connector directory use two reviewed store versions with a fixed tool list: https://mcp.summerengine.com/chatgpt (games, assets and generation; no publishing, no billing links) and https://mcp.summerengine.com/directory (the store, publishing and Grow reads; no image, 3D, audio or video generation). They keep their 3.x tool names and have no summer_search or summer_call. For everything else, use /mcp.
Summer Engine is the game engine built for AI. This repo connects your AI coding agent (Claude Code, Cursor, Codex, Copilot and many more) to it: the agent builds a whole game in the engine, tests it, publishes it to summer.games and reads how players play it.
| Part | What it does |
|---|---|
MCP server (summer mcp) | Tools your agent calls to drive the running editor: build scenes, write scripts, play the game, take screenshots, read errors. After summer login it also runs the cloud operations: assets, plans, the store, publishing, prices and analytics. |
| Skills | Game-dev know-how your agent loads: movement, combat, multiplayer, VFX, audio, UI, level design and more. |
CLI (summer) | Installs the engine, signs you in, sets up your agent, creates projects from templates and publishes games. |
This repo is not the engine itself. The CLI downloads the Summer Engine app for you.
With Summer installed, your agent can:
.summer/ project memory lets a fresh agent pick up where the last one stopped.Studio > Settings > Agent permissions has six switches. They apply to every app you connect, like Claude or ChatGPT. These defaults apply now. You can change them soon. Until then, Summer Games still asks the game's owner before an agent publishes, and price, A/B test and member changes ask you first.
| Switch | Default | What the agent may do without asking |
|---|---|---|
| Make and build | on | Edit drafts, scenes, plans and uploads, and start builds. |
| Spend credits | on | Generate assets and run paid builds, within your credits and your auto top-up limit. |
| Publish | on | Publish store pages, versions and releases. Summer's automatic checks still run first. |
| Prices and live changes | on | Change prices and sales, start or stop A/B tests, change member roles. |
| Delete for good | off: asks | Delete games, assets, pages and releases. |
| Contact people | off: asks | Send invites and other emails to real people. |
When a switch is off, the agent asks you first. It gives you a link (https://www.summerengine.com/studio/approvals/ ), and an open Studio tab shows the request with Approve and Decline. Nothing changes until you approve. The agent always asks before it changes agent permissions or auto top-up, enters a jam, or changes the analytics event limit. Studio > Settings > Agent activity lists what agents changed or asked for, newest first, with Undo for prices, sales, country prices, member roles, team names and the event limit.
Generation and paid builds spend your Summer credits. Turn on auto top-up in Studio Billing: when your credits fall below an amount you pick, Summer adds the amount you choose, up to a monthly limit you set. Agents can never change auto top-up on their own. When credits run out, your agent gets the error no_credits with one link: https://www.summerengine.com/studio/credits.
Summer never installs software without your explicit confirmation. Library entries are structurally prevented (by a capability lint in CI) from instructing agents to touch the network, credentials, or package managers.
Open your AI agent (Claude Code, Cursor, Codex, Copilot, Devin Desktop, etc.) and paste:
Install Summer Engine and let's make a game. Read github.com/summerengine/summer, check what I already have installed, install whatever is missing, and open a starter project so we can start building.
The agent reads this README, checks what is already on your machine, and runs only the missing steps in its shell.
The first run will:
summer-engine npm package (~2 MB) through npx.~/.claude/skills/ (or your agent's user-skill directory) so the agent loads them next session.npx -y summer-engine@latest dev: download the Summer Engine app (about 660 MB) if it's not installed, create a starter project and open it in the engine.Building needs no sign-in. Your agent asks you to sign in only when you first use Summer's cloud (generating assets, publishing).
Agents with no shell (Claude Desktop, chat apps with the local server) do the same through the MCP: summer_projects_create_local writes the starter project and summer_projects_open_local opens it, after you say yes to installing the engine.
In most agents (Claude Code, Codex, Cursor, GitHub Copilot (VS Code, CLI, JetBrains), Zed, Cline, Kilo Code, OpenCode, Devin Desktop, Antigravity, Kiro, Trae, Warp, Goose, Hermes, Crush, Amp, Factory, Junie, Qwen Code, Kimi Code, Grok Build and Mistral Vibe), setup also connects Summer Games (summer-games), so the agent can see your friends, start parties and send messages as you. You sign in once; setup prints the step for your agent (Claude Code: /mcp, choose summer-games; Codex: /mcp login summer-games; Cursor: Connect next to summer-games in its MCP settings). A summer.games page opens in your browser; sign in and choose Allow.
Then ask the agent to build something.
In Claude Code, type:
/plugin install summer --marketplace summerengine/summer
Then type /summer:start. It gets a first game playing in about five minutes, with one OK from you and no sign-in: from a template that already plays, or from a plan of concept art Summer draws for your idea right in the chat, built in the Summer Engine desktop app. The plugin brings Summer's skills and two MCP servers: summer-engine drives the desktop app (needs Node), and summer-cloud is Summer's hosted server (sign in once with /mcp). Use the plugin or summer setup claude-code, not both: they install the same skills.
Sound effects, music, voices, images, 3D models, motion and video are made on Summer's servers, so you do not need the Summer Engine app for them. The quickest way is the hosted server in Connect: no Node, no install. To get the asset skills too, paste this instead:
Connect Summer to this agent so I can make game assets. Read github.com/summerengine/summer, connect yourself to Summer and log me in. Skip the Summer Engine app and the starter project, I only want assets.
The agent installs the asset skills and the MCP config (summer-engine 4.0.0 or newer) and signs you in. It does not download the engine. Each a
Only the beginning is shown; read the rest in the repo