Live

Beautiful.ai logo

Beautiful.ai API and MCP server

beautiful.ai

Beautiful.ai has an API that creates presentations from a structured outline and an official MCP connector that creates draft decks, lists presentations and exports PDF or PowerPoint (checked 11 Oct 2026). Cotlet is a hosted MCP server and REST API for Beautiful.ai with 14 endpoints (5 read, 9 write): your AI agent signs in as you and does the work.

Endpoints
14 5 read, 9 write
Updated
How Cotlet connects your agent to Beautiful.ai
  1. Your agent

    Claude Code, Codex, Cursor or a script

  2. Cotlet

    MCP server and REST API · 14 endpoints

    cotlet.dev/mcp/v1

  3. Beautiful.ai logo

    Beautiful.ai

    Signed in as you on beautiful.ai

You sign in once. We never store your password.

Official API

Does Beautiful.ai have an official API?

Beautiful.ai has an API that creates presentations from a structured outline and an official MCP connector that creates draft decks, lists presentations and exports PDF or PowerPoint (checked 11 Oct 2026). Neither edits existing slides, reads slide text, manages sharing or returns analytics.

What Beautiful.ai's own tools do compared with Cotlet
Task Beautiful.ai official Cotlet
Find presentations Yes The MCP connector lists presentations by title or keyword Yes
Export to PDF or PowerPoint Yes PDF and PPTX through the MCP connector Yes
Duplicate an existing deck Partly The connector copies templates only Yes
Read slide text and speaker notes No Yes
Edit slide text and speaker notes No Yes
Viewer analytics No Yes
Invite collaborators and create share links No Yes
Move decks between folders No Yes

Sources: Beautiful.ai MCP: Quick Setup + FAQ · Beautiful.ai API (help center) · Beautiful.ai API reference · Beautiful.ai pricing · Beautiful.ai: Keyboard Shortcuts (Find and Replace) · Beautiful.ai: Analytics (Pro Tier) · Beautiful.ai: Enabling the Slack Integration · Beautiful.ai: What Powers Beautiful.ai's Generative AI? · Beautiful.ai: Shared Slides Properties

Common use cases

What can an AI agent do in Beautiful.ai?

Cotlet is best for Beautiful.ai users who keep decks for sales, investors or clients and want their AI agent to edit, copy, share and export them without running or fixing a server.

  • Replace text across every deck

    We renamed Acme Insights to Acme Pulse. Find every deck in the Sales folder that still says Acme Insights, show me the matches, then replace them. Your agent calls list_folders, list_presentations, get_slides, update_slide_text and duplicate_presentation.

  • Write speaker notes for every slide

    Write speaker notes for each slide of the investor update: about 40 seconds per slide, plain spoken English, and keep the notes I already wrote. Your agent calls list_presentations, get_slides and set_speaker_notes.

  • Duplicate a deck for the next period Runs: Monthly

    Duplicate October's sales review as November and put it in the Sales folder. Your agent calls list_presentations, duplicate_presentation and move_to_folder.

  • See who viewed a shared deck Runs: Weekly

    Every Monday, tell me who opened the pitch decks in my Fundraising folder last week, how long they stayed and which slides they lingered on. Your agent calls list_presentations and get_presentation_analytics.

  • Export decks to PDF or PowerPoint

    Export the board update as PDF and the sales deck as editable PowerPoint. Your agent calls list_presentations and export_presentation.

Endpoints

What is the Beautiful.ai API?

Cotlet's Beautiful.ai API exposes 14 endpoints for your own Beautiful.ai account: list presentations, list folders, get slides, get presentation analytics, list collaborators, update slide text, set speaker notes, skip slide, duplicate presentation, move to folder, export presentation, invite collaborator, remove collaborator and create share link. The list_presentations endpoint returns presentations in your library and shared folders, newest first, with folder, slide count and owner. Each endpoint takes simple JSON inputs like presentation_id, slide_number or folder and works both as an MCP tool for agents and as a REST call for scripts.

All endpoints · 14 total

missing one? request an endpoint

  • POST

    list_presentations

    read

    Returns decks you can open, newest first. Filter by title keyword or folder. Pass presentation_id from each item to the other tools. Pages hold up to 100 decks.

    POST /api/v1/beautiful-ai/list_presentations

    Input

    Input: list_presentations
    Parameter Type Description
    query string Search titles.
    folder string Only presentations in this folder.
    limit integer 1 to 100. Default: 25.

    Example response

    {
      "presentations": [
        {
          "presentation_id": "pres_8f3k2m9q",
          "title": "Q3 QBR",
          "folder": "Sales",
          "slides": 18,
          "owner": "You",
          "updated_at": "2026-10-08T14:20:00Z"
        },
        {
          "presentation_id": "pres_2q7w1x5c",
          "title": "Investor update",
          "folder": null,
          "slides": 12,
          "owner": "You",
          "updated_at": "2026-10-05T09:02:00Z"
        }
      ]
    }
  • POST

    list_folders

    read

    Returns folders by name with deck counts. Use the name as the folder parameter of list_presentations and move_to_folder.

    POST /api/v1/beautiful-ai/list_folders

    Input

    No parameters.

    Example response

    {
      "folders": [
        {
          "name": "Sales",
          "presentations": 14,
          "shared": true
        },
        {
          "name": "Board",
          "presentations": 6,
          "shared": false
        }
      ]
    }
  • POST

    get_slides

    read

    Returns the slides of one deck in order, starting at 1. Text is listed in reading order per slide. Use it before update_slide_text so your agent sees what is on each slide.

    POST /api/v1/beautiful-ai/get_slides

    Input

    Input: get_slides
    Parameter Type Description
    presentation_id required string Presentation ID from list_presentations.

    Example response

    {
      "presentation_id": "pres_8f3k2m9q",
      "slides": [
        {
          "slide_number": 1,
          "layout": "Title",
          "text": [
            "Q3 QBR",
            "Sales team"
          ],
          "speaker_notes": "",
          "skipped": false
        },
        {
          "slide_number": 4,
          "layout": "Bullets",
          "text": [
            "FY25 targets",
            "Grow ARR 40%",
            "Launch in two new regions"
          ],
          "speaker_notes": "Mention the EU launch date.",
          "skipped": false
        }
      ]
    }
  • POST

    get_presentation_analytics

    read

    Returns the viewer and slide analytics Beautiful.ai shows for one deck. Availability depends on your plan; without it the call fails with an error that names the plan.

    POST /api/v1/beautiful-ai/get_presentation_analytics

    Input

    Input: get_presentation_analytics
    Parameter Type Description
    presentation_id required string Presentation ID from list_presentations.

    Example response

    {
      "presentation_id": "pres_8f3k2m9q",
      "views": 14,
      "unique_viewers": 9,
      "slides": [
        {
          "slide_number": 1,
          "views": 14
        },
        {
          "slide_number": 4,
          "views": 11
        }
      ]
    }
  • POST

    list_collaborators

    read

    Returns each person with access to the deck, with email and permission. Use the email in remove_collaborator.

    POST /api/v1/beautiful-ai/list_collaborators

    Input

    Input: list_collaborators
    Parameter Type Description
    presentation_id required string Presentation ID from list_presentations.

    Example response

    {
      "presentation_id": "pres_8f3k2m9q",
      "collaborators": [
        {
          "email": "anna@example.com",
          "permission": "can_edit"
        },
        {
          "email": "tom@example.com",
          "permission": "can_view"
        }
      ]
    }
  • POST

    update_slide_text

    write

    Replaces exact text on one slide and keeps its layout. Returns the number of matches replaced and the slide text after the change. It reaches no one and one call undoes it, so it runs without asking.

    POST /api/v1/beautiful-ai/update_slide_text

    Input

    Input: update_slide_text
    Parameter Type Description
    presentation_id required string Presentation ID from list_presentations.
    slide_number required integer Slide position in the deck, starting at 1.
    find required string Exact text to replace.
    replace required string New text.

    Example response

    {
      "presentation_id": "pres_8f3k2m9q",
      "slide_number": 4,
      "replaced": 1,
      "slide_text": [
        "FY26 targets",
        "Grow ARR 40%",
        "Launch in two new regions"
      ]
    }
  • POST

    set_speaker_notes

    write

    Replaces the speaker notes of one slide with the text you send. An empty string clears them. It reaches no one and one call undoes it, so it runs without asking.

    POST /api/v1/beautiful-ai/set_speaker_notes

    Input

    Input: set_speaker_notes
    Parameter Type Description
    presentation_id required string Presentation ID from list_presentations.
    slide_number required integer Slide position in the deck, starting at 1.
    notes required string Notes text. Empty string clears them.

    Example response

    {
      "presentation_id": "pres_2q7w1x5c",
      "slide_number": 2,
      "speaker_notes": "Open with the churn drop. Pause for questions before the pricing slide."
    }
  • POST

    skip_slide

    write

    Marks one slide as skipped, so it is left out when presenting, or shows it again. It reaches no one and one call undoes it, so it runs without asking.

    POST /api/v1/beautiful-ai/skip_slide

    Input

    Input: skip_slide
    Parameter Type Description
    presentation_id required string Presentation ID from list_presentations.
    slide_number required integer Slide position in the deck, starting at 1.
    skipped required boolean true to skip, false to show it again.

    Example response

    {
      "presentation_id": "pres_2q7w1x5c",
      "slide_number": 7,
      "skipped": true
    }
  • POST

    duplicate_presentation

    write

    Creates a copy of the deck in your library and returns its ID. The copy is private to you until you share it, so it runs without asking.

    POST /api/v1/beautiful-ai/duplicate_presentation

    Input

    Input: duplicate_presentation
    Parameter Type Description
    presentation_id required string Presentation ID from list_presentations.
    title string Title of the copy. Default: same as the original.

    Example response

    {
      "presentation_id": "pres_9k4m6b2v",
      "source_id": "pres_5d9a4r1t",
      "title": "Sales review, November",
      "slides": 16
    }
  • POST

    move_to_folder

    write

    Moves a deck into a folder from list_folders. People with access to that folder can then see it. One call moves it back, so it runs without asking.

    POST /api/v1/beautiful-ai/move_to_folder

    Input

    Input: move_to_folder
    Parameter Type Description
    presentation_id required string Presentation ID from list_presentations.
    folder required string Folder name from list_folders.

    Example response

    {
      "presentation_id": "pres_9k4m6b2v",
      "folder": "Sales"
    }
  • POST

    export_presentation

    write

    Exports one deck and returns a download link. Formats follow your Beautiful.ai plan. The export changes nothing in the deck and reaches no one, so it runs without asking.

    POST /api/v1/beautiful-ai/export_presentation

    Input

    Input: export_presentation
    Parameter Type Description
    presentation_id required string Presentation ID from list_presentations.
    format required enum pdf or pptx.

    Example response

    {
      "presentation_id": "pres_2q7w1x5c",
      "format": "pdf",
      "download_url": "https://www.beautiful.ai/export/exp_71c0aa.pdf"
    }
  • POST

    invite_collaborator

    write

    Gives one person access to the deck and emails them. Permission is can_edit or can_view. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/beautiful-ai/invite_collaborator

    Input

    Input: invite_collaborator
    Parameter Type Description
    presentation_id required string Presentation ID from list_presentations.
    email required string Email of the person to invite.
    permission required enum can_edit or can_view.

    Example response

    {
      "presentation_id": "pres_8f3k2m9q",
      "email": "anna@example.com",
      "permission": "can_edit",
      "status": "invited"
    }
  • POST

    remove_collaborator

    write

    Removes one person from the deck. They lose access at once. By default you confirm each call; you can switch that off for this tool.

    POST /api/v1/beautiful-ai/remove_collaborator

    Input

    Input: remove_collaborator
    Parameter Type Description
    presentation_id required string Presentation ID from list_presentations.
    email required string Email from list_collaborators.

    Example response

    {
      "presentation_id": "pres_8f3k2m9q",
      "email": "tom@example.com",
      "status": "removed"
    }

Setup

How do I connect Beautiful.ai to Claude Code, Codex or Cursor?

Connecting Beautiful.ai takes three steps: request access, sign in to Beautiful.ai once, then add one MCP server or call the REST API with the same key.

Connect Beautiful.ai over MCP

  1. 1

    Create an account

    Sign up and add Beautiful.ai in the console. Your API key is there too.

  2. 2

    Sign in to Beautiful.ai once

    Open the connect page from the console and sign in to Beautiful.ai the way you always do. We keep the session, never your password, and you can revoke it anytime.

  3. 3

    Add Cotlet to your agent

    Claude Code
    claude mcp add --transport http cotlet \
      https://cotlet.dev/mcp/v1 \
      --header "Authorization: Bearer $COTLET_API_KEY"
    Cursor
    {
      "mcpServers": {
        "cotlet": {
          "url": "https://cotlet.dev/mcp/v1",
          "headers": {
            "Authorization": "Bearer ${COTLET_API_KEY}"
          }
        }
      }
    }
    Codex
    # ~/.codex/config.toml
    [mcp_servers.cotlet]
    url = "https://cotlet.dev/mcp/v1"
    bearer_token_env_var = "COTLET_API_KEY"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

  4. 4

    Ask your agent

    Prompt

    We renamed Acme Insights to Acme Pulse. Find every deck in the Sales folder that still says Acme Insights, show me the matches, then replace them.

    Ask in plain words. Your agent finds the Beautiful.ai tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

Call Beautiful.ai over REST

  1. 1

    Export your API key

    Shell

    export COTLET_API_KEY="cotlet_..."

    Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

  2. 2

    Call a tool

    curl

    curl https://cotlet.dev/api/v1/beautiful-ai/update_slide_text \
      -H "Authorization: Bearer $COTLET_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{"presentation_id":"pres_8f3k2m9q","slide_number":4,"find":"FY25 targets","replace":"FY26 targets"}'

    Every tool is a POST endpoint at /api/v1/beautiful-ai/{tool}. Send its parameters as JSON, exactly as listed in the endpoints above.

  3. 3

    Read the result

    Example response · update_slide_text

    {
      "presentation_id": "pres_8f3k2m9q",
      "slide_number": 4,
      "replaced": 1,
      "slide_text": [
        "FY26 targets",
        "Grow ARR 40%",
        "Launch in two new regions"
      ]
    }

    You get plain JSON back, ready for your script. A failed call costs nothing.

Why Cotlet

Why use Cotlet for Beautiful.ai? Hosted, safe and kept working.

  • Built for agents

    • One MCP server for every app you connect.
    • The same tools as a REST API for scripts and cron jobs.
    • Works with Claude Code, Codex and Cursor.
  • Your login stays yours

    • You sign in to Beautiful.ai yourself. We keep only the session, encrypted with AES-256.
    • The model never sees a login.
    • No stored passwords, no CAPTCHA solving, no MFA bypass.
  • You stay in control

    • Pick read only, or read and write.
    • Anything that reaches other people waits for your OK, unless you switch it off per tool.
    • Revoke access in one click.
  • Kept working for you

    • We test every integration daily.
    • When Beautiful.ai changes, the tool pauses until we fix it.
    • Failed calls cost nothing.

Alternatives

Is there a Beautiful.ai MCP server on GitHub?

Beautiful.ai's own MCP connector creates draft decks and exports them, but its FAQ says it does not edit existing slides. We found no open-source or hosted server that does. The realistic options are the official connector, or opening each deck by hand.

Cotlet compared with a Official connector
Official connector Cotlet
Setup Add the MCP URL and sign in with OAuth Request access, sign in to Beautiful.ai once in your browser, add one MCP server or API key
New decks From an outline, a prompt or a template Use the official connector; Cotlet works on decks you already have
Editing existing slides Not supported Slide text, speaker notes and skipped slides
Sharing and analytics Not supported Share links, collaborators and viewer analytics
Your session OAuth token held by your AI client Encrypted in an EU vault, limited to the actions you allow, revoked in one click
When the app changes Beautiful.ai maintains it Our team tests it daily and fixes it for you; failed calls are free
Price No extra charge listed Free 7-day trial with 5,000 credits, then credits per call

Which one fits you

Pick Cotlet if

  • you are not a developer, or you do not want to maintain a server
  • you need it to keep working when Beautiful.ai changes, without checking it yourself
  • your agent or a script should run it on a schedule, also while your computer is off

Pick an open-source server if

  • you are comfortable installing, updating and fixing it yourself
  • you want the session to stay on your own computer
  • you only need it now and then, from one MCP client

For AI agents

Cotlet for Beautiful.ai in plain text The facts on this page in one block: status, endpoints, access, pricing, contact.

Endpoint health

verified 2h ago

  • list_presentations passing
  • list_folders passing
  • get_slides passing
  • get_presentation_analytics passing
  • list_collaborators passing

+ 9 more endpoints

14/14 passing latest check self-healing

beautiful-ai.txt

Beautiful.ai has an API that creates presentations from a structured outline and an official MCP connector that creates draft decks, lists presentations and exports PDF or PowerPoint (checked 11 Oct 2026). Neither edits existing slides, reads slide text, manages sharing or returns analytics.
Cotlet provides a hosted MCP server and REST API for Beautiful.ai: 14 tools (5 read, 9 write).
Access       Request access at https://cotlet.dev/app/signup?app=beautiful-ai; we email the API key.

MCP server   https://cotlet.dev/mcp/v1
REST base    https://cotlet.dev/api/v1/beautiful-ai
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one.
Tools        list_presentations, list_folders, get_slides, get_presentation_analytics, list_collaborators, update_slide_text, set_speaker_notes, skip_slide, duplicate_presentation, move_to_folder, export_presentation, invite_collaborator, remove_collaborator, create_share_link
Confirm      invite_collaborator, remove_collaborator, create_share_link (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/beautiful-ai-api-mcp-server.md

How access works:
1. The user requests access at https://cotlet.dev/app/signup?app=beautiful-ai (Beautiful.ai is pre-selected). Each request is reviewed and the API key is sent by email.
2. The user signs in to Beautiful.ai once in a browser. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Beautiful.ai server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Session: the user signs in to Beautiful.ai in a browser; Cotlet keeps only the session, AES-256 encrypted, revocable in the dashboard at any time.
Terms: the user stays responsible for following Beautiful.ai's terms; Cotlet is not affiliated with Beautiful.ai.
Full page as Markdown

Automations

Can Beautiful.ai automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Beautiful.ai connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to duplicate a deck for the next period, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

Where to run Beautiful.ai automations through Cotlet, and how to schedule them
Where How to connect How to schedule
Your AI agent Add https://cotlet.dev/mcp/v1 with your API key. A scheduled agent run, for example a Claude Code routine.
n8n MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node to https://cotlet.dev/api/v1/beautiful-ai/{tool}. Schedule Trigger node.
Make HTTP module: POST https://cotlet.dev/api/v1/beautiful-ai/{tool} with an Authorization: Bearer header and a JSON body. Scenario schedule.
Zapier Webhooks by Zapier: POST https://cotlet.dev/api/v1/beautiful-ai/{tool} with the same header and body. Schedule by Zapier trigger.
Your own script POST https://cotlet.dev/api/v1/beautiful-ai/{tool} with your API key. cron or GitHub Actions.

Pricing & limits

How much does the Beautiful.ai API cost?

Free 7-day trial with 5,000 credits, no card needed. After that, the Beautiful.ai API comes with the Cotlet plan, from $29 a month for 3,000 credits, with no limit on apps. Each month's credits stay valid for 3 months, so unused credits add up.

Cotlet plan sizes: price, monthly credits and price per credit
Size Price Credits / month Per credit
Solo $29/mo 3,000 about $0.0097
Pro $99/mo 12,000 about $0.0083
Agency $299/mo 40,000 $0.0075

Each successful call uses credits for the work it takes; failed calls and timeouts cost nothing. A hard spend cap is on by default. Authenticate with the Authorization: Bearer header.

About Cotlet

How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Beautiful.ai account.

Company details
The legal name, address and registration numbers of the company behind Cotlet are in the Terms of service. Terms
Your session
You sign in to Beautiful.ai yourself, in your browser. We keep only the session, never your password: encrypted with AES-256 in an EU vault, isolated to your account and used only when your agent calls a Beautiful.ai tool you allowed. When it expires, your agent gives you a link to sign in again. Security
Revoking access
Disconnect Beautiful.ai in your dashboard: the session is deleted and access ends at once. Actions that reach other people wait for your OK unless you switch that off per tool.
What we never do
Store passwords, solve CAPTCHAs or bypass MFA.
Beautiful.ai's terms
You use your own Beautiful.ai account and stay responsible for following Beautiful.ai's terms. Cotlet is independent and not affiliated with Beautiful.ai. Terms
Contact
Questions about the company, security or an app: contact@cotlet.dev
About Cotlet

Frequently asked questions

How do I get access?

Request access and pick Beautiful.ai. Cotlet reviews each request and emails you your API key.

Do I need to be technical?

No. You sign in to Beautiful.ai once in your browser and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

Is a hosted server safe? My Beautiful.ai session would leave my computer.

Cotlet keeps your Beautiful.ai session encrypted with AES-256 in an EU vault, isolated to your account and used only for the tools you allow: read only, or read and write. The AI model never sees it, and you revoke it in one click. A local server keeps the same session in a file on your computer, readable by any program you run, and needs a fresh sign-in whenever it expires.

Does it work on a Pro plan?

Yes. Cotlet works in your own Beautiful.ai account on any plan. Features your plan lacks, such as viewer analytics or an export format, fail with a clear error (pricing page, checked 11 Oct 2026).

Can it create a deck from a prompt?

No. Creating new decks is what Beautiful.ai's official MCP connector does, so use it for new drafts and Cotlet for decks you already have.

Can my agent post or send messages in Beautiful.ai without asking me?

No. Every call to invite_collaborator, remove_collaborator or create_share_link waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. update_slide_text, set_speaker_notes, skip_slide, duplicate_presentation, move_to_folder, export_presentation runs without asking, because it sends nothing to anyone and one call undoes it.

Can I use the Beautiful.ai API in n8n?

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call https://cotlet.dev/api/v1/beautiful-ai/{tool} from the HTTP Request node.

Give your agent access to Beautiful.ai.

Request access and pick it. We review each request and email you your API key. Free 7-day trial with 5,000 credits, no card needed.