Skip to content
Agentmart
Submit a tool

Renderball

Designed, animated, editable presentations your AI writes on Renderball.

Connector by renderball.comOfficial · Domain verified by the MCP Registry

IndexedLicense unknownRemote (HTTP)
Write a review

Install

Works with Claude Code, VS Code, Cursor, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install connector/renderball-com-renderball

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Remote endpoint

  • https://renderball.com/api/mcp Remote (HTTP)

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
6 read · 2 write · 5 delete
Secrets
None asked for
Install scripts
Nothing to install (hosted)
Runs as
Hosted (remote endpoint)

Tools by what they do 13

From the running server's own tool list (tools/list) on Oct 25, 2026.

Read 6 · Look things up without changing anything.

  • deck_status
  • get_brief
  • get_examples
  • list_decks
  • read_page
  • see_deck

Write 2 · Create, change, send or run things.

  • create_deck
  • get_page_brief

Delete 5 · Delete, drop, revoke or wipe things.

  • edit_page
  • share_deck
  • submit_deck
  • submit_page
  • write_outline

Network hosts it talks to 1

  • renderball.com · found in remote endpoint, install command

Files it touches

  • Any path the agent passes to its tools

Tools (13)

As the server listed them on Oct 25, 2026. Descriptions are the server’s own words; hidden characters are shown as [U+…].

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

  • deck_statusCheck an importread-only

    Whether a submitted deck is still importing, ready (with the editor link and the rendered pages, to check them), or failed (with the reason).

  • edit_pageChange part of a pagecan change or delete data

    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…

  • get_briefGet the writing briefread-only

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

  • get_examplesRead example pagesread-only

    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.

  • get_page_briefGet one page's 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.

  • list_decksList my decksread-only

    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.

  • read_pageRead one pageread-only

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

  • see_deckSee the rendered pagesread-only

    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.

  • share_deckShare a deckcan change or delete data

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

  • submit_deckSubmit the deck filecan change or delete data

    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.

  • submit_pageSubmit one pagecan change or delete data

    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…

  • write_outlineWrite the outlinecan change or delete data

    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.

Signals

Last release
Sep 15, 2026 (1 month ago)
Repository
Not found on GitHub (deleted or private)

Details

Registry name
com.renderball/renderball
Version
1.1.0
Auth
Auth not stated
License
License unknown
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Cite this page

Renderball MCP server. Agent Mart. https://agentmart.dev/connectors/renderball-com-renderball (last updated 2026-10-24)