Beautiful.ai MCP Server

Create, edit, duplicate and export Beautiful.ai decks from your agent.

ホスト型 MCP サーバー

npx add-mcp 'https://cotlet.dev/mcp/v1/beautiful-ai'

Claude Code、Codex、Cursor などにインストールできます

ドキュメント

Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up

Beautiful.ai API and MCP server: Let your AI agent edit the decks you already have.

Beautiful.ai has an official API and an MCP connector, listed in Claude's directory since 30 Jul 2026. Both create decks from a prompt, outline or template, list decks and folders and export PDF or PowerPoint, but neither reads or edits slide text (checked 24 Oct 2026). Cotlet runs 14 Beautiful.ai tools hosted for the decks you already have, over MCP for agents and REST for scripts.

Read Beautiful.ai presentations, slide content and collaborators through MCP or REST. Connect your agent or prepare presentation reports from a script.

MCP setup REST API guide

What can you automate in Beautiful.ai?

  • Replace wording across many decks
  • Write speaker notes per slide
  • Report who viewed each deck
  • Copy a deck for next month
  • Share a deck with a client
  • Clean up who can edit

Does Beautiful.ai have an MCP server or an API?

  • The official API has 10 endpoints. It covers 3 of our 14 tools in full: listing decks, listing folders and export. Copying works for templates only.
  • No speaker notes, skipped slides, viewer analytics, collaborators or share settings in either. The connector page says to refine the deck in Beautiful.ai.
  • Zapier and n8n have no Beautiful.ai app. We found no Beautiful.ai MCP server on GitHub besides the official docs.
What you needOfficial connectorOfficial APICotlet
New deck from a prompt or outlineYesYes, in your codeNo, use the connector
List decks and export PDF or PPTXYesYes, in your codeYes
Read and change slide text and notesNoNoYes, layout kept
Viewer and slide analyticsNoNoYes, on your plan
Share links and collaboratorsNoNoYes, after your OK
The route Beautiful.ai providesYes, officialYes, officialUses the web app

Checked 24 Oct 2026. Sources: Beautiful.ai MCP: Quick Setup + FAQ, Beautiful.ai API reference, Beautiful.ai: Claude connector, Beautiful.ai integrations

How does Cotlet connect to Beautiful.ai?

  1. Sign in to Beautiful.ai. Use your own account in its Cotlet Cloud Browser.
  2. Choose MCP or REST. Connect your agent or create a Cotlet API key.
  3. Run your workflow. Ask your agent or send an HTTP request.

We never keep your Beautiful.ai password, and no invite or share link goes out until you approve it.

Connect Beautiful.ai to your agent or workflow

Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.

  1. Enable Beautiful.ai for agents. Sign up, sign in to Beautiful.ai in its Cloud Browser, then press Enable for agents.
  2. Add the Cotlet address. Add https://cotlet.dev/mcp/v1 as an MCP server or connector in your agent.
  3. Approve the connection. Chat apps ask you to sign in to Cotlet. Editors, n8n and scripts use an API key from the console.

The address https://cotlet.dev/mcp/v1 is shared: Beautiful.ai sits there next to your other apps. Keep Beautiful.ai's own connector next to it for new drafts; the two do not clash. After enabling Beautiful.ai, refresh the connector so its tools appear.

Claude:

Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect

Claude Code:
claude mcp add --transport http cotlet-beautiful-ai \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"

ChatGPT:

Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth

Cursor:

// ~/.cursor/mcp.json
{
  "mcpServers": {
    "cotlet-beautiful-ai": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
    }
  }
}

Codex:

# ~/.codex/config.toml
[mcp_servers.cotlet-beautiful-ai]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"

n8n:

MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: beautiful_ai_read

Make, Zapier:

Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: beautiful_ai_write

How to use the Beautiful.ai REST API

Create your Cotlet API key

Sign in to Beautiful.ai in its Cotlet Cloud Browser and enable the app for agents. Use your own Beautiful.ai login; your plan determines analytics access.

Create a Cotlet API key with access to Beautiful.ai and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.

Make your first Beautiful.ai API request

cURL: list_presentations:

curl "https://cotlet.dev/api/v1/beautiful-ai/presentations?limit=5" \
  -H "Authorization: Bearer $COTLET_API_KEY"

Read presentations within the selected limit

A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.

Illustrative response excerpt:

{
  "status": "success",
  "app": "beautiful-ai",
  "tool": "list_presentations",
  "result": {
    "presentations": [
      {
        "presentation_id": "pres_8f3k2m9q",
        "title": "Q3 QBR",
        "folder": "Sales",
        "slides": 18,
        "owner": "You",
        "updated_at": "2026-10-08T14:20:00Z"
      }
    ]
  }
}

Read result.presentations. The list defaults to 25 presentations and accepts at most 100, with title and folder filters but no cursor or offset.

Narrow the selection for large libraries rather than treating a limited list as a complete export. Use presentation IDs to read slide text, speaker notes and skipped-slide flags.

Analytics depend on your Beautiful.ai plan. Collaborator reads show sharing permissions without inviting or removing anyone.

Beautiful.ai workflows for agents and automations

ToolConnect throughExample workflow
n8nHTTP RequestRead folders, presentations and slides into a wording review draft without editing the deck.
MakeHTTP > Make a requestRead plan-supported presentation analytics into a viewer report in your chosen sheet.
Python or Node.jsREST APIRead deck collaborators into a sharing-permission review without inviting or removing anyone.

Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.

Cotlet reads Beautiful.ai; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.

Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.

The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.

Beautiful.ai API endpoints and MCP tools

Decks and folders

Shared folders need the Team plan since Beautiful.ai merged folder types on 10 Sep 2026; Pro keeps private folders.

  • List presentations (list_presentations, read): Presentations in your library and shared folders, newest first, with folder, slide count and owner.
  • List folders (list_folders, read): Your folders, including shared workspace folders, with the number of decks in each.
  • Duplicate presentation (duplicate_presentation, write): Copy any presentation in your library, as the Duplicate menu item does.
  • Move to folder (move_to_folder, write): Put a presentation in one of your folders.
  • Export presentation (export_presentation, write): Export the deck and return a download link.

Slide text, notes and skipped slides

Slides are counted from 1. A text change keeps the Smart Slide layout, so Beautiful.ai still fits the words to the slide.

  • Get slides (get_slides, read): Every slide in order: layout, text, speaker notes and whether it is skipped.
  • Update slide text (update_slide_text, write): Replace text on one slide, keeping its Smart Slide layout.
  • Set speaker notes (set_speaker_notes, write): Write or replace the speaker notes of a slide.
  • Skip slide (skip_slide, write): Skip or unskip a slide when presenting.

Viewers, collaborators and share links

Viewer analytics come with Pro, slide-level analytics with Team. Invites and links reach people outside the workspace, so they wait for you.

  • Get presentation analytics (get_presentation_analytics, read): Viewer and slide analytics for a deck, as the app shows them.
  • List collaborators (list_collaborators, read): People with access to a presentation and whether they can edit or view.
  • Invite collaborator (invite_collaborator, write, asks first): Invite someone by email to edit or view a presentation. They get an email.
  • Remove collaborator (remove_collaborator, write, asks first): Revoke a collaborator's access to a presentation.
  • Create share link (create_share_link, write, asks first): Share the presentation and return a link to it.

Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/beautiful-ai-api-mcp-server#tools

Who can see my Beautiful.ai session, and how do I revoke it?

  • What we store. Your signed-in Beautiful.ai profile, AES-256-GCM encrypted, kept in Finland. No password.
  • What your agent gets. The 14 Beautiful.ai tools, never the session cookie.
  • What the session sees. Your decks, shared folders, Team Slides and viewer emails.
  • What no tool touches. Billing, seats, Brand Kits, your password and deleting decks.
  • Google, Microsoft or SSO. Any sign-in prompt is yours to answer. We never answer it.
  • How to cut access. Disable for agents or reset the Cloud Browser in the Cotlet console.

Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). We have no SOC 2 report or third-party pentest yet; Beautiful.ai lists SOC 2 Type II for its own Enterprise plan.

Is it against Beautiful.ai's terms? Account safety

Customer may not ... use any meta tags, "hidden text", robots, spiders, crawlers, or other tools, whether manual or automated, to collect, scrape, index, mine, republish, redistribute, transmit, sell, license or download the Beautiful.ai Services or any part thereof ... without Beautiful.ai's prior written permission or authorization.

Beautiful.ai Terms of Service, section 2.4 (i), revised 22 Aug 2025

Section 6.2 (c) lets Beautiful.ai suspend an account "with or without notice" when it believes this rule was broken. Cotlet reads slides and exports decks in your own workspace through the web app, which Beautiful.ai could still count as an automated tool. We found no public case of a Beautiful.ai account closed for automation (checked 24 Oct 2026).

How we keep your workspace looking like you:

  • Your own Beautiful.ai login, signed in by you
  • One Cloud Browser with a steady IP and cookies
  • Invites and share links wait for your OK
  • No tool deletes a deck, slide or folder
  • If Beautiful.ai objects, the Beautiful.ai tools pause for every user within 24 h

Listing decks, exporting and new drafts are what Beautiful.ai's own API and connector do, the route it backs. Use those for that work and Cotlet for the edits they lack.

What happens when Beautiful.ai changes?

  • 12 h between tests of the Beautiful.ai reads and slide edits
  • 24 h between tests of invites and share links
  • $0 for a call to a Beautiful.ai tool paused for repair

Beautiful.ai posted 10 product updates between 31 Jul and 29 Sep 2026: themes became Brand Kits on 11 Sep, and folders merged into one type on 10 Sep. When a change like that moves a field, we fix the tool and your prompts keep working. status.cotlet.dev watches the site, console and API every 3 minutes.

Approvals, undo and mistakes

  1. Lists the folder. Every deck in Sales, with its slide count.
  2. Reads each deck. Slide text in order, so it finds every match.
  3. Shows the matches. Deck, slide and old wording, before any change.
  4. Replaces and reports. Slides changed, count per deck, anything skipped.
ActionUndo
Change slide text or speaker notesOne call puts the old text back
Skip a slideOne call shows it again
Copy a deckDelete the copy in Beautiful.ai
Move a deck to a folderMove it back; folder members may have seen it
Invite a collaboratorRemove them; the invite email is already sent
Create a share linkTurn sharing off; anyone who opened it saw the deck

3 of 14 tools ask first: invite_collaborator, remove_collaborator and create_share_link, the ones that change who sees a deck. Slide edits, notes, copies and exports reach nobody, so they run at once. For a scheduled job you can switch the wait off per tool.

Text on a Team Slide changes only for an Owner or Librarian, through Edit Shared Slide. Other roles get an error and nothing moves.

MCP call:

{
  "name": "update_slide_text",
  "arguments": {
    "presentation_id": "pres_8f3k2m9q",
    "slide_number": 4,
    "find": "FY25 targets",
    "replace": "FY26 targets"
  }
}

REST:

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

Tool output:

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

Scripts and cron jobs call the same tools over REST at /api/v1/beautiful-ai, with one key and one price. Analytics on a plan without them fails with an error naming the plan, and a failed call costs nothing. The tools table lists the REST path of each tool.

How much does the Beautiful.ai MCP server cost?

About $15 a month for one person keeping about 30 team decks current, 2,540 credits. Beautiful.ai still bills your plan as before.

JobCallsCredits
Rename a product across one folder27 × 1270
Speaker notes for a 12-slide deck13 × 2260
Viewer check on 3 decks, weekly4 × 4160
Copy last month's report and update it9 × 2180
Export, share and invite a client3 × 4120
Collaborator cleanup5 × 150
Cloud Browser, 30 days1,500
Total2,540
  • Free 7-day trial, no card
  • 10 credits per successful call, MCP or REST
  • 50 credits a day for the Cloud Browser
  • Works on Pro and Team; analytics follow your plan

The month is our example: one rename pass over 10 decks, notes for 2 decks, a weekly viewer check, 2 monthly copies and 4 client shares. Beautiful.ai gives no typical account size, only "more than 100,000 customers". Dollars at the $29 pack rate.

Beautiful.ai MCP server on GitHub, Zapier or hosted: which to use

OptionWhat it doesWhere it stops
Beautiful.ai connectorOfficial MCP with OAuth, about 10 tools: new decks from a prompt, outline or template, search, folders, themes, PDF and PPTX export.No change to an existing slide, no notes, analytics or sharing.
Beautiful.ai APIThe same 10 actions over REST with an API key.Same limits, and code you write and host.
beautifulai/beautifulai-docsThe official API docs on GitHub, 0 stars, last push 28 Apr 2026.Docs only. No other Beautiful.ai MCP server or CLI on GitHub.
Zapier, n8nNo Beautiful.ai app or node.Nothing to connect.
Gamma, Canva and other deck tools with MCPTheir own decks from an agent.You move your decks off Beautiful.ai.

For a new draft, Beautiful.ai's connector comes with your Beautiful.ai account and is the route Beautiful.ai backs. For the decks already in your library (a rename, notes, a viewer count, a client share), nothing but Cotlet reaches them today. Both can sit in the same agent.

Also listed on: Odel, mcpbeat

Who runs Cotlet

Cotlet is run by Take Group sp. z o.o., a software company registered in Poland, EU (VAT PL6342984273), in business since 2019 and founded by Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the Beautiful.ai tools go to contact@cotlet.dev.

Beautiful.ai API and MCP: questions

Can I use the Beautiful.ai API without an AI agent?

Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.

How do I get access?

Make a free account at https://cotlet.dev, open Beautiful.ai under Integrations in the console and sign in to Beautiful.ai in its Cloud Browser. The trial starts when you sign up, no card asked.

How do I connect Beautiful.ai to ChatGPT or Claude?

Sign up at cotlet.dev, log in to Beautiful.ai once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your Beautiful.ai account through Cotlet, in their phone apps too.

What can ChatGPT do in Beautiful.ai?

With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in Beautiful.ai: replace text across every deck; write speaker notes for every slide; duplicate a deck for the next period. You ask in plain words, and anything that reaches other people waits for your OK first.

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 I use Beautiful.ai's connector and Cotlet together?

Yes. Add both to your agent: the official connector for new drafts, Cotlet for edits, notes, analytics and sharing on decks you already have. The agent picks the tool by the job.

Does a text change break my slide layout?

No. update_slide_text swaps exact text on one slide and keeps its Smart Slide layout, so Beautiful.ai fits the new words the same way it fits typed ones.

Does Beautiful.ai have webhooks?

We found none in its API reference (checked 24 Oct 2026). Run your agent on a schedule instead, for example a weekly list_presentations and get_presentation_analytics pass.

Is the MCP server different from the REST API?

Only the door differs. Both carry the same 14 tools, inputs and answers, with one API key and one price. Agents use MCP; scripts and HTTP steps use REST.

Is Cotlet affiliated with Beautiful.ai?

No. Cotlet is independent and not affiliated with Beautiful Slides, Inc.


Give your AI agents your signed-in browser.

Product: Integrations · How it works · Pricing · Security

Resources: Blog · API docs · Help center · Changelog · GitHub

Solutions: For developers · For automation agencies

Company: About · AI info: company facts · Contact

Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors

Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.