Developer documentation

Choose the publishing interface that fits your workflow

Use the browser for a quick test, the CLI for local artifacts, MCP for configured Agents, the Skill for runtime guidance, or the HTTP API for your own integration.

Last tested: July 28, 2026Reference hub

Publishing interfaces

First publishQuickstartPublish without an account, verify the result, claim the deck, and update the same URL.Local artifactSlidesfly CLIInstall from the official website, publish local HTML, claim decks, update versions, and manage sharing controls.Agent toolModel Context ProtocolConnect a hosted Streamable HTTP server or run the stdio implementation from source.Agent guidanceSlidesfly SkillInstall the canonical task contract for Codex, Cursor, and Claude Code.HTTP integrationOpenAPIUse the same BFF routes as the CLI and MCP with explicit auth and idempotency.Reader integrationEmbed and oEmbedPut an eligible Slidesfly reader inside an external document or publishing surface.Trust modelSecurity architectureUnderstand origin separation, iframe sandboxing, private object access, and abuse controls.

Where to start

First time: follow the five-minute quickstart.
One local HTML file: follow the single-file guide.
Framework output: use the compatibility matrix to choose single-file or zip publishing.
Configured Agent: use MCP when available, otherwise use the CLI.
Reusable Agent behavior: install the Skill and keep the artifact-generation step separate.
Custom product integration: use OpenAPI and an API key.

Machine-readable contracts