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 Sept 2026. Not supplied by the maker.

• list_decks

  The user's Renderball documents, newest first, with editor links. Needs an account (a key).

• create_deck

  Start a new presentation from a brief, the brand as YOU know it (name, and only the colours, fonts and logo you actually have — never guess a colour) and your outline. With the outline the reply carri

• write_outline

  Save the page-by-page outline you wrote for a deck. Returns the WRITING BRIEF: the exact instructions for writing the deck file (format, brand facts, truth rules). Follow it, then call submit_deck.

• 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 or an element off its page, then fix the file and submit_deck again. Available once the de

• submit_deck

  Send the complete deck file you wrote. Renderball checks it against the brief, repairs small slips, renders every page and opens it in the editor. Returns 'ready' with the editor_url, or 'importing' —

• deck_status

  Whether a submitted deck is still importing, ready (with the editor link), or failed (with the reason).

• share_deck

  Turn on the public link for a deck and return it.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.