MCP — Standalone generation & file attachments
- MCP
generate_presentationaccepts an optionaltemplate_id. Omit it for the Standalone path — Chronicle drafts a storyline first, then slides. - New MCP tool
create_upload_targetfor issuing presigned S3 upload targets so the host can attach files (PDF, PPTX, images, text) to a generation. attachments[]accepted on MCPgenerate_presentationandsend_followup_message— pass entries fromcreate_upload_targetto ground the generation on a file’s contents.
Standalone generation, non-interactive mode, structured params
template_idis now optional onPOST /presentations/generate. When omitted, Chronicle uses the Standalone flow — storyline outline first, then slides.non_interactive: truebody flag: Chronicle never pauses to ask clarifying questions; auto-proceeds end-to-end. Built for automation integrations like n8n, Zapier, Make, and MCP.- Structured storyline params (Standalone path with
non_interactive: true):narrative_type,rewrite_style,section_count,language. GET /presentations/generate/:generationId/statusnow returnsphase: 'storyline' | 'slides'for Standalone generations so clients can show two-phase progress.
File attachments
POST /uploads/create-targetfor uploading reference files (PDF, PPTX, images, text) used to ground generationattachments[]accepted onPOST /presentations/generateandPOST /presentations/generate/:generationId/message
Initial public release of the Chronicle API.
- API key authentication for workspace admins
GET /templatesfor listing available templatesGET /presentations/:idfor fetching an existing presentationPOST /presentationsfor creating a deck from a templatePATCH /presentations/:idfor updating presentation metadata (title only)POST /presentations/generatefor generating a deck from a promptGET /presentations/generate/:generationId/statusfor polling a generation jobPOST /presentations/generate/:generationId/messagefor sending follow-up answers when generation requests clarification