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 Coding agents

In Claude Code

Sign in with MakoDeck from Claude Code. No token to copy.

  1. Run this in a terminal (--scope user makes it work in every project):

  2. Claude Code, signing in · a terminal

    claude mcp add --transport http --scope user makodeck https://makodeck.com/mcp

  3. 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 each maker's own docs on 15 October 2026.

In Codex

A personal token, read from MAKODECK_TOKEN.

  1. This way needs a personal API token. Make one on Connect your AI, which has these same steps — you'll sign in first.

  2. Add MakoDeck with one command, or put the same in Codex's config by hand. The CLI, the IDE extension and the ChatGPT desktop app share it; an app started from the dock may not see MAKODECK_TOKEN, so start it from a terminal if it can't connect.

  3. Codex, in one command · a terminal

    codex mcp add makodeck --url https://makodeck.com/mcp --bearer-token-env-var MAKODECK_TOKEN

  4. Codex · ~/.codex/config.toml

    [mcp_servers.makodeck]
url = "https://makodeck.com/mcp"
bearer_token_env_var = "MAKODECK_TOKEN"

  5. If the app asks you to sign in to MakoDeck, your token didn't reach it: set MAKODECK_TOKEN (or make a new token) and restart the app, and don't finish that sign-in.

Steps checked against each maker's own docs on 15 October 2026.

In Cursor

A personal token, read from MAKODECK_TOKEN.

  1. This way needs a personal API token. Make one on Connect your AI, which has these same steps — you'll sign in first.

  2. Add this to .cursor/mcp.json, export MAKODECK_TOKEN in your shell profile, and restart Cursor (start it from a terminal if it can't see the variable).

  3. Cursor · .cursor/mcp.json

    {
  "mcpServers": {
    "makodeck": {
      "url": "https://makodeck.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:MAKODECK_TOKEN}"
      }
    }
  }
}

  4. If the app asks you to sign in to MakoDeck, your token didn't reach it: set MAKODECK_TOKEN (or make a new token) and restart the app, and don't finish that sign-in.

Steps checked against each maker's own docs on 15 October 2026.

In VS Code (GitHub Copilot)

A personal token, read from MAKODECK_TOKEN.

  1. This way needs a personal API token. Make one on Connect your AI, which has these same steps — you'll sign in first.

  2. Add this to .vscode/mcp.json in your project, and start VS Code from a terminal where MAKODECK_TOKEN is set (code .).

  3. VS Code (GitHub Copilot) · .vscode/mcp.json

    {
  "servers": {
    "makodeck": {
      "type": "http",
      "url": "https://makodeck.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:MAKODECK_TOKEN}"
      }
    }
  }
}

  4. If the app asks you to sign in to MakoDeck, your token didn't reach it: set MAKODECK_TOKEN (or make a new token) and restart the app, and don't finish that sign-in.

Steps checked against each maker's own docs on 15 October 2026.

In Gemini CLI

A personal token, read from MAKODECK_TOKEN.

  1. This way needs a personal API token. Make one on Connect your AI, which has these same steps — you'll sign in first.

  2. Export MAKODECK_TOKEN in your shell profile (Gemini CLI doesn't read it from a .env file here), then add this to its settings by hand:

  3. Gemini CLI · ~/.gemini/settings.json

    {
  "mcpServers": {
    "makodeck": {
      "httpUrl": "https://makodeck.com/mcp",
      "headers": {
        "Authorization": "Bearer ${MAKODECK_TOKEN}"
      }
    }
  }
}

  4. Gemini CLI is for paid Gemini API keys and Code Assist licences; Google moved other plans to Antigravity CLI, which this page doesn't cover yet.

  5. If the app asks you to sign in to MakoDeck, your token didn't reach it: set MAKODECK_TOKEN (or make a new token) and restart the app, and don't finish that sign-in.

Steps checked against each maker's own docs on 15 October 2026.

In Muse Code

A personal token, read from MAKODECK_TOKEN (Muse Code 1.4.4 or later).

  1. This way needs a personal API token. Make one on Connect your AI, which has these same steps — you'll sign in first.

  2. Export MAKODECK_TOKEN in your shell profile, then add MakoDeck to Muse Code's settings (if the file already exists, add only the makodeck entry under mcp_servers). It's optional, so Muse still starts if MakoDeck can't connect. Check your version with muse --version.

  3. Muse Code · ~/.config/muse/settings.json

    {
  "schema_version": 1,
  "mcp_servers": {
    "makodeck": {
      "transport": "streamable_http",
      "url": "https://makodeck.com/mcp",
      "mode": "optional",
      "headers": {
        "Authorization": "Bearer ${MAKODECK_TOKEN}"
      }
    }
  }
}

  4. If the app asks you to sign in to MakoDeck, your token didn't reach it: set MAKODECK_TOKEN (or make a new token) and restart the app, and don't finish that sign-in.

Steps checked against each maker's own docs on 15 October 2026.

Any other MCP client

Any app that can add a remote MCP server with a header.

  1. This way needs a personal API token. Make one on Connect your AI, which has these same steps — you'll sign in first.

  2. Any MCP client · its remote server settings

    Address (Streamable HTTP): https://makodeck.com/mcp
Header: Authorization: Bearer <your token>

  3. If the app can read the token from an environment variable or a secret prompt, use that (MAKODECK_TOKEN). If not, paste it only into the app's own settings — never into a file you commit or share, and never into the address.

  4. If the app asks you to sign in to MakoDeck, your token didn't reach it: set MAKODECK_TOKEN (or make a new token) and restart the app, and don't finish that sign-in.

The deck workspace

A folder set up for Claude Code: it builds, previews and publishes your decks.

  1. Download it, open it in Claude Code, and follow its README.

  2. Download the deck workspace

The Agent Skill

For an agent that loads skills: MakoDeck's guide and starter deck in one folder.

  1. Add it to your agent's skills: it builds decks by MakoDeck's guide, ready to upload.

  2. Download the skill

Have it make the files

For an agent that writes files: it builds a ZIP, you upload it.

  1. Give your agent this prompt and what the deck is about.

  2. Build a slide deck for MakoDeck. First read https://makodeck.com/llms.txt and follow it exactly. Fetch its pages raw (for example with curl), or use the skill at https://makodeck.com/ai/makodeck-skill.zip, because the code in them must be copied exactly.

Brand: use our brand kit [attach it, or describe the colours, fonts, logo and tone]. If there is none, use MakoDeck's default look.

The deck is about [topic], for [audience]. Key points: [points]. Data: [figures, with their source and date].

Deliver one ZIP with index.html at its root. Run the guide's checklist before you hand it over, and tell me the title to use when I upload it.

  3. It hands you a ZIP (or one HTML file). Open Upload, choose it, then Publish.

  4. Uploading needs a MakoDeck account: you'll sign in, or create one, first.

For agents

The guide as plain text: