Renderball

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.renderball/renderball and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 15 Oct 2026. Not supplied by the maker.

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

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

• 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

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