Choose an integration
What the API can automate
- Upload source documents and reusable assets.
- Generate a presentation from a prompt, Markdown outline, or uploaded files.
- Select language, tone, verbosity, slide count, template, and export format.
- Enable optional web research.
- Edit presentations or individual slides.
- Create a new deck from an existing presentation.
- List available themes and templates.
- Export PPTX or PDF output.
/api/v1/* routes except /api/v1/auth/* use the same admin username and password as the web UI through HTTP Basic authentication.
What MCP adds
The MCP server exposes supported presentation actions as tools to a compatible AI client. The client can discover the tools, create a presentation, and return the result to the user without requiring the user to construct REST requests. MCP is served from:/api/v1/auth/login and send it as a bearer token. MCP is disabled in the Electron desktop app; use the Docker or web deployment.
Deployment guidance
- Use HTTPS for a remote instance.
- Store REST credentials and MCP tokens in a secret manager.
- Restrict network access to approved applications and clients.
- Use asynchronous generation for long-running or high-latency jobs.
- Treat webhook payloads as untrusted input and verify requests according to your application design.
- Persist
/app_dataso generated presentations and uploads survive replacement containers. - Review generated content before it is published automatically.
Generate with the REST API
Make an authenticated request, inspect the result, and open the generated deck.
Connect an MCP client
Configure authenticated local, remote, or multiple Presenton instances.