Capabilities

The server exposes a deliberately small tool surface. Tool names are stable API identifiers; your client may describe them with friendlier labels.

Tool	Scope	Effect
get_slidelang_guide	none	Returns authoring guidance for valid presentation source.
list_presentations	presentations:read	Lists the presentations available to the connected account.
get_presentation	presentations:read	Returns one deck, its editable source, metadata, and current checksum.
create_presentation	presentations:write	Validates, stores, renders, and publishes a new presentation.
update_presentation	presentations:write	Replaces a deck’s source when the supplied checksum is current.
delete_presentation	presentations:write	Moves a presentation to trash.

What MCP does—and does not do

MCP standardizes discovery, tool calls, results, and authorization between the AI client and SlideWeave. It does not write the story or choose the design by itself. The AI client authors ZiraDocs presentation source; SlideWeave validates it, persists it, renders it, and serves the result.

Presentation source

The API calls the editable field slidelang for compatibility with the existing tool contract. The source follows the open ZiraDocs presentation format.

Destructive operations

Deletion is recoverable: the tool moves the presentation to trash. Clients should still state the exact deck and ask for confirmation before calling it.