Build with AI — indiegames.de
Skip to content

Build with AI

You can make games with an AI assistant (for example Cursor or Claude) and send them straight from the editor to indiegames.de as a draft. Every game is welcome, with or without AI. The AI disclosure is required and has to be honest.

Whether a game goes public is decided by quality. What “good” means here

What the interface can do

The MCP interface provides these tools.

Read (no account)

  • search_games — Search published games.
  • get_game — Get one published game by slug.
  • list_new — List the newest published games.
  • list_picks — Featured game and weekly picks.
  • list_news — List published platform news.

With a token

  • create_draft — Create a game draft.
  • update_game — Update a game, including AI disclosure, age rating, tags, platforms, store links, and trailer.
  • upload_cover — Name the REST path for the cover upload. The image file does not go through MCP.
  • upload_build — Set an https play URL, or name the REST path for the ZIP upload.
  • upload_screenshot — Name the REST path for screenshot uploads. The image file does not go through MCP.
  • get_checklist — The publish checklist.
  • request_publish — Ask to publish. The first game waits for a person.
  • write_devlog — Write a devlog.
  • get_stats — Plays and downloads.
  • list_feedback — Reviews for a game.

create_news_draft and update_news_draft are only for the editorial team.

Address

The interface is at https://api.indiegames.de/mcp. Transport: Streamable HTTP, JSON. Read tools work without a token.

https://api.indiegames.de/mcp

Getting a token

Create an account (login via mail code) and confirm you are 16 or older. In Settings → API tokens, enter a name, choose permissions (read, drafts, request_publish), and create the token. It is shown only once. Default lifetime: 90 days. Tokens can only be created in the browser, not with another token.

Authorization: Bearer ig_…

Open settings

Setup

Claude Code (tested)

Claude Code
claude mcp add --transport http indiegames https://api.indiegames.de/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Check with claude mcp list — it shows Connected.

claude mcp list
claude mcp list

Cursor

File ~/.cursor/mcp.json or .cursor/mcp.json in the project:

mcp.json
{
  "mcpServers": {
    "indiegames": {
      "url": "https://api.indiegames.de/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Claude Desktop (via mcp-remote, tested)

claude_desktop_config.json
{
  "mcpServers": {
    "indiegames": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.indiegames.de/mcp",
        "--header",
        "Authorization:${AUTH}"
      ],
      "env": {
        "AUTH": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Other MCP clients

Any client with Streamable HTTP and a custom header works. Test:

MCP inspector
npx @modelcontextprotocol/inspector --cli https://api.indiegames.de/mcp --transport http --header "Authorization: Bearer <YOUR_TOKEN>" --method tools/list

First game, step by step

  1. create_draft with title, slug, description, tags (at least one category), and deliveryType browser or download.
  2. update_game: AI disclosure (for example aiNone: true or the AI fields), ageRating 0/6/12/16/18, more tags, platforms, store links, trailer.
  3. Files: binary uploads go over REST with the same token. POST https://api.indiegames.de/api/v1/games/{slug}/cover, https://api.indiegames.de/api/v1/games/{slug}/media (screenshots), https://api.indiegames.de/api/v1/games/{slug}/build (ZIP with index.html for browser games), multipart field file. Alternatively upload_build with an https externalUrl. The tools upload_cover, upload_build and upload_screenshot name these paths.
  4. get_checklist until ready: true. Then request_publish.

Publishing and rules

The same rules as a website upload. This also applies when republishing.

  • A cover (the existing 1200×630 px minimum still applies)
  • Playable: a build or an external link
  • The AI disclosure
  • At least one screenshot
  • A description of at least 200 characters
  • An age rating 0, 6, 12, 16, or 18 (18 = adults only)

A studio’s first game is reviewed by a person before it goes public; after that, games go live directly.

Upload rate limit: 20 per hour.

Short FAQ

Do I have to use AI?

No.

What happens to my token?

It lasts 90 days unless you set something else. You can revoke it in settings.

What if a tool reports “forbidden”?

You can only change your own games.

Contact: [email protected]