Build decks with AI
Your AI builds the deck from MakoDeck's guide, in your own brand. Some AIs publish it here themselves once they're connected; any AI can hand you a deck to upload.
Which AI do you use?
Connect Claude
In the Claude app
Add MakoDeck as a connector and sign in. No token to copy.
On claude.ai or in the desktop app, open Customize → Connectors, click + Add, then Add custom connector. Name it MakoDeck and give it this address:
https://makodeck.com/mcp
Keep "Use Claude's published identity" for the OAuth client, add it, then sign in to MakoDeck and allow. It works on your phone too once it's added.
On a Team or Enterprise plan, an Owner adds it once in Organization settings → Connectors (Add → Custom → Web), and each person clicks Connect under Customize → Connectors.
Steps checked against Claude's own docs on 15 October 2026.
In Claude Code
Sign in with MakoDeck from Claude Code. No token to copy.
Run this in a terminal (--scope user makes it work in every project):
Claude Code, signing in · a terminal
claude mcp add --transport http --scope user makodeck https://makodeck.com/mcp
Then, in Claude Code, type /mcp, pick makodeck and choose Authenticate (or run claude mcp login makodeck). Your browser opens MakoDeck: sign in and allow.
Steps checked against Claude's own docs on 15 October 2026.
The deck workspace
A folder set up for Claude Code: it builds, previews and publishes your decks.
Download it, open it in Claude Code, and follow its README.
- Download the deck workspace
In a Claude chat
Copy a prompt in, paste the deck it writes back. Nothing to connect.
Paste this into a new Claude chat, then fill in what the deck is about.
Build a slide deck I can paste into MakoDeck (https://makodeck.com): ONE self-contained HTML file. If you can open web pages, read https://makodeck.com/llms-full.txt first and follow it exactly, except where it asks for a ZIP or separate files: the lines at the end win. Either way, follow these rules: 1. Mark the deck native: `<html data-mako-deck>`, one `.deck`, and one `<section class="slide …">` per slide directly inside it, each with a layout class: `slide--title`, `slide--section`, `slide--content`, `slide--closing`. Nothing else has the class `slide`, and nothing else in `<body>` shows: a header outside the `.deck`, or a wrapper around a slide, adds a page to the PDF (https://makodeck.com/ai/format.md). 2. Let MakoDeck run the slides: it shows one at a time, scales the 1920×1080 frame to the window, moves between them and prints each on a page of its own. Add no navigation script, `is-active` class, scaling or print CSS, and never hide a `.slide` yourself (https://makodeck.com/ai/format.md). 3. Fit every slide in 1920×1080: nothing scrolls, clips or overflows — split long content into "(cont.)" slides. Body text at least 20px and nothing under 18px; text contrast at least 4.5:1, even in the brand's colours; status written as a word, never shown by colour alone (https://makodeck.com/ai/brand-and-design.md). 4. Title every slide (`aria-labelledby` naming its heading) and put its speaker notes in `<aside class="notes">` inside it (https://makodeck.com/ai/format.md). 5. Deliver one ZIP with `index.html` at its root, or a single `.html` file when there is nothing else to bundle. Keep the deck in that one page, use relative paths only, put every file it uses in the ZIP, and add no top-level `_mako/` folder (https://makodeck.com/ai/packaging.md). 6. Load nothing from another site — no CDN scripts, font or image URLs, API calls or embedded pages. Use the site's pinned libraries at `_mako/lib/` (https://makodeck.com/ai/interactive.md) and bundle everything else. 7. Put the brand font FIRST in every font list. Inter, any Google Fonts family and the workspace's own fonts work by name; bundle any other font with `@font-face` and its licence (https://makodeck.com/ai/brand-and-design.md). 8. Put the client's brand kit into the skeleton's BRAND TOKENS; with no brand kit, keep them — they are MakoDeck's default look. Never invent a logo, and put no MakoDeck branding on the slides (https://makodeck.com/ai/brand-and-design.md). 9. Never invent figures, names, dates or sources, not even "to show the layout": every number on a slide comes from the brief, or plain arithmetic on it. Delete the rest, don't build slides the data can't fill, and label recommendations the brief didn't give "Draft for discussion" (https://makodeck.com/ai/workflow.md). 10. Put no secrets, keys, passwords or private data in any file: anyone who can view the deck can read every file and every line of code. 11. Code is optional. A slide drawn by code uses `Mako.onSlide`, shows its finished state at once when `still` is true, finishes within about 3 seconds and uses seeded randomness; a part of a slide that takes clicks or keys itself is a control (`<button>`, `<a>`) or sits inside `data-interactive`, or a click on it also changes slide (https://makodeck.com/ai/interactive.md). Because I'll paste your answer in, also: - One file only: no ZIP, and no separate CSS, script, image or font files. Put all the CSS in one `<style>` element, and draw icons and charts as inline SVG. - Show a logo only if I paste its SVG code: use it exactly as given. Otherwise use no logo. - Load nothing from another site: no image URLs, no CDN scripts or stylesheets, no Google Fonts link. Name Inter or any Google Fonts family in `font-family` and MakoDeck supplies it. - No photos: use SVG shapes, or a labelled placeholder box where an image would go. - If you can't open the skeleton deck (https://makodeck.com/ai/skeleton.md), put the brand's colours and fonts in CSS custom properties at the top of the `<style>`. - Put the deck's title in its `<title>`. Reply with the whole file in ONE code block, from `<!doctype html>` to `</html>`, with nothing left out (never "the rest is unchanged") and nothing after it. I'll publish it with MakoDeck's "Paste the code". The deck is about [topic], for [audience]. Key points: [points]. Data: [figures, with their source and date]. Brand: [colours, fonts and tone, or use MakoDeck's default look].
It answers with the whole deck as one HTML file. Copy that, open Upload, choose Paste the code and paste it in, then Publish.
Uploading needs a MakoDeck account: you'll sign in, or create one, first.
For agents
The guide as plain text:
- llms.txt — the index and the rules
- llms-full.txt — the whole guide in one file
- Workflow
- Connect and publish
- Deck format
- Skeleton deck
- Packaging
- Sandbox
- Brand and design
- Interactive slides
- Checklist
- Warnings
- Share a deck