Build with an AI tool
Connect your own AI assistant to draft, edit, and check your Play by Mail games over MCP.
Start from your own setting, characters, and rules. When you connect an MCP-capable AI tool to your designer account, you can sketch out locations, items, creatures, or mecha squads in conversation and write them straight into a draft game.
Everything the tool creates shows up in the Game Designers studio immediately, with direct links back to each screen so you can inspect the details, add artwork and soundscapes, and publish when you are happy with it.
Connector address
Point your AI tool at this address and sign in with your Play by Mail account when prompted:
https://playbymail.games/mcp
Connect your tool
Pick the client you use below. Each one signs in through your browser and asks you to approve access before the tool can read or edit anything.
Claude (web and desktop)
- Open Settings, then Connectors, and choose Add custom connector.
- Paste the connector address above and save.
- Click Connect, sign in to Play by Mail, and approve access.
ChatGPT
- Open Settings, then Apps and Connectors, and add a new MCP connector.
- Paste the connector address above and choose OAuth authentication.
- Complete sign-in in your browser and approve access.
Claude Code
-
Add the Play by Mail server from your terminal:
claude mcp add --transport http playbymail https://playbymail.games/mcp - Run /mcp in Claude Code, pick playbymail, and follow the browser sign-in prompt.
VS Code
- Open the Command Palette and run MCP: Add Server, then choose HTTP.
- Paste the connector address above and name the server playbymail.
- Start the server and approve access in the browser window that opens.
What the connector can and cannot do
What it does
- Reads your draft and published games, along with the schemas and rules for each game type.
- Creates, updates, and removes records inside your draft games.
- Runs game validation and reports issues so you can fix them before publishing.
- Returns direct links to the matching studio screen for every record it touches.
What it does not do
- It never changes published games. Edits are blocked once a game is published.
- It cannot publish games, start or stop game instances, invite players, or process turns.
- It cannot upload artwork, maps, or audio files. Add media in the studio instead.
- It only sees games on your own account. It does not export or download other designers' games or demos.
Available tools
These are the tools exposed by the connector right now, read directly from the server.
| Tool | Access | What it does |
|---|---|---|
read_design_guide |
Read | Returns the design guide for a game type: how a designer's story maps onto the game's configuration, the order resources are built in, a checklist, and the headings of the game type's rules document. With a section it returns that part of the rules document. |
list_resource_types |
Read | Lists every kind of record a game of one type is configured with, such as locations, creatures and items for an adventure game, or sectors, chassis and squads for a mecha game, in the order they are built: each resource comes after the resources it refers to. |
describe_resource |
Read | Describes one resource: its fields with their types, whether each is required, the allowed values of each choice field, which resource each ID field points at, the IDs each operation needs, its named actions and its studio page. |
list_records |
Read | Lists the records of one resource: your games, the records in one of your games, platform library content or your image library. Each record comes with the studio link that opens it. |
get_record |
Read | Returns one record of a resource with every field the API returns, and the studio link that opens it. |
review_scenario |
Read | Reads one of the designer's games in a single call: the game record and its status, every readiness issue with the studio link that fixes it, a review checklist for the game's type, and the game's contents, which are every record of every resource the game has, child records included, each with its studio link. The checklist names what the server does not check, such as how hard the fights are and whether the pacing fits; read the contents to answer each point. |
check_readiness |
Read | Runs the game's readiness check, the same one the studio's issues panel shows, and returns every issue with its severity and the studio link that opens the page, and where possible the record, that fixes it. |
create_record |
Draft edit | Creates one record in a draft game, or a new draft game, and returns it as saved with the studio link that opens it. |
update_record |
Draft edit | Changes fields of one record in a draft game, or the draft game itself, and returns the record as saved with its studio link. Fields you leave out keep their values. |
delete_record |
Draft edit | Deletes one record from a draft game. It does not delete whole games. |
run_action |
Draft edit | Runs one of a resource's named actions on a game: reordering objectives, clocks or chapters, listing or setting the skills an adventure game offers, or copying a library creature or item into the game. Actions: adventure_game_skill.list_available_skills, adventure_game_skill.list_rule_set_skills, adventure_game_skill.set_available_skills, adventure_library_creature.copy_into_game, adventure_library_item.copy_into_game, game_chapter.reorder, game_clock.reorder, game_objective.reorder. |
get_image_upload_link |
Read | Returns the studio link where the designer uploads an image for a record: a location's or sector's turn sheet background, a creature's or item's portrait, mech chassis, weapon, equipment and building art, a chapter's illustrations, or the game's own turn sheet backgrounds. It uploads nothing. |
list_sound_keys |
Read | Lists the sounds a game can use, from the same sound library the studio and the players' turn sheets play from: ambient loops and one-shot sounds, each with its key, name, category and length. |
get_playtest_link |
Read | Returns the studio link where the designer play-tests a game in the Design Test panel, whether a test can start, whether one is already running, and any readiness errors that stop it. It does not start, advance or end a test: the designer does that in the studio. Draft and published games can both be play-tested. |
get_publish_link |
Read | Returns the studio link where the designer publishes a game, whether it is already published, and the readiness errors to fix first. It does not publish: publishing cannot be undone, so the designer does it in the studio. |