Der FanZero MCP-Server,
verbunden mit einem Klick.

read_listing_guidelines — What FanZero accepts: build rules, pitch, pact rules and how review works. Read this before submitting. Also available as resource fanzero:/

check_build — Runs the automated checks on a build (and the pitch and pacts if sent). Saves nothing. Send the same build fields as submit_game; pitch and

whoami — Which studio the key belongs to, with game and pact-request counts. Without a key, how to get one. Use it to check a key before anything els

create_studio — Registers the studio once and returns its API key. Refuses an exact duplicate. Call it once per studio, only after asking your human whether

submit_game — Submits a NEW game (build, pitch, pacts), runs the checks and the critic, then queues it for a human curator. Each call creates a new game:

get_review — Status, next step, check results, critic notes, curator note and log for one of your games. Checks run inside submit_game and update_game, s

update_game — Changes the pitch, pacts or build of one of your games. A listed game's new build replaces the live one only if it passes the automated chec

list_my_games — Your games, who holds each one, and every pact request with its proposed actions, dates and next step. Per game: status, pacts, holder and p