Jabbertoon for AI assistants

Build it with AI using the Jabbertoon tools. Ask ChatGPT, Claude, Gemini, Grok or any AI assistant to build with you. An assistant that can use tools adds Jabbertoon's as a connector (an MCP server) at https://jabbertoon.com/mcp: in Claude or ChatGPT, a custom connector with that address. Then ask it for what you want, a cartoon, a thing in 3D, a world, a place to walk or a game, and it gives you a link that opens it here, for you to change and keep.

Or just send an AI agent here. Tell an agent that can run code or call web addresses (Claude Code, Codex, ChatGPT's agent mode and others) to go to jabbertoon.com and make what you want. It reads this page and the site's guide for AI, works out the tools for itself (when a step is wrong, the answer says how to put it right), and gives you a link that opens what it built. A chat that can only read web pages learns how Jabbertoon works the same way, but to build, it needs the connector above.

If you are an AI assistant, or you build one, these are the ways to build with Jabbertoon without a browser: cartoons, things in 3D, worlds, places to walk and games. Every tool is free and needs no key and no account. They read Jabbertoon's guides, moves, characters and looks; build what the person asked for from steps and check it, saying what is wrong, where, and how to fix it; and make a jabbertoon.com link that opens it: a cartoon in the editor, where the person plays it, changes it and saves the video, and a thing, a world or a game in the editor, to play and keep. The online tools keep nothing you send, except report_problem, which keeps the report it is sent (see "What happens to what you send", below). The one thing still to come is turning a script into a video in code, with a command that runs on your own machine and runs these tools there for assistants that run tools locally: it is not yet published, and neither are the two more tools it carries, preview and render_video.

The makers, for a person to use

Jabbertoon's top bar is its makers, and each feeds the Cartoon, the main page. Cast makes a character - a person or an animal, its body, head, colours and clothes - and puts it in a cartoon. Sets builds the place a cartoon happens in - rooms, walls, roofs, hills, water, trees, buildings and props, its time of day and its weather - and puts it in a cartoon. Props makes a thing to hold, sit on or stand in a set. Animation makes moves. What a person makes there is kept in their own browser and offered in the Cartoon's lists there, so when someone asks to make one of these by hand, send them to that page: a character or a set made there cannot be named in a script you write.

How to connect

The order of calls

A cartoon from a script is one call: make_cartoon {"script": "Mia (cat): Have you seen my hat?\nLeo: Is it on that crab?"} answers the link to give the person. A line each, Name: what they say, with (happy, waves) in a line, [Leo walks to Mia] between lines and Place: Beach (get_guide start has the whole form). For anything more:

  1. get_guide first: {"topic": "cartoon"} explains the cartoon's JSON, and the other topics the moves, characters, voices, places, errors and limits.
  2. Write the cartoon, then validate it until ok is true. Each problem says where it is, what is wrong and how to fix it, and when the fix is certain it comes with did_you_mean and a patch; "repair": true applies those. What the site cannot draw is an error, so ok means the editor shows what was written. validate also says what a viewer would see go wrong (a character off stage, two over each other, a line cut off).
  3. share_link: the link to give the person.

When the story needs something Jabbertoon does not have yet (a costume, a prop, a move), do not drop it: put it on the cartoon's To do list, "todo": [{"bucket": "props", "name": "a coffee pot", "for": "Rose"}], in the person's own words (get_guide start: "Plan it as five, and keep a To do list"). The person finds it in the cartoon with Make it.

To build a thing in 3D (a character, an animal, a car, a house, anything) for the person's cartoons, worlds and games: get_guide {"topic": "build"} gives the builder's steps, with a person, a car and a house to copy; then build with the steps, until ok is true. Its link opens the thing in the Forge, where the person changes it and uses it.

What the tools return

Every answer carries the canonical jabbertoon.com page for the thing it is about, so you can link your user to it. Every error has a stable code; the error codes page says what each means and how to fix it. To write programs, read the block language reference and the JSON Schemas; a plain-text overview is in llms.txt, and every pack's program text is in llms-full.txt.

What happens to what you send

When an AI assistant uses Jabbertoon's online tools to check a cartoon, it sends the cartoon to jabbertoon.com, where it is checked in memory and not kept; a written scene in it is kept until it is played, and what it found for an hour.

The tools for AI assistants, at jabbertoon.com/mcp and jabbertoon.com/api, read what they are sent, answer and forget it, all but three. report_problem keeps the report it is sent. validate, given a cartoon with a written scene (its Choreography text), keeps that scene and its cast until the server has played it, a few seconds, and what it found (the scene's length, its lines' names and times, what came nearest to what and the moments asked for, which can quote its lines) for an hour, so the same call can fetch it; then both are deleted. read_blueprint fetches the picture at the link it is given and keeps a grey copy of it (at most 1600 pixels across), that link and the walls it found, under the id it answers, so a second call can measure the plan; each is deleted once it is two days old, by the next plan read after that. For each call their log keeps only which tool was used, on which day, by which door, whether it worked, how long it took, how many bytes the request was, what kind of thing it checked, the codes of the problems it found and, for a build, how many steps and parts it had, how many were redone and which kind of step was refused, never a word of what was sent.

One tool, report_problem, is how an AI assistant tells us something is wrong, and it keeps what it is sent: the kind of problem, what it is about, a short note and the tool call that went wrong, which can hold a program (up to 4,000 characters), are saved on our server for the people who run Jabbertoon to read. Any email address in it is removed first. A report is kept until we delete it.

So put no one's personal details in a report. Nothing you send is used to train anything, and the site's full privacy notice applies to the tools as well.

The tools

ToolWhat it doesReads only?DoorsExample
make_cartoon
Make a talking cartoon from a plain script, in one call
The quickest way to a cartoon: send the script as people write one, a line each, Name: what they say, and get the jabbertoon.com link that opens it in the editor ready to play and to record as a video (free, no account). Read too: (happy, waves) in a line; [Leo walks to Mia] on a line of its own; Place: Beach (another later starts the next scene); Cast: Mia (cat). Our characters come by name (Sunny, Grump, Ria, Bob, Kiki) and a new name becomes one of our 3D cast. What was not used is in notes. Example: {"script": "Place: Beach\nMia (cat): (worried) Have you seen my hat?\nLeo: (looks around) Is it on that crab?"}.yesMCP · REST: /api/make_cartoon{"script":"Place: Beach\nMia (cat): (worried) Have you seen my hat?\nLeo: Your hat? (looks around) Is it the one on that crab?\nMia: (laughing) It looks better on the crab!\nNarrator: And so the crab kept the hat."}
A https://jabbertoon.com/cartoon/#v=1&w=1.... link that opens the cartoon in the editor: Mia the cat and Leo at the Beach, four lines; the person presses Watch, then Record video.
get_guide
Read Jabbertoon's guide for writing a cartoon
Call this first, except for make_cartoon. One topic of Jabbertoon's guide as Markdown (under 20,000 characters): start (what it makes, the order of calls, every other topic), cartoon (the JSON program), text (a cartoon as screenplay text), song (the editor's film file: lines, moves, shots, choreography, words on the picture), build (the 3D builder), export (STL, 3MF, glTF, SVG, Minecraft), minecraft (seven houses to start from, and a build taken into Minecraft), world (a 3D world built from inside, as in Minecraft), game, motion (movement written as words, jabbertoon.com/motion/). x and y are shares of the stage (0 to 1, ground 0.92); times are seconds. Example: {"topic": "cartoon"}.yesMCP · REST: /api/get_guide{"topic":"cartoon"}
How to write a cartoon as JSON: the cast, scene hats, say, does, enter and exit, with a whole example to copy.
list_moves
List the moves and words a character can do
Lists what a character can do: the Do list's moves (wave hello, hop, bow...), each with the motion language's lines that play it (a does block plays one by id), and the motion language's own words (swim_to, hover, on_guard, sneak...) with their dials. category: humanoid, mammal, bird, fish or fantasy. q: words to match, or what a word means (dance finds Groove). Example: {"q": "wave", "category": "humanoid"}.yesMCP · REST: /api/list_moves{"q":"wave"}
The moves whose words mention waving, each with what it works on, its page and its editor link.
list_characters
List Jabbertoon's ready-made cartoon characters and voices
Lists the cast in 3D by category - humanoid (the people, in costume or not; bear2, fox2, rabbit2, raccoon2, cat2), mammal (dog, cat, fox, horse, dolphin, whale), bird (gull), fish (goldfish, ten reef fish), fantasy (pegasus) - each with its designed entry, voice and word library; the voices; cartoon_example, a talking cartoon to copy. A cast entry: {"name": "Biscuit", "designed": {"kind": "animal3d", "preset": "dog"}, "voice": "am_puck"}.yesMCP · REST: /api/list_characters{}
The six ready-made characters with their legs, views, colour slots and options, the voices, and a whole talking cartoon to copy.
get_move
Get one move's program and readable text
Returns one move or word. A Do list move (by id c4c:beh:wave_hello, short name or page slug): its block program as JSON and screenplay text, the motion language's lines that play it, its length, settings, page and links. A motion language word (people.sneak, or sneak): its form, dials, bodies and whole text. Example: {"move": "wave_hello"}.yesMCP · REST: /api/get_move{"move":"wave_hello"}
Wave hello's block program as JSON, the same program as text, its length, what it works on, its page and its links.
validate
Check a Jabbertoon cartoon, scene, move, pack or character
Checks a cartoon, with the editor's own checks, before anyone sees it. Give one of cartoon, program, pack, character or file. Returns errors (it will not play as written: also a character or background the site lacks) and warnings, each {code, where, says, fix, url}, with did_you_mean and an RFC 6902 patch when certain; issues a viewer would see (off stage, overlapping, an empty stage, a line cut off) with a summary of who is where and says what when (seconds; x as a share of the stage); and, when ok, the canonical program and a link. repair: true also returns the program with every certain patch applied. A written scene is played and read out (written_scene; playing: call again), kept until played, its answer an hour; nothing else is kept. Example: list_characters' cartoon_example.yesMCP · REST: /api/validate{"cartoon":{"cast":{"dog":{"name":"Biscuit","designed":{"kind":"animal3d","preset":"dog"}},"cat":{"name":"Mia","designed":{"kind":"person3d","who":"ria"},"at":{"x":0.7,"facing":-1}}},"program":{"v":1,"kind":"cartoon","name":"Hello, Mia","scripts":[{"hat":{"on":"scene","name":"Hello"},"body":[{"op":"enter","who":"dog","from":"left","x":0.3},{"op":"does","who":"dog","behaviour":"c4c:beh:wave_hello"},{"op":"say","who":"dog","text":"Hi, Mia! Do you want to play?"},{"op":"does","who":"cat","behaviour":"c4c:beh:bounce"},{"op":"say","who":"cat","text":"Yes, please!","mood":"happy"}]}]}}}
ok is true with no errors or warnings: a talking cartoon in which a dog walks in, waves and asks, and a cat bounces and answers; the shape to copy for a cartoon of your own.
build
Build a thing in the 3D builder from steps, and link it
Builds anything (a character, an animal, a car, a house) in Jabbertoon's 3D builder from steps, as its buttons do: spine, grow, bone (a skeleton, a bone at a time), add a ready part (leg, arm, head, wing, wheel, hat ...), set, copy, remove, look. Checks every step, says what was made (its parts and size) and gives a jabbertoon.com/forge/ link that opens it in the Forge, to change and use in a cartoon, world or game. Over MCP the answer also shows a picture of it from four sides. Steps that start {"op": "new", "kind": "move"} make a move from keys, {"op": "new", "kind": "world"} a world (a level is played to check it), and a game, every one in 3D: "walk" a place to walk at real size (played on foot: told what cannot be reached), or "trench", "space", "surface" or "sky" a game to fly. A refused step says where, why and how to fix it. export_link opens Export, free: STL/3MF to 3D print, glTF (Blender, Unity, Godot), SVG, Minecraft .schem. The steps: get_guide {"topic": "build"}, a game's {"topic": "game"}.yesMCP · REST: /api/build{"steps":[{"op":"look","name":"Sam"},{"op":"add","on":"spine","preset":"head","as":"head"},{"op":"add","on":"head","preset":"hat","style":"crown"},{"op":"add","on":"spine","preset":"arm"},{"op":"add","on":"spine","preset":"leg"}]}
A https://jabbertoon.com/forge/#build=1.... link that opens Sam (a body, a head with a crown, two arms, two legs) in the Forge, and what was made: its parts, its 2 legs and its size in blocks.
read_blueprint
Read a floor plan's picture: its walls measured
Reads a floor plan's picture (https) for build: its walls found, numbered, on a grid, and an id. Call again with the id and known (one length on the plan): every wall as a wall step's from, to and thick. Then build with blueprint {id}. get_guide {"topic": "blueprint"}.noMCP · REST: /api/read_blueprint{"url":"https://commons.wikimedia.org/wiki/Special:FilePath/2_bhk_Bungalow_floor_plan.jpg"}
The sheet with its grid and its walls found, numbered, and an id; then {"id": ..., "known": {"walls": [n, m], "length": "10' 0\""}} gives each wall in the builder's units.
report_problem
Tell Jabbertoon something is wrong
Tells the people who make Jabbertoon something is wrong: a wrong answer, a check that refused a good cartoon or passed a bad one, a move that looks wrong, a link that does not open, wrong docs, something missing, or a step that was hard to get right (kind hard_step, with hard_because: optional, never needed to go on). Unlike the other tools, it keeps what you send: the report (kind, tool, code, where, item, note, hard_because) is saved for a person to read. Never put the cartoon, a name, an address or anything about the person you help in it. Example: {"kind": "validator_wrong", "tool": "validate", "code": "op_unknown", "note": "say was refused in a cartoon"}.noMCP · REST: /api/report_problem{"kind":"wrong_answer","tool":"list_moves","note":"The description of a move does not match what it does."}
The report is saved for a person to read; the answer gives its report id.