Renderball

Last 30 days

Uptime

100%

Response time

438 ms typical, 458 ms slowest 5%

Last check

2 h ago

Next check

in 4 h

How to call it

Add it to any MCP client that supports remote servers.

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

13 tools

• 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.

• 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 al

• 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.

• get_brief

  The writing brief for a deck whose outline is already saved.

• 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.

• 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

• 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).

• share_deck

  Turn on the public link for a deck and return it: anyone with the link can view the deck.

• 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

• 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.

• 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 carri

• 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 p

• 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 so

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks