Pick your agent
Bring the tool you already use. Setup is one URL and about a minute.
What this is
TipTap runs a server your AI agent can talk to. Once it is connected, you describe the game you want in your own tool and the agent does the work: it reads the platform spec and the SDK documentation, writes a single self-contained HTML file, uploads it as a draft, and runs it through our validator. The validator is the important half — it catches the things a model gets wrong and hands back specific errors the agent repairs until they are gone. You watch it happen on your sessions page, and nothing reaches the feed without a human moderator saying yes.
Rather not start from a blank prompt? The cookbook has ready-made prompts for whole games, single mechanics and the SDK integration — and a connected agent can browse the same recipes with list_cookbook_recipes. Pointing an agent at these docs? Give it /llms-full.txt, which is every page on this site in one plain-text document.
The one value every client needs
Whichever tool you use, setup comes down to giving it this URL. The guides above just show you where each one wants it typed.
Server URL
https://mcp.tiptapgames.com/mcpTwo ways to prove it's you
You give the client the URL and nothing else. It sends you to TipTap in a browser, you press Approve once, and it is connected — no token to copy, store or leak. Works with claude.ai, Claude Code, Codex and Replit.
You mint a token in settings and paste it into your client's config. Use it when no browser can open, or when your client only sends a static header. Shown once, so save it; revoke and mint another if it escapes. Required for Cursor and VS Code.
Questions people actually ask
Is this safe?
Your agent never touches the feed directly, and it never reaches the review queue either: everything it builds lands in your Drafts, and you decide what gets submitted. From there it goes through the same validator and the same human moderation queue as a hand-uploaded game, and approved games run in a locked-down sandbox with no network access, no cookies and no storage. The connection is scoped to your account and revocable in one click — see the security model.
What can the agent actually do to my account?
Create build sessions, upload and validate drafts, and save games to your Drafts under your name. That is the whole surface — it cannot read your messages, change your profile, delete your games, or see anything about other creators. Create → Agents & access lists every connected app and key, with a revoke button that takes effect on the connection's very next request.
Does it cost credits?
No. TipTap charges nothing for agent builds — no credits, no build minutes, no paid tier gating any of this. You pay whatever your own agent costs you.
My tool has no MCP support. Am I stuck?
Not at all. Ask the agent for one self-contained HTML file and paste it at /create/upload. Same validator, same review queue — you just carry the file across yourself. Point the agent at the agent spec first so it builds against the real constraints.
What happens next
Once your agent is connected, this is the whole path from prompt to feed.
Your agent opens a build session
It does this itself, on its first tool call — there is no session to create on the website first. Everything it does afterwards is attached to that session and shows up under your account.
You watch it work
The session page shows a live activity feed — spec read, draft uploaded, validation run, cover set. It is built from the server's own audit trail, not from what the agent reports, so it shows what actually happened.
The validation loop runs
The agent uploads a draft and validates it. Failing the first time is normal and healthy: the validator returns specific errors, the agent repairs them and validates again until it passes.
It lands under Needs work
Only once validation passes. The game is saved to your account as a draft, tagged as agent-built, under My games → Needs work. It is not in review and not in the feed — nobody but you can see it, and nobody has been asked to look at it.
You play it and submit it
This step is yours and cannot be done by an agent. Open My games in your Creator Studio, play the game, and submit it when you are happy. Submitting is where you accept the licence that lets us publish it, which is why it has to be you.
A human moderator approves it
Then — and only then — it goes live in the feed. The decision comes to you either way: a notification in the bell, and an email where enabled. You keep full ownership, and you can take it down whenever you like.
No agent can submit a game, let alone publish one. The tool it calls is submit_game — a name kept for compatibility — and it creates a draft. Sending that draft for review is a step only you can take, signed in, because it is where you accept the licence over your own work. If your agent says the game is “submitted” or “published”, it is getting ahead of itself; what is true is on My games.