# Beautiful.ai API and MCP server

> 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.

Presentation software that builds slides from Smart Slide layouts and AI prompts, with secure sharing, shared folders and viewer analytics.

## 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.

- **Category:** [Local services & SaaS](https://cotlet.dev/integrations/category/local-services-saas)
- **Endpoints:** 14 (5 read, 9 write)
- **Updated:** 2026-10-11

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.

## 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.

| 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](https://support.beautiful.ai/hc/en-us/articles/44246954338829-Beautiful-ai-MCP-Quick-Setup-FAQ), [Beautiful.ai API (help center)](https://support.beautiful.ai/hc/en-us/articles/43654071102605-Beautiful-ai-API), [Beautiful.ai API reference](https://docs.beautiful.ai/reference/createpresentation-1), [Beautiful.ai pricing](https://www.beautiful.ai/pricing), [Beautiful.ai: Keyboard Shortcuts (Find and Replace)](https://support.beautiful.ai/hc/en-us/articles/360000193552-Keyboard-Shortcuts), [Beautiful.ai: Analytics (Pro Tier)](https://support.beautiful.ai/hc/en-us/articles/360028082532-Analytics-Pro-Tier), [Beautiful.ai: Enabling the Slack Integration](https://support.beautiful.ai/hc/en-us/articles/360045650612-Enabling-the-Beautiful-ai-Slack-Integration), [Beautiful.ai: What Powers Beautiful.ai's Generative AI?](https://support.beautiful.ai/hc/en-us/articles/37567933064973-What-Powers-Beautiful-ai-s-Generative-AI), [Beautiful.ai: Shared Slides Properties](https://support.beautiful.ai/hc/en-us/articles/360047188952-Shared-Slides-Properties)

## For AI agents

```text
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.
```

## 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](https://cotlet.dev/integrations/beautiful-ai-api-mcp-server/replace-text-across-decks)**: "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." → `list_folders`, `list_presentations`, `get_slides`, `update_slide_text`, `duplicate_presentation`
- **[Write speaker notes for every slide](https://cotlet.dev/integrations/beautiful-ai-api-mcp-server/write-speaker-notes)**: "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." → `list_presentations`, `get_slides`, `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." → `list_presentations`, `duplicate_presentation`, `move_to_folder`
- **[See who viewed a shared deck](https://cotlet.dev/integrations/beautiful-ai-api-mcp-server/deck-viewer-analytics)** (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." → `list_presentations`, `get_presentation_analytics`
- **Export decks to PDF or PowerPoint**: "Export the board update as PDF and the sales deck as editable PowerPoint." → `list_presentations`, `export_presentation`

## 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 | 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. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 14 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 403 until the account has an API key with access to Beautiful.ai.

### list_presentations

Presentations in your library and shared folders, newest first, with folder, slide count and owner. Access: read. REST: `POST /api/v1/beautiful-ai/list_presentations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Search titles. |
| `folder` | string | no | Only presentations in this folder. |
| `limit` | integer | no | 1 to 100. Default: 25. |

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.

Example response:

```json
{
  "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"
    }
  ]
}
```

### list_folders

Your folders, including shared workspace folders, with the number of decks in each. Access: read. REST: `POST /api/v1/beautiful-ai/list_folders`.

No parameters.

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

Example response:

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

### get_slides

Every slide in order: layout, text, speaker notes and whether it is skipped. Access: read. REST: `POST /api/v1/beautiful-ai/get_slides`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `presentation_id` | string | yes | Presentation ID from list_presentations. |

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.

Example response:

```json
{
  "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
    }
  ]
}
```

### get_presentation_analytics

Viewer and slide analytics for a deck, as the app shows them. Access: read. REST: `POST /api/v1/beautiful-ai/get_presentation_analytics`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `presentation_id` | string | yes | Presentation ID from list_presentations. |

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.

Example response:

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

### list_collaborators

People with access to a presentation and whether they can edit or view. Access: read. REST: `POST /api/v1/beautiful-ai/list_collaborators`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `presentation_id` | string | yes | Presentation ID from list_presentations. |

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

Example response:

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

### update_slide_text

Replace text on one slide, keeping its Smart Slide layout. Access: write. REST: `POST /api/v1/beautiful-ai/update_slide_text`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `presentation_id` | string | yes | Presentation ID from list_presentations. |
| `slide_number` | integer | yes | Slide position in the deck, starting at 1. |
| `find` | string | yes | Exact text to replace. |
| `replace` | string | yes | New text. |

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.

Example response:

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

### set_speaker_notes

Write or replace the speaker notes of a slide. Access: write. REST: `POST /api/v1/beautiful-ai/set_speaker_notes`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `presentation_id` | string | yes | Presentation ID from list_presentations. |
| `slide_number` | integer | yes | Slide position in the deck, starting at 1. |
| `notes` | string | yes | Notes text. Empty string clears them. |

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.

Example response:

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

### skip_slide

Skip or unskip a slide when presenting. Access: write. REST: `POST /api/v1/beautiful-ai/skip_slide`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `presentation_id` | string | yes | Presentation ID from list_presentations. |
| `slide_number` | integer | yes | Slide position in the deck, starting at 1. |
| `skipped` | boolean | yes | true to skip, false to show it again. |

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.

Example response:

```json
{
  "presentation_id": "pres_2q7w1x5c",
  "slide_number": 7,
  "skipped": true
}
```

### duplicate_presentation

Copy any presentation in your library, as the Duplicate menu item does. Access: write. REST: `POST /api/v1/beautiful-ai/duplicate_presentation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `presentation_id` | string | yes | Presentation ID from list_presentations. |
| `title` | string | no | Title of the copy. Default: same as the original. |

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.

Example response:

```json
{
  "presentation_id": "pres_9k4m6b2v",
  "source_id": "pres_5d9a4r1t",
  "title": "Sales review, November",
  "slides": 16
}
```

### move_to_folder

Put a presentation in one of your folders. Access: write. REST: `POST /api/v1/beautiful-ai/move_to_folder`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `presentation_id` | string | yes | Presentation ID from list_presentations. |
| `folder` | string | yes | Folder name from list_folders. |

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.

Example response:

```json
{
  "presentation_id": "pres_9k4m6b2v",
  "folder": "Sales"
}
```

### export_presentation

Export the deck and return a download link. Access: write. REST: `POST /api/v1/beautiful-ai/export_presentation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `presentation_id` | string | yes | Presentation ID from list_presentations. |
| `format` | enum | yes | pdf or pptx. |

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.

Example response:

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

### invite_collaborator

Invite someone by email to edit or view a presentation. They get an email. Access: write, asks the user first. REST: `POST /api/v1/beautiful-ai/invite_collaborator`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `presentation_id` | string | yes | Presentation ID from list_presentations. |
| `email` | string | yes | Email of the person to invite. |
| `permission` | enum | yes | can_edit or can_view. |

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.

Example response:

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

### remove_collaborator

Revoke a collaborator's access to a presentation. Access: write, asks the user first. REST: `POST /api/v1/beautiful-ai/remove_collaborator`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `presentation_id` | string | yes | Presentation ID from list_presentations. |
| `email` | string | yes | Email from list_collaborators. |

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.

Example response:

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

### create_share_link

Share the presentation and return a link to it. Access: write, asks the user first. REST: `POST /api/v1/beautiful-ai/create_share_link`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `presentation_id` | string | yes | Presentation ID from list_presentations. |
| `name` | string | no | Link name, to tell links apart. |

Makes the deck viewable through a link and returns the link. Anyone who gets the link can open the deck. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "presentation_id": "pres_8f3k2m9q",
  "name": "Investors",
  "url": "https://www.beautiful.ai/player/pres_8f3k2m9q",
  "status": "shared"
}
```

## 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 to your agent.

1. **Create an account** Sign up and add Beautiful.ai in the console. Your API key is there too.

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. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   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"
```

4. **Ask your agent** 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.

```
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.
```

### Call Beautiful.ai from your scripts.

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

```
export COTLET_API_KEY="cotlet_..."
```

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

```
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"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

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

## Why use Cotlet for Beautiful.ai?

**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.

## 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.

|  | 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

## 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.

| 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. [See full pricing](https://cotlet.dev/pricing)

## 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](https://cotlet.dev/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](https://cotlet.dev/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](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## 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.