Agents build the deck
An MCP server gives Claude Code, Cursor and other agents tools to create a deck, add slides from typed building blocks, and fix what the server rejects.
Open source · In development
Your agent builds the deck over MCP from ready-made blocks: titles, comparisons, tables, charts and timelines, with no HTML. You open it by URL, share it, and present it in the browser on a laptop or a phone.
A live sample deck, rendered by the same blocks an agent fills. Click it and use the arrow keys.
An MCP server gives Claude Code, Cursor and other agents tools to create a deck, add slides from typed building blocks, and fix what the server rejects.
Every deck has a link. Open it in a browser and present on a laptop or a phone, with speaker notes and a part tracker that shows where you are in the talk.
Coming later: people join with a QR code and answer live polls, word clouds and Q&A from their phones while you drive the deck from yours.
How it works
The agent writes no HTML. It reads the layout catalogue, then sends each slide as a layout and its slots. The server checks every slot against the layout's schema and rejects a slide it can't render, naming the field that broke, so the agent can fix it and try again.
/mcp. It registers itself, and you approve it in the browser.right is required for compare: { tag, title, items[] }create_decklist_layoutsadd_slideupdate_slidemove_slidedelete_slideset_notesupload_imageset_sharingset_looklist_templateslist_palettespreview_deckget_deck_url
Building blocks
A slide is a layout plus typed slots. Here is every block in one 16-slide deck: one sentence per headline, light content slides with cards, dark slides for the title, dividers and close, and a part tracker across the top. Under each slide are the slots an agent fills.
Templates and palettes
The template holds the structure, the type and the shape. The palette holds every colour. A slide never stores a colour or a font, so the same deck looks right in any palette. Every built-in palette passes a contrast check, and the build fails if a pair drops below its bar.
talkdefaultA talk to a room: a story in parts, with one point per slide.
workshopdeep dives onA talk plus exercises the room does. Exercises are deep dives you can skip when you run late.
updateno partsA status or metrics report. Numbers first, then what is next.
Later: all 348 Sanzo Wada colour combinations as palettes, and your own templates, uploaded or imported from an HTML deck.
The app
A table, not a wall of thumbnails, so forty decks stay easy to scan. The Last change column says whether an agent or a person made it, and the deck page's activity log shows who changed what, when, and through which tool.
https://slides.example.com/mcp| Deck | Slides | Last change | Sharing | Updated | ||
|---|---|---|---|---|---|---|
| Ship smallerTeam offsite · draft | 16 | Claude via MCP · added slide 16 | Link | 2 min ago | Present | |
| Q4 platform reviewLeadership update | 22 | You · moved slide 7 | 3 viewers | 1 h ago | Present | |
| Onboarding: week oneFor new joiners | 12 | Cursor via MCP · updated notes | Private | Yesterday | Present | |
| Incident review: checkout outageBlameless write-up | 9 | Claude via MCP · created | 5 viewers | 12 Nov | Present | |
| Design crit: mobile nav | 8 | You · uploaded 2 images | Private | 9 Nov | Present | |
| Lead time, Jul–OctMetrics | 6 | Codex via MCP · updated slide 3 | Link | 4 Nov | Present | |
| Hiring loop refresh | 14 | You · deleted slide 4 | Private | 28 Oct | Present |
Keep a deck private, share it with anyone who has the link, or name the people who can view it. Agents get the same control through set_sharing.
Every change is logged with who made it and through which tool, so you can see what your agent did while you were away.
Every slot is validated against its layout's schema. A slide the player can't render never reaches the deck.
Designed · next up
The presenter window is dark, so it doesn't light up your face from the lectern. The current slide is largest, the next one waits beside your notes, and the timer turns amber with five minutes left. Scan a QR code and your phone drives the same talk. Try it: click into the window and use ← → and B, or tap Next on the phone.
Designed · coming after
Camera, then the browser, then you're in. No app, no account, no name field and no join button: the page joins on load. Phones follow the slides by themselves, and polls, word clouds and Q&A take over the card when the presenter reaches them.
0 s
The native camera spots the QR code on the join slide. Tap the chip. That is the only tap.
Ship smaller
with Sam Rivera and 23 others
No app, no account.
This page follows the slides by itself.
~2 s
The page joins on load, confirms it with a tick, and says who else is here.
from then
The current slide, kept in step with the presenter. People at the back can read it.
on an interactive slide
A poll takes over the card when the presenter reaches it, then hands back to the slide. Tap an answer.
Roadmap
Every Feature starts as reviewed mockups with its design questions answered, then ships in small pieces. The mockups on this page come straight from those designs.
SW-1FoundationDeck library, deck page, sharing, the player, the 17 blocks and the MCP server.
SW-2Templates and palettesTalk, workshop and update templates. Cobalt, Ember, Plum and Midnight. Share cards.
SW-4Presenter view and phone remoteCurrent and next slide, notes, timer, blackout, skipping deep dives, and your phone as the remote.
SW-5Audience joinA QR code and a six-digit code. Guests follow the slides with no app and no account.
SW-6+Live audience activitiesPolls, word clouds and Q&A, answered from phones in the room.
SW-15Sanzo Wada palettesAll 348 classic colour combinations, mapped to roles with contrast fixes.
SW-50Your own templatesUpload a template, or import one from an existing HTML deck.
Self-hosted and MIT licensed
One container: ASP.NET Core and a React player, with SQLite for storage. Put it behind your TLS proxy, sign in with Google, and connect any MCP client to it.
# set SLIDEWORKS_PUBLIC_URL and the sign-in keys in .env
docker compose up -d
claude mcp add --transport http slideworks \ https://slides.example.com/mcp
"Make a 20-minute deck on shipping smaller, in four parts."
Why small batches beat big plans, and how to start on Monday
One change a day beats one launch a quarter.
Why the quarter-long launch keeps slipping.
Median from first commit to the first customer using it.
Eight of our 12 launches waited on one last piece of work that had nothing to do with the rest.
“We stopped asking ‘is it done?’ and started asking ‘is it out?’ The second question is much harder to fudge.”Team lead, payments squad
How to cut work so each piece reaches a customer.
upload_image| Slice size | Review time | Rollback | Customer feedback | Verdict |
|---|---|---|---|---|
| One quarter | Days | Painful | Week 10+ | Avoid |
| One sprint | Hours | Possible | Week 2–3 | OK |
| 2–4 days | Under an hour | Flip a flag | Same week | Target |
| Under a day | Minutes | Flip a flag | Same week | Great |
Name the person who would see the change on day one.
Hard-code anything that isn't the point.
If not, what would have to change so it can?
If the answer is "nothing", pick another slice.
Unfinished work goes behind a flag, not on a branch.
To a customer if you can, and to the team if you can't.
Ship what's done, and make the rest a new story.
Every story starts with "Now a customer can …".
Small pull requests that can be reviewed in one sitting.
Release 1 needs a design, not only the final vision.