Slidura — Your PowerPoint template, filled by your AI agent on Slidura

Automate PowerPoint proposals

Mon, 01 Jan 0001 00:00:00 +0000

Automate PowerPoint proposals

(TODO: long-form landing page for the consultant ICP. The “stop being a copy-paste machine” angle. Before/after screenshots. CTA to /pricing/ and /docs/getting-started/first-deck-in-10-minutes/.)

Charts

Mon, 01 Jan 0001 00:00:00 +0000

Charts

Place data-driven native charts into your PowerPoint slides. The template owns the chart type and styling; your fill supplies the data.

How charts work

When Slidura scans a template, any existing chart shape becomes a chart field in the catalog. The catalog records the chart type (bar, line, pie, …), the number of series, and the category labels — the shape signature. Your fill provides new categories and series values; the build patches the chart’s data caches and embedded workbook in-place without touching the template’s colours, data labels, or number formats.

Connect Claude Desktop

Mon, 01 Jan 0001 00:00:00 +0000

Connect Claude Desktop

One-paste setup, plus troubleshooting for the things that go wrong.

Prerequisites

A Slidura account — access is by private beta invitation. Request access.
An API key — account dropdown → API keys → New. Copy it now; it is shown once. Keys carry scopes: read, write, delete, build.
Claude Desktop installed.

Add the server

Open claude_desktop_config.json:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Add (or merge into) the mcpServers block:

First deck in 10 minutes

Mon, 01 Jan 0001 00:00:00 +0000

First deck in 10 minutes

The fastest path through the whole Slidura loop: sign in → upload → catalog → fill → build → download.

Before you start

Slidura is in private beta. If you don’t have access yet, email hello@slidura.com to request it. Once accepted, sign in at app.slidura.com/login via email magic-link or Google.

You’ll also need a .pptx template to try. If you don’t have one, starter templates are available in the templates home — no upload required.

Templates and versions

Mon, 01 Jan 0001 00:00:00 +0000

Templates and versions

⚠️ This page is a stub — full write-up coming soon.

A named handle and the immutable .pptx blobs under it.

The fill builder

Mon, 01 Jan 0001 00:00:00 +0000

The fill builder

The fill builder is the editing surface for a created build, reached at /builds/{id}. It is structured into three tabs: Assistant, Slides, and Values.

Slide thumbnails and field locator

The Slides tab shows a thumbnail for each slide. When a PDF export was uploaded with the template, each thumbnail is the real slide image with filled values overlaid. If no PDF was uploaded, the fallback is a server-rendered SVG mock (see below).

Fill a PowerPoint template via API

Mon, 01 Jan 0001 00:00:00 +0000

Fill a PowerPoint template via API

(TODO: long-form landing for the automation-engineer ICP. The /api/v1 shape, an end-to-end curl walkthrough, error handling, idempotency notes.)

Tables

Mon, 01 Jan 0001 00:00:00 +0000

Tables

Place tabular data into PowerPoint tables. The template owns the table style and banding; your fill drives the row and column count.

How tables work

When Slidura scans a template, any existing table shape becomes a table field in the catalog. The catalog records the current row count, column count, and the table style ID. At build time the engine reshapes the template table — adding or removing rows and columns to match your data — then writes cell content. The table’s style, banding, and header formatting are never touched, so the output stays on-brand regardless of how many rows your data has.

The build assistant

Mon, 01 Jan 0001 00:00:00 +0000

The build assistant

The build assistant is an optional hosted chat available on the Assistant tab of a created build. It helps you draft the working fill by reading the template brief, searching your assets, and writing suggested values — using the same draft-validation path as any external agent or API call.

The assistant is server-side AI and requires GOOGLE_API_KEY to be configured on the Slidura instance you are using. If the tab is absent, the assistant is not available on that instance.

How it works

You type a message on the Assistant tab — typically a brief description of the deck you want (topic, audience, key points).
The assistant reads the annotated catalog (the field names, descriptions, and agent hints you set during annotation) and the current working fill, then calls a read-only asset search tool to find relevant images, charts, or other media from your library.
It replies with a chat message and, when it has enough information, writes a complete updated fill into the build. That fill goes through the same draft validation as any other write — the assistant cannot bypass it.
When the assistant needs more information it may ask structured questions, rendered as an inline answer form in the chat thread. Fill in the answers and submit the form to continue.

Honest caveats

No streaming. Each turn is a synchronous round-trip. Replies appear after the full response is ready.
Conversations persist per build. Closing the tab and returning later resumes the same thread. Conversations are scoped to one build and are not shared across builds.
The human presses Build deck. The assistant only edits the working fill; it never starts the build engine. Review the Slides and Values tabs before clicking Build deck.
Server-side AI is opt-in. Simply not using the Assistant tab sends no data to the assistant’s model provider. The fill builder (Slides and Values tabs) works entirely without it.
Rate-limited. Turns are rate-limited per user to prevent runaway spend.

The underlying model

The assistant uses Gemini (default gemini-2.5-flash, configurable via ASSISTANT_MODEL). See specs/user-experience/assistant-spec-v1.md for the full technical spec.

The catalog

Mon, 01 Jan 0001 00:00:00 +0000

The catalog

A catalog is Slidura’s machine-readable view of a .pptx: every slide, every fillable field, in reading order. It’s produced once per template version by a background catalog job and stored as JSON.

(TODO: full write-up — full vs compact, what counts as a field, how pptx_field_id differs from the editable field_id, where the JSON lives.)

Tool reference

Mon, 01 Jan 0001 00:00:00 +0000

Tool reference

Slidura exposes 42 MCP tools across eight areas. All tools require a valid API key (account dropdown → API keys). Individual tools note the scope they require where it differs from the default read scope.

Recommended agent loop

The recommended sequence for producing a finished deck:

list_templates — pick a template and note its catalog_id.
get_catalog — read the annotated field brief and theme palette.
create_build — open a draftable build (no credit spent yet).
(optional) create media assets (create_chart, create_diagram, etc.) and use the returned @kind:<id> sentinels as field values.
update_build_fill — write or revise the working fill (lenient validation; repeatable).
start_build — validate, spend one credit, and enqueue. Raises with a checkout URL when the balance is zero.
get_build_status — poll until status is "completed".
get_build_result — receive a short-lived signed download URL for the .pptx.

One credit is spent per start_build call. If the build fails the credit is refunded automatically.

Upload your template

Mon, 01 Jan 0001 00:00:00 +0000

Upload your template

⚠️ This page is a stub — full write-up coming soon.

What makes a good .pptx for Slidura.

Variables and typed values

Mon, 01 Jan 0001 00:00:00 +0000

Variables and typed values

Annotation turns a raw catalog into a reusable product. Two tools drive that transformation: per-field typed values (defaults, choices, and a strict/suggestion flag) and head variables (catalog-level {{name}} placeholders interpolated once at submit).

Per-field defaults and choice lists

Every field in the Variables view of the template workspace can carry:

Default value — the text (or ref sentinel like @icon:starter/star) used when a caller omits that field from the fill. Explicit values always win; hidden fields never receive a default.
Choices — an ordered list of allowed values. Up to 50 choices, each non-empty and unique. When a caller sends a string value outside the list, the build is rejected with a validation error that names the field and its allowed values.
Strict vs suggestion — a field with choices either enforces the list strictly or treats it as a suggestion set for the fill builder UI.

In the fill builder, a choices-bearing field renders as a <select>. The first option is “use default” (or “keep template content”) with an empty value; omitting the field is equivalent to selecting the default. A text field with a default shows it as a placeholder.

Annotate the catalog

Mon, 01 Jan 0001 00:00:00 +0000

Annotate the catalog

⚠️ This page is a stub — full write-up coming soon.

Turn auto-named fields into a great agent brief.

Annotations as the agent brief

Mon, 01 Jan 0001 00:00:00 +0000

Annotations as the agent brief

⚠️ This page is a stub — full write-up coming soon.

The human-in-the-loop quality step that turns auto-named fields into a clear brief for your agent.

Images

Mon, 01 Jan 0001 00:00:00 +0000

Images

Upload a raster or vector image once; reference it from any fill. The build embeds it into image_N picture-frame fields in the finished deck.

How images work

Slidura’s scanner detects picture-frame shapes in a template and records them as image fields in the catalog. At build time the filler replaces the placeholder with your image, cropped and scaled to fill the frame exactly as PowerPoint would.

Supported formats: PNG, JPG, GIF, SVG. Each file is validated on confirm (magic-byte check, dimension cap, decompression-bomb guard) before being stored privately in object storage.

Let Claude fill your deck over MCP

Mon, 01 Jan 0001 00:00:00 +0000

Let Claude fill your deck over MCP

(TODO: long-form landing for the AI-forward / MCP-directory crowd. The “intelligence on your machine” architecture, the tool suite, the one-paste config, a worked Claude conversation.)

Published fill endpoints

Mon, 01 Jan 0001 00:00:00 +0000

Published fill endpoints

A published fill endpoint lets an external system POST plain data and receive a finished deck — no Slidura account, no fill builder, no MCP client. You publish a draft from a template, receive a capability token, and hand the URL to whatever system produces the data.

How it works

In the template workspace, open the Usage tab and create an endpoint. Give it a name, optionally set a callback URL and a monthly build cap, then click Publish. Publishing snapshots your current draft — the slide selection, order, and any pre-filled values — as the endpoint’s default_fill. The token (sfe_…) is shown once; copy it.

Signed download URLs

Mon, 01 Jan 0001 00:00:00 +0000

Signed download URLs

⚠️ This page is a stub — full write-up coming soon.

How the finished .pptx leaves the MCP channel.

Build and download

Mon, 01 Jan 0001 00:00:00 +0000

Build and download

⚠️ This page is a stub — full write-up coming soon.

Submit a fill.json, watch the job, download the deck.

Design palette

Mon, 01 Jan 0001 00:00:00 +0000

Design palette

Every .pptx embeds a PowerPoint theme: a color scheme of ten named slots and a major/minor font pair. Slidura reads this palette once at catalog time and uses it as the single source of truth for all auto-derived color schemes across your template.

What the palette contains

Slot	Role
`dk1`, `lt1`	Primary text / background pair
`dk2`, `lt2`	Secondary text / background pair
`accent1` – `accent6`	Brand accent colors

Plus major_font (headings) and minor_font (body text).

Icons

Mon, 01 Jan 0001 00:00:00 +0000

Icons

Replace template icon carriers with glyphs from any SVG icon pack. Icons land in the finished deck as native vector shapes — no raster fallback.

How icons work

The scanner detects three kinds of icon carrier in a template: SVG-picture shapes, textless autoshapes used as placeholder icons, and icon-font glyph runs. Each becomes an icon field in the catalog. At build time the filler swaps the carrier with the SVG geometry for the chosen glyph, placed through the same native-shape pipeline (svgdeck) that procedural arts use.

Reference agent

Mon, 01 Jan 0001 00:00:00 +0000

Reference agent

⚠️ This page is a stub — full write-up coming soon.

A PydanticAI script that runs the loop.

The fill.json schema

Mon, 01 Jan 0001 00:00:00 +0000

The fill.json schema

⚠️ This page is a stub — full write-up coming soon.

The shape your agent produces to fill a template.

Builds and credits

Mon, 01 Jan 0001 00:00:00 +0000

Builds and credits

A build is the act of running the fill engine against a template: it reads a fill.json, resolves every field and variable, and produces a finished .pptx. Each successful build consumes one credit.

What costs a credit

One successful build = one credit. Credits are spent when a build moves to started (i.e., when you press Build deck in the web UI or call POST /builds/{id}/start via the API).
If the build fails, the credit is automatically refunded — you only pay for what you receive.

What is free

Uploading templates, running the catalog scan, annotating fields, editing the working fill, and creating draft builds are all free. You can iterate on a fill as many times as you like before pressing Build deck.

Diagrams

Mon, 01 Jan 0001 00:00:00 +0000

Diagrams

Place Mermaid diagrams into your slides in three modes: a static image, a step-by-step Morph animation, or fully editable native shapes.

Three modes

Mode	Sentinel	Output	Editable in PowerPoint
Static	`@diagram:<id>`	One PNG placed as a picture	No
Morph animation	`@diagram-morph:<id>`	One still slide per cumulative step, linked by a Morph transition	No (images)
Native shapes	`@diagram-native:<id>`	Autoshapes, connectors, and text transcoded from SVG	Yes

All three modes use the same domain/diagram feature and the same API/MCP surface; the mode is set when you create the diagram.

Code blocks

Mon, 01 Jan 0001 00:00:00 +0000

Code blocks

Place syntax-highlighted, animated code reveals into your slides. Syntax highlighting uses Pygments; animation uses PowerPoint Morph or native click builds.

Two animation engines

Engine	How it works	Slides produced
`morph` (default)	One slide per reveal step; identical code box, only highlight colours change; Morph cross-fades them	One per step
`native`	One slide; each step’s code box is revealed on click via a `<p:timing>` tree	One

Choose morph for smooth animated transitions between steps. Choose native for an in-slide, click-to-reveal build that keeps everything on one slide.

The build lifecycle

Mon, 01 Jan 0001 00:00:00 +0000

The build lifecycle

A build is the durable working object that carries both the fill you are composing and the resulting .pptx. It moves through a defined set of states and is never silently deleted.

States

State	What it means
`created`	The fill is editable. The fill builder (or an API/MCP agent) can read and write the working fill. No credit has been spent.
`started`	The build engine is running. One credit has been reserved. The fill is now read-only.
`built`	The build succeeded. The `.pptx` is available for download.
`failed`	The build engine returned an error. The credit was automatically refunded. The build can be reopened.
`archived`	The build’s output file has been cleaned up; the fill is still kept. An archived build can be reopened or copied.

Transitions

created ──start──► started ──success──► built ──archive──► archived
 │ └──failure──► failed ──►──────►─┘
 └── edit fill (PATCH /builds/{id}) — stays in created

Start: validates the fill, spends the credit, enqueues the job.
Reopen: moves a built, failed, or archived build back to created with its fill intact so you can edit and re-run it.
Copy: creates a new created build pre-seeded with the source build’s fill — useful for branching variations.
Archive: explicit archival any time from built or failed; also triggered automatically by the scheduler after 7 days. The fill is always kept; only the output file is removed.

The `/builds/{id}` view

The build view at /builds/{id} switches its layout based on the current state:

Procedural arts

Mon, 01 Jan 0001 00:00:00 +0000

Procedural arts

Procedural arts are Slidura’s replacement for SmartArt: structured data goes in, a native PowerPoint diagram comes out. No AI, no external render service — the geometry engine runs synchronously in pure Python.

How it works

The artdeck engine accepts a layout ID and a data payload, solves the geometry, and emits an SVG built from theme tokens (accent1, neutral, etc.) rather than literal colours. The svgdeck pipeline then converts that SVG into native PowerPoint shapes, picking up the template’s actual palette at build time. The round-trip budget is under 100 ms; failures surface as validation errors, not silently broken slides.

Components & shortcodes

Mon, 01 Jan 0001 00:00:00 +0000

Components & shortcodes

A reference page that exercises every layout element and shortcode the site ships with. Use it as a copy-paste cheat sheet when writing docs and blog posts.

Callouts

Note

This is the default note callout. It supports markdown and inline code.

An info callout with no title.

Tip

Why Slidura fills templates instead of designing decks

Mon, 01 Jun 2026 00:00:00 +0000

Most AI deck tools start from a blank canvas and generate something new. That’s great when you don’t have a brand — and a problem when you do. A brand-approved template is the result of a long sign-off process, and “close enough” is not good enough.

Slidura takes the opposite stance: it fills, it doesn’t design. You upload the .pptx your brand team already approved, and your own AI agent fills every field over MCP. The geometry, fonts, and master slides come out pixel-identical to what went in.

Slidura — Your PowerPoint template, filled by your AI agent on Slidura

Automate PowerPoint proposals

Automate PowerPoint proposals

Charts

Charts

How charts work

Connect Claude Desktop

Connect Claude Desktop

Prerequisites

Add the server

First deck in 10 minutes

First deck in 10 minutes

Before you start

Templates and versions

Templates and versions

The fill builder

The fill builder

Slide thumbnails and field locator

Fill a PowerPoint template via API

Fill a PowerPoint template via API

Tables

Tables

How tables work

The build assistant

The build assistant

How it works

Honest caveats

The underlying model

The catalog

The catalog

Tool reference

Tool reference

Recommended agent loop

Upload your template

Upload your template

Variables and typed values

Variables and typed values

Per-field defaults and choice lists

Annotate the catalog

Annotate the catalog

Annotations as the agent brief

Annotations as the agent brief

Images

Images

How images work

Let Claude fill your deck over MCP

Let Claude fill your deck over MCP

Published fill endpoints

Published fill endpoints

How it works

Signed download URLs

Signed download URLs

Build and download

Build and download

Design palette

Design palette

What the palette contains

Icons

Icons

How icons work

Reference agent

Reference agent

The fill.json schema

The fill.json schema

Builds and credits

Builds and credits

What costs a credit

What is free

Diagrams

Diagrams

Three modes

Code blocks

Code blocks

Two animation engines

The build lifecycle

The build lifecycle

States

Transitions

The /builds/{id} view

Procedural arts

The `/builds/{id}` view