Slidura MCP Server

Slidura exposes its full functionality as an MCP server at https://app.slidura.com/mcp. Any MCP-compatible client — Claude Desktop, a PydanticAI agent, your own pipeline — can discover templates, read annotated catalogs, create and edit builds, upload content, and download finished decks.

Endpoint

https://app.slidura.com/mcp

Transport: streamable HTTP (official mcp SDK).
Authentication: API key as a Bearer token.
Mint a key: app.slidura.com/settings/api-keys.

The full tool suite

The MCP server currently exposes 42 tools across the complete workflow:

Discovery and catalog

• list_templates, get_template, get_catalog — find a template, read the annotated catalog (your agent’s brief).
• get_template_theme, set_template_theme — read and write the deck’s design palette for on-brand content.
• request_enrichment, get_enrichment_status — trigger optional vision enrichment and poll it.
• get_fill_schema — the fill document format, with a worked example.

Build lifecycle

• create_build — open a new build to edit before spending a credit.
• update_build_fill — replace the working fill (lenient validation; full pipeline runs at start).
• start_build — validate, spend one credit, and enqueue.
• copy_build — copy any build into a fresh editable one (the reopen path for archived builds).
• list_builds, get_build_status, get_build_result — poll and retrieve the signed download URL.
• submit_build — one-shot alternative: submit fill and start in a single call.

Ref search

• search_refs — unified search across all your stored assets, returning paste-ready @kind:id refs. Pass a context of open build/template ids to rank scoped items first.

Content creation

• Charts: create_chart, list_charts, get_chart
• Tables: create_table, list_tables, get_table
• Images: request_image_upload, confirm_image, list_images, get_image
• Icons: list_icon_packs, get_icon_catalog, search_icons, enrich_icon, get_icon_ref
• Diagrams (Mermaid → SVG): create_diagram, get_diagram_status, get_diagram
• Code blocks: create_code_block, list_code_blocks, get_code_block
• Procedural arts (SmartArt-style): list_art_layouts, create_art, get_art

Account

• get_account — your credit balance.

The recommended agent loop

create_build(catalog_id, fill_json?)
  → update_build_fill(build_id, fill_json)   # iterate as needed
  → start_build(build_id)                    # spends one credit
  → poll get_build_status until "completed"
  → get_build_result → signed download URL

Use search_refs at any point to find stored assets; drop @chart:id, @image:id, @art:id, etc. directly into fill values.

Download the agent skill

Every template workspace has a downloadable agent skill — a ready-made Claude Code skill file with your catalog pre-wired. Open the template, go to the Overview tab, and download it. Drop it into your .claude/skills/ folder and your agent already knows the fill contract for that template.

Connect in one paste

Add this to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "slidura": {
      "url": "https://app.slidura.com/mcp",
      "headers": {
        "Authorization": "Bearer slidura_live_..."
      }
    }
  }
}

Restart Claude Desktop and the full Slidura tool suite appears.

Full instructions: Connect Claude Desktop →.

Scoped API keys

Each key carries coarse per-route scopes: read, write, delete, build. Mint a read-only key for catalog discovery; add build only for agents that submit builds. Revoke any key at any time from /settings/api-keys.

Why MCP-first

Slidura’s split is deliberate: the mechanical work — scanning and filling .pptx — runs server-side; the intelligent work — deciding what content goes in each field — runs on your machine, with your model, under your control. MCP is the cleanest protocol for that boundary.

Tool reference → · Reference agent → · Signed download URLs →