Docs

Agent workflow

Set up an agent from OpenSlideX

Generate the MCP setup from your local Workspace, then let an agent work only within the presentation scope you chose.

Terminal

$ open-slidex mcp --workspace ~/Presentations --print-config codex

The six MCP tools

MCP is the local file and validation boundary, not another hosted presentation service. Read the latest revision first; every write action must carry it.

ToolKey inputsPurpose
open_slidex_workspacelist / select + presentationIdLists decks or selects one deck before deck-specific calls.
open_slidex_readintent, sourceFormat, slideIndex, componentPath, resourcePath…Reads canonical TSX, one local component, MDX, HTML, skills, or knowledge resources.
open_slidex_source_importaction, filePath, expectedRevisionInspects a root-confined PPTX; import-media writes extracted WebP assets.
open_slidex_mediaaction, expectedRevision, filePath, query, providerAssetIdIngests staged sources, searches/imports trusted media, or imports a local image.
open_slidex_reviewscope, slideIndexRuns structural validation and rendered visual QA without changing the deck.
open_slidex_editexpectedRevision, target, source, slideIndex…Replaces a complete TSX deck, one Slide, or controlled HTML, then runs QA.

Set it up from Workspace Settings

OpenSlideX Workspace Settings generates a user-level MCP configuration for Codex, Claude Code, or Claude Desktop. Choose the client, add the generated configuration, then restart that client so it can load the local OpenSlideX server.

A Workspace scope lets the agent select one of the decks you exposed; a fixed project scope limits it to one project. OpenSlideX creates the configuration but does not probe, launch, or control the client.

A small, reviewable tool surface

The local MCP server provides six workflow tools: workspace selection, progressive reading, PPTX source import, media intake, read-only review, and revision-safe editing. Read again before an edit and use the returned revision so changes stay attributable to the local deck.