---
name: deckcp
description: Create, edit, and render slide decks with DeckCP. Use when the user wants a slide deck, presentation, pitch deck, or keynote, or wants to edit, review, or render slides on deckcp.com. Works through the deckcp MCP server; includes connection instructions if the tools are missing.
---

# DeckCP — slide decks over MCP

DeckCP turns text into rendered 1920×1080 slide decks. All work happens
through the `deckcp` MCP tools. Humans see the same decks live in the
visual editor, so edits land in front of them immediately.

## If the deckcp tools are missing

The MCP server is not connected yet. Connect it, then continue:

- Claude Code: `claude mcp add --transport http deckcp https://deckcp.com/api/mcp`
- Claude Desktop / claude.ai: Settings → Connectors → Add custom connector → `https://deckcp.com/api/mcp`

A browser window opens once for Google sign-in; the token is revocable and
scoped to one DeckCP user.

## Workflow

1. `whoami` once to confirm which account you act as; `list_decks` /
   `get_deck` to orient.
2. Before writing slide MDX by hand, read `get_authoring_guide` (rendering
   contract + component catalog: charts, diagrams, timelines, ~60 entries)
   and `get_brand` (palette, logos, non-negotiable rules). Never guess
   class names or component props.
3. Fast path from prose: `generate_outline` → show the human →
   `generate_slides_from_outline`. One-shot: `generate_slides_from_text`.
4. Manual authoring: run `check_slide` on each slide's MDX before
   `upsert_slides` — it is instant and catches classes that silently don't
   render. Use `slide_order` gaps of 10 (10, 20, 30…).
5. Always `render_slides` after writing and look at the images. Never
   declare a deck done without seeing it rendered.
6. Iterate per slide with `rewrite_slide` — it persists the edit and
   returns a fresh check report.
7. Real media only: `upload_asset` or `search_assets`. Never hot-link or
   invent image URLs.

## Pitfalls

- "Not authorized to edit/read deck X" is per-deck access, not a token
  problem. Retrying will not help — ask the user to share that deck with
  the email `whoami` returns, or work in a deck owned by their org.
- A 401/token error IS a token problem — reconnect the connector.

Machine-readable overview of the whole surface: https://deckcp.com/agents.md