Skip to main content

Overview

Summer is the game engine built for AI. Your agent (Claude Code, Cursor, Codex, Devin Desktop or any MCP app) can find game assets and import them straight into your Summer Engine project. You describe what you need in plain words. The agent searches, imports the match, and can add it to your scene. Search covers the Summer asset library (more than 239,000 assets), your own assets, or both. It matches words and meaning: “sci-fi weapon” also finds an asset described as “futuristic gun”.
Search is free for every signed-in account. It has rate limits. Generating new assets uses your credits.

Prerequisites

  • To search: add https://mcp.summerengine.com/mcp to your agent (or use the local server) and sign in once. No engine needed.
  • To import into your project: Summer Engine open with your project, and the local server (npx -y summer-engine@latest setup <agent> --yes, then npx -y summer-engine@latest login).

The tools

summer_assets_search and summer_assets_get are tools on the hosted MCP and in the assets profile of the local server. Elsewhere, call them through summer_call with "op": "assets.search" or "op": "assets.get". The 3.x names summer_search_assets and summer_get_asset still work through summer_call. See 3.x tool names. Each result has assetId, title, type, source (mine, curated, public or community), fileUrl, thumbnailUrl, format and license.

Import in one step: summer_import_asset

It searches, picks the top match, downloads the file and runs the engine’s import. With parent and scenePath, a 3D model is added to that scene. Kenney 3D packs import with their texture into a pack folder (res://assets/models/kenney/<pack>/), so two packs never overwrite each other’s colormap.png.

Search tips

  • Be specific: “low-poly wooden crate” beats “crate”.
  • Name a style: pass style, or add words like “cartoon”, “pixel” or “realistic”.
  • Give context: “platformer tiles”, “FPS weapon”, “RPG character”.
  • Name a pack if you know it, for example “Nature Kit”.

Errors

Every error has a code and one next step (next). Do that step first. All codes: How Summer answers. No results is not an error: the list is empty. Try other words or a wider assetType.

Workflow examples

One asset into the scene

User: “Add a low-poly tree to my World node” Agent calls: summer_import_asset({ query: "low-poly tree", parent: "./World", scenePath: "res://main.tscn", assetType: "3d_model" })

Look before importing

User: “What sci-fi weapons do you have?” Agent calls: summer_call({ op: "assets.search", input: { query: "sci-fi weapon", assetType: "3d_model", limit: 15 } }) The agent shows the results and the user picks one. The agent then calls summer_import_asset_by_id with that assetId, and scenePath and parent to place it.

Many assets at once

User: “Add some wooden crates and barrels to the warehouse” The agent searches once per kind, then imports the picks with summer_import_from_url_batch (one scan for all files), or calls summer_import_asset once per asset.

The asset library

The Summer library has more than 239,000 assets: 3D models, 2D sprites, UI elements, audio and music, including the CC0 Kenney collection. Licenses differ by asset: each result carries its license, and assets.get shows it in full. Browse the library at summerengine.com/asset-store. See Art System Licensing.

Summer Studio

Create, browse, and manage assets in Summer Studio

MCP Setup

Connect Cursor, Claude Code, and other agents

Need help? Ask in Discord first. That is where you get the fastest reply and support. For concrete help, email support@summerengine.com or founders@summerengine.com.