# render.ai in Claude

Connect render.ai to Claude and ask for a presentation in the chat you are already in. Claude
does the thinking, render.ai builds the slides, and you get a finished, editable deck back.
The human-readable version of this page is at `/mcp`. For driving render.ai over the
MCP or REST API, read `/agents.md`; for generation and editing costs, `/pricing.md`.

**This is a connector, not an export.** Claude does not hand you an outline to paste somewhere.
It calls render.ai, render.ai designs every slide, and the deck opens in the editor with real
text boxes and shapes you can change.

After generation, ask for changes in the same conversation: "Improve slide 3's title" or
"Make all slide titles red". Claude calls `edit_presentation`, and render.ai's editor agent
makes and checks the changes. Supported MCP Apps hosts show a live gallery during generation
and the affected slides after editing, so there is no need to ask to see them.
`get_slide_previews` opens a gallery of another deck, an earlier version or selected slides.
Presentation reads return selected content and the active theme; the theme
catalog is optional. If an edit saves no document changes, its result says so and explains why.
Ask for a PDF of a finished deck and Claude calls `export_presentation`; the card offers the
download when the file is ready.

## Three steps to your first deck

1. **Create a free render.ai account.** Do this before starting the connection — the browser
   then already holds a session, which keeps Claude's approval screen to a single tap.
2. **Add the connector in Claude.** Claude asks render.ai for permission over OAuth. There is
   no API key to copy and nothing to paste.
3. **Ask Claude for a deck**, naming render.ai in the message.

A prompt that works: *"Use render.ai to build a 10-slide investor update covering revenue,
churn, hiring and the two risks we flagged last quarter."*

Naming render.ai matters. Claude only reaches for a connector when it knows to; without the
name it will usually write an outline in the chat instead of building slides.

## Questions

**Does this cost anything?** The free plan includes credits. A completed generation uses
40 credits. Edits charge only for new or rewritten text and generated images or infographics;
theme, layout and structure changes, reads, previews and exports are free. Free-plan PDFs carry
render.ai branding. See `/pricing.md` for details.

**What if I run out of credits?** Claude can check the current balance without spending
credits. At 0 credits, edits are refused and nothing changes; viewing and exporting existing
presentations still works. See [render.ai's plans](https://render.ai/pricing) for what each
plan includes. Once credits are available, ask Claude to retry; changes already saved are kept.

**Can Claude make a Studio presentation?** No. The connector creates classic presentations;
create Studio presentations in the render.ai web app.

**Do I have to give Claude a password or an API key?** No. You create your render.ai account
first, and Claude then asks render.ai for permission over OAuth.

**Can I use it from my phone?** Yes — iPhone and Android chats work the same as desktop. The
one-time account approval may open in your browser.

**What do I get back?** A themed presentation, editable afterwards, exporting to PowerPoint,
PDF and Google Slides as real text boxes, shapes and images rather than pictures of slides.

## Related

- `/agents.md` — driving render.ai over MCP or the REST API
- `/pricing.md` — credit costs and plan limits
- `/guides.md` — one article per question about what render.ai can do and how