← Registry

Content Tools

renderball.com

Creates and edits presentation decks by generating outlines, rendering pages as images, and fixing layout issues.

1 endpoint8 known toolsFirst detected September 16, 2026Last detected September 16, 2026

ENDPOINT 1

https://renderball.com/api/mcp

No auth detected

MCP server metadata

Name
renderball
Version
1.1.0
Capabilities
tools.listChanged
Server instructions

Renderball turns a deck you write into a designed, animated, editable presentation the user can finish in the Renderball editor and share. Flow: (1) create_deck with the user's 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, one entry per page — the reply carries the deck_id and the WRITING BRIEF. (2) Write the complete deck file exactly as that brief specifies (a single TypeScript React file; every numeral must come from the user's material). (3) submit_deck with the file — it waits for the import; if it still reports 'importing', call deck_status until 'ready'. The ready reply carries the RENDERED PAGES as images: look at every page for overlapping or clipped text, odd spacing or an element off its page, fix the file and submit_deck again (see_deck shows the pages any time). (4) Give the user the link you get back: editor_url for an account, or deck_url for a guest deck — one link that shows the deck and has an Edit button that signs them in. Two calls for a whole deck; write_outline only exists to change the outline of an existing deck, get_brief to re-read its brief. No key? You can still make a deck. create_deck without an account returns a guest_token — pass it on every later call for that deck. Guest decks are limited per day and expire unless the user signs in through the deck's Edit button, which makes the deck theirs. Never invent facts, figures or quotes: the deck's truth check flags anything not in the brief. Ask the user for missing numbers instead of guessing.

Known tools 8

list_decks

The user's Renderball documents, newest first, with editor links.

Inferred read-only
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.

Inferred read-only
write_outline

Save the page-by-page outline you wrote for a deck.

Inferred read-only
get_brief

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

Inferred read-only
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.

Inferred read-only
submit_deck

Send the complete deck file you wrote.

Potential side effects
deck_status

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

Inferred read-only
share_deck

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

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.renderball]
url = "https://renderball.com/api/mcp"
enabled = true
Claude Code

.mcp.json

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

Settings → Connectors → Add custom connector

Name: renderball
Remote MCP URL: https://renderball.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "renderball": {
      "url": "https://renderball.com/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "renderball": {
      "type": "http",
      "url": "https://renderball.com/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "renderball",
  "transport": "streamable-http",
  "url": "https://renderball.com/api/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.