All servers · Other
Renderball
com.renderball/renderball · v1.1.0
Has write/delete tools
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Has destructive tools (destructiveHint) |
| Capabilities declared | tools |
| Tool definitions | 13 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Designed, animated, editable presentations your AI writes on Renderball. No account needed to try.
Connect
streamable-http · https://renderball.com/api/mcp
claude mcp add --transport http renderball https://renderball.com/api/mcp{
"mcpServers": {
"renderball": {
"url": "https://renderball.com/api/mcp"
}
}
}Tools as reported by the server
list_decksThe user's Renderball documents, newest first, with editor links. Needs an account (a key). The design open in the person's editor right now comes first, marked open_now.create_deckStart a new presentation from a brief, the brand and your outline. The brand: if you can open the brand's website, read its real colours and fonts there first and declare them — the lead colour is usually the main buttons and the large coloured areas, not the link colour — and always give the websitwrite_outlinewrite/deleteSave a new page-by-page outline for a deck (pages written for the old one are dropped). The reply carries PAGE 1'S BRIEF; each submit_page reply carries the next page's.get_briefThe writing brief for a deck whose outline is already saved.see_deckThe deck's rendered pages as images, page 1 first — look at them for overlapping or clipped text, odd spacing, an element off its page or a picture that does not say its page's claim, then fix that page and submit_page it again. Available once the deck has been rendered.submit_deckwrite/deleteReplace the whole file of a deck whose pages are all written (while pages are still being written, submit_page each one — a whole file is refused then). Renderball checks it against the brief, renders every page and opens it in the editor. Returns 'ready' with the editor_url, or 'importing' — then pdeck_statusWhether a submitted deck is still importing, ready (with the editor link and the rendered pages, to check them), or failed (with the reason).share_deckwrite/deleteTurn on the public link for a deck and return it: anyone with the link can view the deck.get_page_briefThe full writing brief for ONE page: the studio's method, the rules, the examples chosen for that page, and (after page 1) page 1's file to continue. You rarely need it: page 1's brief comes with create_deck and each submit_page reply carries the next page's. Use it for a helper that writes one pageget_examplesUp to 4 of the studio's example pages, by the ids listed in a page brief — read the ones that fit the page you are about to write.submit_pagewrite/deleteSave one page you wrote (page 1: the file with Section0 and the shared design; page N: only its Section), with its direction (one sentence: the thing, the motion that acts out the claim, one craft detail). A page is accepted only after its brief was handed to you. The reply carries the next page's bread_pageRead one page of a design as it is NOW — the code the person's editor shows, including their own edits — before changing it. Use it whenever the person asks to change something in a design that already exists: their editor may hold edits you have not seen. The reply carries the page's code, the codeedit_pagewrite/deleteChange part of a design that already exists, the way you edit a file: each edit replaces exact text from read_page (it must appear exactly once) with new text. Use it for any change the person asks for in an existing design — a headline, a colour, a picture, moving or removing something — instead of
Repository · Website · JSON · Text for agents · Registry updated 2026-09-15