Renderball

com.renderball/renderballVersion 1.1.0

Designed, animated, editable presentations your AI writes on Renderball. No account needed to try.

Status

Responds232 msNov 14, 2026, 14:12 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:12 UTC
Latency: 232 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://renderball.com/api/mcpResponds232 msNov 14, 2026, 14:12 UTC

No sign-in

Claude Code

claude mcp add --transport http renderball https://renderball.com/api/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: renderball
Remote MCP server URL: https://renderball.com/api/mcp

Cursor

{
  "mcpServers": {
    "renderball": {
      "url": "https://renderball.com/api/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"renderball","type":"http","url":"https://renderball.com/api/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

13 tools

Tools of Renderball
	Description		Read-only	Idempotent	Open world
`create_deck`Start 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 website; never invent a colour. With the outline the reply carries PAGE 1'S BRIEF; write page 1 and send it with submit_page — each reply carries the next page's brief.	Start 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 website; never invent a colour. With the outline the reply carries PAGE 1'S BRIEF; write page 1 and send it with submit_page — each reply carries the next page's brief.	No	No	Not declared	Yes
`deck_status`Whether a submitted deck is still importing, ready (with the editor link and the rendered pages, to check them), or failed (with the reason).	Whether a submitted deck is still importing, ready (with the editor link and the rendered pages, to check them), or failed (with the reason).	No	Yes	Not declared	No
`edit_page`Change 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 sending the whole page again: everything you do not touch stays as it is, the person's own edits included, and they see the change in their editor at once and can undo it. One page per call, or shared: true for the code every page shares. A refused edit changes nothing and says why. The reply shows the page as it looks now.	Change 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 sending the whole page again: everything you do not touch stays as it is, the person's own edits included, and they see the change in their editor at once and can undo it. One page per call, or shared: true for the code every page shares. A refused edit changes nothing and says why. The reply shows the page as it looks now.	Yes	No	Not declared	No
`get_brief`The writing brief for a deck whose outline is already saved.	The writing brief for a deck whose outline is already saved.	No	Yes	Not declared	No
`get_examples`Up 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.	Up 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.	No	Yes	Not declared	No
`get_page_brief`The 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 page with nothing in front of it.	The 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 page with nothing in front of it.	No	No	Not declared	No
`list_decks`The 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.	The 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.	No	Yes	Not declared	No
`read_page`Read 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 code every page shares (palette, fonts, helpers), the page's element ids and, when the person has the design open, the element they selected ("this").	Read 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 code every page shares (palette, fonts, helpers), the page's element ids and, when the person has the design open, the element they selected ("this").	No	Yes	Not declared	No
`see_deck`The 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.	The 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.	No	Yes	Not declared	No
`share_deck`Turn on the public link for a deck and return it: anyone with the link can view the deck.	Turn on the public link for a deck and return it: anyone with the link can view the deck.	Yes	No	Not declared	Yes
`submit_deck`Replace 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 poll deck_status.	Replace 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 poll deck_status.	Yes	No	Not declared	No
`submit_page`Save 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 brief; when every page is saved the deck is merged, checked and rendered and the reply carries the rendered pages. To rewrite one page of a finished design, submit just that page: it replaces that page only, and everything else stays as it is, the person's own edits included. To change part of a page, read_page and edit_page are lighter.	Save 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 brief; when every page is saved the deck is merged, checked and rendered and the reply carries the rendered pages. To rewrite one page of a finished design, submit just that page: it replaces that page only, and everything else stays as it is, the person's own edits included. To change part of a page, read_page and edit_page are lighter.	Yes	No	Not declared	No
`write_outline`Save 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.	Save 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.	Yes	No	Not declared	No

Details

Registry status: Active
Published: Sep 15, 2026
Updated: Sep 15, 2026
Website: https://renderball.com/⁠ (opens in a new tab)
Repository: https://github.com/agarces1999/renderball-skills⁠ (opens in a new tab)
Categories (suggested): DocumentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing