Deck context protocol
DeckCP is a deck editor with a CRM inside. Your AI writes the slides, one link tracks every read, and the follow-up goes out from the same place.
⌘K tell the copilot what to changetap the mic — tell the copilot what to change
PowerPoint or PDF in — a tracked, AI-editable link out. The sandbox needs no signup.
deck://seed-round · read trackingsnapped
deck://pipeline
A pitch deck is a sales tool — so it should tell you how the sale is going. Gate the deck with an email and every viewer is a named lead. Watch them move across the board as they read, and follow up while you're still on their mind.
Share it public, or ask for an email at the door. Named viewers, not anonymous hits.
Who opened it, who finished it, and which slide they sat on. If they lingered on the ask, you want to know today.
The follow-up ties to the deck and the read — not to a Zapier run between four tools.
slide 2 · just now
slide 3 of 9…
9/9 · 8m total
replied ✓
deck://loop
Your AI already knows your company — the memo, the numbers, last week's thread. So you don't gather anything; you just ask. Claude, ChatGPT, Cursor, anything that speaks MCP builds the deck on your brand.
Share a link and see who actually read it. Then nudge anything by hand — same deck, no re-export, no version soup.
It already has your context — memo, metrics, past chats. Ask in plain words and it writes the slides, on your brand.
One link, not an attachment. Anyone you send it to opens the real thing — and you keep the read receipts.
Who opened it, and which slides they actually spent time on. Update the deck; the link they have stays current.
Drag anything onto the grid. It saves itself — the link stays the same.
deck://anywhere
No pinching, no tiny handles. Say the change and watch the slide snap into place. It is the same editor you use at your desk.
One button, bottom right, where your thumb already sits.
Captions show you what it heard, as you talk.
The slide updates on the grid and saves itself.
$ claude mcp add deckcp
you: turn these notes into a deck
deckcp: built 8 slides →
deck://agents
DeckCP is the MCP for decks — the open standard that lets an AI assistant work inside other apps. Connect Claude, ChatGPT, or Gemini once, and it can build and edit your decks right here, the same ones you polish by hand.
One line points your assistant at DeckCP. Sign in happens in your browser — no keys to paste.
“Turn my notes into a deck.” It writes the slides, in order, on your brand.
The deck lands in your editor, ready to drag, tweak, and send.
Not a video. This is the real DeckCP editor with your own copy of a deck. Drag something and watch it snap.
deck://manifesto
So tell yours to a room that can't ghost you. A DeckCP link reports back — who listened, where they leaned in, and when to make the call.
open a sandbox deck → no signupYou talk, it builds the slides. You send it, it reports back. Here is the rest.
The share link reports back: who opened the deck, which slides they sat on, and for how long. Slide by slide, not just “opened”.
slide 7 · the traction slide · 2m 14s
Talk through the raise, or paste your notes. DeckCP sorts them into slides with a clear order and a clean layout.
Gate the deck with an email and every viewer is a name, not a hit. The follow-up ties to the deck — no Zapier run between your slides and your CRM.
Set your fonts, colors, and logo once. Every deck after that comes out matching, no matter who makes it.
Export to PowerPoint or PDF when an investor insists on a file. Send the link when you’d rather know what happens after you hit send.
DeckCP speaks MCP — the open protocol AI assistants use to work other software. So Claude, ChatGPT, or Gemini can build and edit the same decks you do.
Share the deck and work on it at the same time. You see your teammates' changes as they make them.
We wrote a head-to-head for each one — where they're strong and where we differ. No spin.
See the full comparison