ShipGames

Ship a game

Make it with your AI, ship it here, send the link. Every build gets a game page, a Play link and play stats.

Make a game with your AI

The best way: your AI builds the game in a GitHub repo and ships every build here for you. Each build gets a page, a Play link and play stats, and the game can show a Verified build time.

1. Connect ShipGames to your AI

Add this link as a connector (an MCP server) in your AI app. It asks you to sign in to ShipGames once.

https://shipgames.io/mcp
Claude
  1. Open Settings, then Connectors, then Add custom connector.
  2. Name it ShipGames and paste the link. Add.
  3. Tap Connect, sign in with your passkey and tap Allow.
  4. In a chat, turn ShipGames on from the tools menu.
Claude Code
claude mcp add --transport http shipgames https://shipgames.io/mcp

Then run /mcp to sign in.

ChatGPT
  1. Open Settings, then Apps and Connectors. Under Advanced settings, turn on Developer mode.
  2. Create a connector: name ShipGames, paste the link, authentication OAuth.
  3. Sign in with your passkey and tap Allow.
Cursor

Add this to ~/.cursor/mcp.json, then open Cursor Settings, MCP, and tap Login next to ShipGames:

{
  "mcpServers": {
    "shipgames": { "url": "https://shipgames.io/mcp" }
  }
}
An agent without connectors

Make a token on your account page and give it to the agent as SHIPGAMES_TOKEN. It can ship and edit your games, nothing more, and you can revoke it any time.

2. Paste this prompt

It makes the game's GitHub repo first, builds the smallest playable version, commits and pushes as it goes, and ships each build here.

Help me make a small browser game and put it on ShipGames (https://shipgames.io), set up from the start so its build time can be Verified.

Before writing any game code:
1. If I haven't said what the game is, ask me for a name and a one-line idea.
2. Make a new folder for the game (its own folder, not inside another project) and run git init.
3. Make a new public GitHub repo for it and push once. If the GitHub CLI is installed and signed in, run: gh repo create <name> --public --source . --push. If not, ask me to make an empty public repo on github.com and give you its link, then add it as the remote "origin" and push.
4. Make every commit push by itself: save these two lines as .git/hooks/post-commit and make the file executable.
   #!/bin/sh
   git push --quiet origin HEAD >/dev/null 2>&1 &

Then build:
5. Make the smallest playable version first, as index.html at the top of the repo. Static files only: HTML, JavaScript, CSS, images, sound.
6. Commit after every change that works, with a message saying what changed. Don't save the commits up for the end.

Connect it to ShipGames:
7. If you have the ShipGames connector (tools like ship_github), use it. If not, ask me to add it (https://shipgames.io/mcp) or to make a token at https://shipgames.io/account and give it to you as SHIPGAMES_TOKEN. Never print the token or commit it.
8. Ship the first build from the repo: ship_github with repo set to the repo's link. With a token instead: POST {"repo": "<the repo's link>", "path": "index.html"} to https://shipgames.io/api/v1/ship/github with the header Authorization: Bearer $SHIPGAMES_TOKEN.
9. For every later build: commit and push, then ship_github with game set to the game's slug (with a token: POST {"game": "<slug>"} to the same address).
10. Each time, give me the game page link from the answer.

The rest of what you can do on ShipGames (devlog, who can play it, stats, player feedback): https://shipgames.io/llms.txt

Every step an agent can take on ShipGames is at https://shipgames.io/llms.txt. Full API: /docs/api.

Already have a finished game?

Drop the files, paste its public link, or point at its GitHub repo. Sign in to ship it

Uploaded files can't show a Verified build time: only games shipped from GitHub, pushed as they were built, can.