Blender integration through the Model Context Protocol
Renderball is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Designed, animated, editable presentations your AI writes on Renderball. No account needed to try.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http renderball-mcp https://renderball.com/api/mcp
# 2 — ask your agent for something these tools do
# list_decks, create_deck, write_outline and 10 more
Renderball costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http renderball-mcp https://renderball.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
13 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 parameter schema on file.
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 i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| brief | string | yes | What the deck is for, who it is for, what it should argue and ask. Real facts only; the truth check refuses invented figures. |
| brand | object | no | The brand as YOU know it: name, and only the colours, fonts and logo you actually have. Never guess a colour; leave it out. |
| brand_url | string | no | Key holders only: a website Renderball reads for colours, fonts and logo when no brand is declared. |
| pages | integer | no | How many pages you intend to write (default 5). Ignored when outline is given. |
| size | string | no | The page size: wide 1920×1080 (slides, the default), square 1080×1080 (a post), vertical 1080×1920 (a story, a poster, a menu). Pick the size the person asked for: never draw a page turned sideways to |
| outline | object | no | Your page-by-page outline (one entry per page: label, description, visual_concept, content with a headline). Send it here and the reply carries the brief to write from (page 1's brief when the deck is |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deck_id | string | yes | — |
| tone | string | no | The register, e.g. 'confident, technical, CTO-to-CTO'. |
| pages | array | yes | — |
The writing brief for a deck whose outline is already saved.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deck_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deck_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deck_id | string | yes | — |
| source | string | yes | The complete deck file, exactly as the writing brief specifies. Raw file or a ```tsx fenced block. |
| label | string | no | Who wrote it, e.g. 'claude-code'. Shown in the deck's trace. |
| wait_seconds | integer | no | How long to wait for the import before returning (default 25). Use deck_status to keep checking. |
Whether a submitted deck is still importing, ready (with the editor link and the rendered pages, to check them), or failed (with the reason).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deck_id | string | yes | — |
Turn on the public link for a deck and return it: anyone with the link can view the deck.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deck_id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deck_id | string | yes | — |
| page | integer | yes | Which page, 1 first. Page 1 must be saved before any other page's brief. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deck_id | string | yes | — |
| ids | array | yes | Up to 4 example ids from the page brief's list, e.g. ["L3", "R12"]. |
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 re
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deck_id | string | yes | — |
| page | integer | yes | — |
| source | string | yes | Page 1: the file with Section0 and every shared constant, helper and chrome. Page N: ONLY export const Section{N-1}. Raw code or a ```tsx fenced block. |
| direction | string | yes | This page's direction in one sentence — the thing, the motion that acts out the claim, one craft detail. It goes into the page as its // Direction: line. |
| next_brief | boolean | no | Default true: the reply carries the next page's brief. A helper writing just one page sends false. |
| label | string | no | Who wrote it, e.g. 'claude-code'. Shown in the deck's trace. |
| wait_seconds | integer | no | When this page completes the deck: how long to wait for the import (default 25). |
| page_id | string | no | Rewriting a page of a finished design: the page_id read_page gave. If the person moved pages since, it is refused instead of replacing another 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 de
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deck_id | string | yes | — |
| page | integer | yes | Which page, 1 first. |
| with_shared | boolean | no | Default true: also return the code every page shares (palette, fonts, helpers). Send false when you already have it in this conversation. |
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 in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deck_id | string | yes | — |
| page | integer | no | Which page to change, 1 first. Leave out only with shared: true. |
| shared | boolean | no | true: the edits are to the code every page shares (palette, fonts, helpers), as read_page shows it. Only when the person asks to change the whole design. |
| edits | array | yes | Applied in order, all or nothing. |
| summary | string | no | What you changed, in a few plain words the person sees in their editor, e.g. 'Shortened the headline'. |
| page_id | string | no | The page_id read_page gave for this page. If the person moved pages since, the edit is refused instead of landing on another page. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Renderball or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Renderball can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.