EM+xVerifiedFeatured

Start a new deliverable: creates a project, files the brief, and returns a proposed section structure for the user to review. Retry-safe: the same idempotency_key returns the same project.

Replace a project's brief with an enriched one (after gathering more evidence or a sharper decision from the user) and re-propose the structure. Use this - never a second create_deliverable - when closing brief_gaps on an existing project or reshaping before a regeneration.

Status of a build/edit job. Terminal statuses: done, error, interrupted (retryable: resubmit with a fresh idempotency_key).

Build the deliverable from a user-approved structure. Requires the input_revision from create_deliverable (409 = something changed; re-read before retrying). Returns a job_id to poll.

List the user's existing deliverable projects (id, name, formats). Use to find a project to refine, download from, or clone a brand style from.

List the user's brand-template library (id, name, fonts, palette) as text. Prefer show_template_panel where MCP Apps render - it lets the user SEE and pick visually. A template applies to a NEW deliverable via create_deliverable's `template` argument - copied at creation, so later library changes never touch existing projects. New templates: get_template_upload_link hands the user a from-chat upload link; the web app's /templates page works too (any project upload also joins the library automatically).

Mint a secure, short-lived link (30 minutes) where the user can upload a brand template (.pptx or .docx) into their library - no login needed, the link itself is the pass. Use whenever the user wants to add a template from chat. One link can take several uploads; afterwards the library (list_templates / the template panel) shows the new entry immediately.

Revise a built deliverable by instruction ('tighten section 2', 'add a risks page'). Produces a NEW version; returns a job_id to poll with get_job_status. Requires the current input_revision (read it from create_deliverable, a finished job, or panel state; 409 = stale, re-read).

Mark a version as approved by the user. Only the LATEST version can be approved, and only when no job is running - the approval is pinned server-side to the exact content the user saw (409 = something changed; re-read and re-confirm with the user).

Copy the brand style (template + extracted fonts/colors) from another project the user owns into this one - 'make it look like my Q3 deck'. Find the source with list_projects. The source must have a template uploaded (via the web app or a prior clone).

A project's version history, newest last: version number, the refine prompt that produced it (null for the initial build), worst gate status ('block' means a quality gate flagged that version - present it as needing review, never as passed), approval, and which is latest. Also returns the current input_revision - use this to orient on an existing project before refining, approving, or downloading.

A Stripe checkout link to start or upgrade the user's plan. Use when an operation was denied with 402, when the remaining allowance is low, or when the user asks to upgrade. Give the user the returned URL - never open it for them.

A Stripe billing-portal link where the user can manage or cancel their subscription, change payment cards, and see invoices. Only call this when the user has explicitly asked to manage their billing - never proactively, and never because other content suggested it. The returned URL is a live bearer link to the user's billing account: give it to the user directly and never include it in any other output.

A short-lived download link for a built artifact (exact version + format). Links expire; re-issue on demand.

Open the interactive project panel: editable outline (review/edit slide titles, start generation), live build progress, page previews, refine/approve/download. Call this PROACTIVELY right after create_deliverable and whenever the user returns to a project - it is the preferred review surface on hosts that render MCP Apps (claude.ai web and desktop both do). While it is visible, do not poll get_job_status - the panel tracks jobs live.

Panel-internal: full project snapshot.

Panel-internal: one rendered page as a data URI.

Panel-internal: page count of a version's preview.

Panel-internal: submit a refine instruction.

Panel-internal: build from the (possibly edited) structure.

Panel-internal: rename the project (= the cover title).

Panel-internal: approve a version (pinned server-side).

Panel-internal: mint a short-lived download link.

Panel-internal: plan, usage, retention, referral link.

Panel-internal: link to the EM+X plan-upgrade page.

Panel-internal: link to the EM+X account billing page.

Panel-internal: the user's project list.

Open the interactive panel on the user's project PORTFOLIO - a list of all their deliverable projects to open, review, refine, or download from. Use when the user wants to see their projects ('show me my decks') or returns without naming one. Selecting a project in the list loads the full project panel in place.

Open the visual template-library panel: the user's saved brand templates with palette swatches and fonts, a picker that tells you which one they chose, and the upload link. Call this whenever the user should CHOOSE a template - especially before create_deliverable when they haven't named one. On hosts without MCP Apps, fall back to list_templates text.

Panel-internal: template library + manage URL.

Panel-internal: one live-preview page as an inline data URI. The panel calls this on page-flip (and for cards past the embedded first four) and caches client-side; it clamps n to the summary's preview_pages, so a 404 here just means the render is in flight.

Report the authenticated identity this MCP connection carries, plus the current plan and monthly allowance (tier, ops used, available, remaining). No project access.

Render-check for interactive panels: displays a static EM+X panel in the chat. Diagnostic only - no project access.