[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Privy API and MCP server

> Privy has a public API on paid plans and a read-only MCP server (checked 23 Oct 2026). The API reads contacts, campaigns, flows, displays, segments, coupons, orders and reports, and writes contacts, order events and custom events. Neither the API nor the MCP can create or change a campaign, flow, display or segment.

Email, SMS and popup marketing for online stores: signup popups called displays, email and text campaigns, automated flows, segments and coupons in one dashboard.

## What is the Privy API?

Cotlet's Privy API exposes 13 endpoints for your own Privy account: list campaigns, list displays, list flows, list segments, list contacts, create a segment, duplicate a campaign, create an email campaign draft, send or schedule an email campaign, unschedule a campaign, pause a display, launch a paused display and tag contacts. The list_campaigns endpoint returns list email and SMS campaigns with status, subject, send date and results. Each endpoint takes simple JSON inputs like page, per_page or status and works both as an operation of the privy_read or privy_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Marketing & SEO](https://cotlet.dev/integrations/category/marketing-seo.md)
- **Endpoints:** 13 (5 read, 8 write)
- **Updated:** 2026-10-20

Privy has a public API on paid plans and a read-only MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for Privy with 13 endpoints (5 read, 8 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Privy have an official API?

Privy has a public API on paid plans and a read-only MCP server (checked 23 Oct 2026). The API reads contacts, campaigns, flows, displays, segments, coupons, orders and reports, and writes contacts, order events and custom events. Neither the API nor the MCP can create or change a campaign, flow, display or segment.

| Task | Privy official | Cotlet |
|---|---|---|
| Read campaigns, flows, displays and segments | Yes: Public API on paid plans and the read-only MCP | Yes |
| Read performance reports | Yes: API reports on paid plans; the MCP reads campaign metrics | Yes |
| List and search contacts | Yes | Yes |
| Tag contacts | Partly: The API updates a contact by id; the MCP cannot change anything | Yes |
| Create a segment | No | Yes |
| Duplicate or create an email campaign | No | Yes |
| Send, schedule or unschedule a campaign | No | Yes |
| Pause or launch a display | No | Yes |

Sources: [Privy Help: Privy MCP](https://help.privy.com/docs/learn/mcp), [Privy Help: API Overview](https://help.privy.com/docs/api-reference/overview), [Privy Help: Connect Privy to Zapier](https://help.privy.com/docs/learn/integrations/zapier)

## Quick reference

```text
Privy has a public API on paid plans and a read-only MCP server (checked 23 Oct 2026). The API reads contacts, campaigns, flows, displays, segments, coupons, orders and reports, and writes contacts, order events and custom events. Neither the API nor the MCP can create or change a campaign, flow, display or segment.
Cotlet provides a hosted MCP server and REST API for Privy: 13 tools (5 read, 8 write).
Access       Sign up at https://cotlet.dev/app/signup?app=privy, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    privy_read, privy_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/privy, each operation at its own route, e.g. POST /api/v1/privy/campaigns/{campaign_id}/email-campaigns
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_campaigns, list_displays, list_flows, list_segments, list_contacts, create_segment, duplicate_campaign, create_email_campaign, send_email_campaign, unschedule_campaign, pause_display, launch_display, tag_contacts
Confirm      send_email_campaign, launch_display, tag_contacts (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/privy-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=privy, requests Privy in the Cotlet console and creates an API key there.
2. The user signs in to Privy once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Privy for agents. 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 Privy 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.
Sign-in: the user signs in to Privy in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Privy only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Privy login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Privy's terms; Cotlet is not affiliated with Privy.
```

## What can an AI agent do in Privy?

Cotlet is best for ecommerce marketers who run Privy campaigns and popups and want their AI agent to build segments, schedule sends and pause weak popups without running or fixing a server.

- **[Resend a campaign to people who did not open it](https://cotlet.dev/integrations/privy-api-mcp-server/resend-campaign-to-non-openers.md)**: "Find the October sale email, make a segment of contacts who did not open it, copy the email with the subject "In case you missed it: our October sale", and schedule it for Thursday at 10:00." → `list_campaigns`, `create_segment`, `duplicate_campaign`, `send_email_campaign`
- **[Schedule a weekly email campaign](https://cotlet.dev/integrations/privy-api-mcp-server/schedule-weekly-email-campaign.md)** (runs: weekly): "Every Monday, create a campaign from my Saved Template "Weekly picks" with the subject "Five picks for your weekend", send it to Engaged Contacts and schedule it for Tuesday at 9:00 in recipient time zones." → `list_segments`, `list_campaigns`, `create_email_campaign`, `send_email_campaign`, `unschedule_campaign`
- **[Pause popups that do not convert](https://cotlet.dev/integrations/privy-api-mcp-server/pause-low-converting-popups.md)**: "List my live popups. Pause every popup with at least 3000 views and a signup rate under 1%, and tell me which ones you paused." → `list_displays`, `pause_display`
- **Weekly campaign, flow and popup report** (runs: weekly): "Every Monday, summarize last week's sent campaigns (delivered, opened, clicked, unsubscribed), my active flows and my live popups with views and signups." → `list_campaigns`, `list_flows`, `list_displays`
- **Tag unengaged contacts for a sunset email**: "List members of Unengaged Contacts and tag them sunset, so my sunset flow picks them up." → `list_segments`, `list_contacts`, `tag_contacts`

## Can Privy automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Privy 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 schedule a weekly email campaign, 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 with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/privy/segments. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/privy/segments with your API key. | cron or GitHub Actions. |

## Tools

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

### list_campaigns

List email and SMS campaigns with status, subject, send date and results. Access: read. REST: `GET /api/v1/privy/campaigns`. MCP: `privy_read → list_campaigns`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | draft, scheduled, preparing, awaiting_winner, sending, sent, partially_sent, unsent or canceled |
| `channel` | string | no | email or sms |
| `page` | integer | no | Page number, starting at 1 |
| `per_page` | integer | no | Items per page |

Returns the rows of the Campaigns table: title, channel, status, subject and send date, plus Delivered, Opened, Clicked and Unsubscribed. Opened is a count and the other two rates are percentages of delivered contacts. Privy tracks an open with an invisible image, so a contact whose client blocks images is not counted as opened.

Example response:

```json
{
  "data": [
    {
      "id": "cmp_41c8",
      "title": "October sale announcement",
      "channel": "email",
      "status": "sent",
      "subject": "Our October sale starts now",
      "send_date": "2026-10-20T10:00:00-04:00",
      "delivered": 4820,
      "opened": 1930,
      "clicked_percent": 2.4,
      "unsubscribed_percent": 0.3
    },
    {
      "id": "cmp_3a07",
      "title": "Fall lookbook",
      "channel": "email",
      "status": "sent",
      "subject": "The fall lookbook is here",
      "send_date": "2026-10-06T10:00:00-04:00",
      "delivered": 4710,
      "opened": 2105,
      "clicked_percent": 3.1,
      "unsubscribed_percent": 0.2
    },
    {
      "id": "cmp_5b92",
      "title": "October sale resend",
      "channel": "email",
      "status": "draft",
      "subject": "In case you missed it: our October sale",
      "send_date": null,
      "delivered": 0,
      "opened": 0,
      "clicked_percent": 0,
      "unsubscribed_percent": 0
    }
  ],
  "pagination": {
    "page": 1,
    "per_page": 25,
    "total_count": 3,
    "total_pages": 1
  }
}
```

### list_displays

List popups, flyouts, bars and other displays with status, views and signups. Access: read. REST: `GET /api/v1/privy/displays`. MCP: `privy_read → list_displays`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | draft, scheduled, live, paused, ended or archived. Archived displays appear only when you ask for them |
| `page` | integer | no | Page number, starting at 1 |
| `per_page` | integer | no | Items per page |

Returns each display with its type, status, Views, Signups and Signup Rate, the numbers Privy shows on its card. Views counts a display appearing on a visitor's screen, not a pageview, and a signup is a submitted form. Orders and revenue are not returned.

Example response:

```json
{
  "data": [
    {
      "id": "dsp_c3e0",
      "title": "Welcome popup",
      "display_type": "popup",
      "status": "live",
      "views": 7400,
      "signups": 212,
      "signup_rate_percent": 2.9
    },
    {
      "id": "dsp_19a4",
      "title": "Exit offer",
      "display_type": "popup",
      "status": "live",
      "views": 6200,
      "signups": 31,
      "signup_rate_percent": 0.5
    },
    {
      "id": "dsp_88d2",
      "title": "Spring flyout",
      "display_type": "flyout",
      "status": "live",
      "views": 3900,
      "signups": 27,
      "signup_rate_percent": 0.7
    }
  ],
  "pagination": {
    "page": 1,
    "per_page": 25,
    "total_count": 3,
    "total_pages": 1
  }
}
```

### list_flows

List automated flows with status, trigger and the steps they contain. Access: read. REST: `GET /api/v1/privy/flows`. MCP: `privy_read → list_flows`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | draft, active or inactive |
| `page` | integer | no | Page number, starting at 1 |
| `per_page` | integer | no | Items per page |

Returns each flow with its status, the trigger that starts it and its steps in order (email, sms, delay, split, tag, update_contact). It reads the flow and changes nothing; flows are built and published in the Privy flow builder.

Example response:

```json
{
  "data": [
    {
      "id": "flw_2e71",
      "title": "Welcome email",
      "status": "active",
      "trigger": "Customer subscribed to marketing",
      "steps": [
        "email",
        "delay",
        "email"
      ]
    },
    {
      "id": "flw_90bb",
      "title": "Abandoned cart",
      "status": "inactive",
      "trigger": "Cart abandoned",
      "steps": [
        "delay",
        "email",
        "email"
      ]
    }
  ],
  "pagination": {
    "page": 1,
    "per_page": 25,
    "total_count": 2,
    "total_pages": 1
  }
}
```

### list_segments

List custom and smart segments with the number of mailable and textable contacts. Access: read. REST: `GET /api/v1/privy/segments`. MCP: `privy_read → list_segments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `page` | integer | no | Page number, starting at 1 |
| `per_page` | integer | no | Items per page |

Returns the four Smart Segments (Engaged Contacts, Unengaged Contacts, Potential Customers, Current Customers) and your custom segments, each with prebuilt, mailable_count and textable_count. Segments are dynamic, so the counts are the current ones, and the segment ids go into create_email_campaign and duplicate_campaign.

Example response:

```json
{
  "data": [
    {
      "id": "seg_2b11",
      "name": "Engaged Contacts",
      "prebuilt": true,
      "mailable_count": 6310,
      "textable_count": 1240
    },
    {
      "id": "seg_c9e4",
      "name": "Unengaged Contacts",
      "prebuilt": true,
      "mailable_count": 2150,
      "textable_count": 380
    },
    {
      "id": "seg_7d20",
      "name": "Did not open October sale",
      "prebuilt": false,
      "mailable_count": 2890,
      "textable_count": 0
    }
  ],
  "pagination": {
    "page": 1,
    "per_page": 25,
    "total_count": 3,
    "total_pages": 1
  }
}
```

### list_contacts

Search contacts, or list the members of a segment, with consent and tags. Access: read. REST: `GET /api/v1/privy/contacts`. MCP: `privy_read → list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Name, email address or phone number |
| `tag` | string | no | Only contacts with this Privy tag |
| `segment_id` | string | no | Only members of this segment (id from list_segments) |
| `page` | integer | no | Page number, starting at 1 |
| `per_page` | integer | no | Items per page |

Returns contacts with name, email, phone, email_consent, sms_consent and tags. Only a contact whose email_consent is subscribed can receive marketing email, and only sms_consent subscribed can receive marketing texts. Contact ids start with cus_ and go into tag_contacts.

Example response:

```json
{
  "data": [
    {
      "id": "cus_91f2",
      "first_name": "Dana",
      "last_name": "Reed",
      "email": "dana@example.com",
      "email_consent": "subscribed",
      "sms_consent": "never_subscribed",
      "tags": [
        "spring-promo"
      ]
    },
    {
      "id": "cus_a4c7",
      "first_name": "Leo",
      "last_name": "Park",
      "email": "leo@example.com",
      "email_consent": "subscribed",
      "sms_consent": "subscribed",
      "tags": []
    }
  ],
  "pagination": {
    "page": 1,
    "per_page": 25,
    "total_count": 2,
    "total_pages": 1
  }
}
```

### create_segment

Create a custom segment from conditions such as Did not open a campaign. Access: write. REST: `POST /api/v1/privy/segments`. MCP: `privy_write → create_segment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Segment name. Only you see it, contacts do not |
| `match` | string | no | all (Match all, the default) or any (Match any) |
| `conditions` | array | yes | Objects with category, rule and value as in Privy's Choose Category picker, for example Email Engagement, Did not open, and a campaign name |

Creates the segment and returns its id and current mailable_count. Privy cannot edit the conditions of a segment after creation, so a wrong condition means a new segment; a custom segment can be deleted in Contacts > Segments. It reaches no one, so it does not wait for your OK. Campaigns in a "Did not open" condition are listed by their name, not their subject line.

Example response:

```json
{
  "segment_id": "seg_7d20",
  "name": "Did not open October sale",
  "match": "all",
  "conditions": [
    {
      "category": "Email Engagement",
      "rule": "Did not open",
      "value": "October sale announcement"
    }
  ],
  "mailable_count": 2890
}
```

### duplicate_campaign

Copy a campaign into a new draft with its own name, subject and recipients. Access: write. REST: `POST /api/v1/privy/campaigns/{campaign_id}/duplicate`. MCP: `privy_write → duplicate_campaign`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `campaign_id` | string | yes | Campaign to copy (id from list_campaigns) |
| `name` | string | no | Name of the copy |
| `subject_line` | string | no | New subject line |
| `segment_ids` | array | no | Segments to send to, replacing the original audience |
| `exclude_segment_ids` | array | no | Segments to leave out |

Does the same as Duplicate in the Campaigns menu, then sets the To field, the subject and the name. The copy keeps the original design and stays a draft, so nothing is sent. It reaches no one and a draft can be deleted from the Campaigns menu, so it does not wait for your OK. The body is not edited; change it in the Privy editor.

Example response:

```json
{
  "campaign_id": "cmp_5b92",
  "title": "October sale resend",
  "status": "draft",
  "copied_from": "cmp_41c8",
  "subject_line": "In case you missed it: our October sale",
  "audience": {
    "included_segments": [
      "Did not open October sale"
    ],
    "excluded_segments": []
  }
}
```

### create_email_campaign

Create an email campaign draft from a template, with subject and recipients. Access: write. REST: `POST /api/v1/privy/email-campaigns`. MCP: `privy_write → create_email_campaign`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Campaign name |
| `template` | string | yes | Name of a Privy Template or Saved Template as shown in the template picker |
| `subject_line` | string | yes | Subject line |
| `preview_text` | string | no | Preview text |
| `segment_ids` | array | yes | Segments to send to (ids from list_segments) |
| `exclude_segment_ids` | array | no | Segments to leave out |

Does what Campaigns > Send email does up to the Review step. The design is the template as saved, so a Saved Template you update each week carries the content. From name, From Email and Reply To use your Settings defaults. The draft sends nothing, reaches no one and can be deleted from the Campaigns menu, so it does not wait for your OK.

Example response:

```json
{
  "campaign_id": "cmp_6c15",
  "title": "Weekly picks, 27 Oct",
  "status": "draft",
  "template": "Weekly picks",
  "subject_line": "Five picks for your weekend",
  "audience": {
    "included_segments": [
      "Engaged Contacts"
    ],
    "excluded_segments": []
  }
}
```

### send_email_campaign

Send a draft email campaign now or schedule it for a day and time. Access: write, asks the user first. REST: `POST /api/v1/privy/campaigns/{campaign_id}/email-campaigns`. MCP: `privy_write → send_email_campaign`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `campaign_id` | string | yes | Draft campaign (id from list_campaigns) |
| `send_at` | string | no | ISO 8601 time in your business time zone. Leave out to send now |
| `recipient_timezone` | boolean | no | Send in recipient's timezone |

Returns the campaign status, scheduled when send_at is set. With recipient_timezone on, delivery spreads over about 24 hours, and contacts with no known time zone get it at the chosen time in your business time zone. The audience is fixed when you approve, and Privy may send a scheduled email a couple of minutes early. Sent emails cannot be recalled. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "campaign_id": "cmp_5b92",
  "status": "scheduled",
  "send_at": "2026-10-22T10:00:00-04:00",
  "send_in_recipient_timezone": false
}
```

### unschedule_campaign

Move a scheduled campaign back to draft. Access: write. REST: `POST /api/v1/privy/campaigns/{campaign_id}/unschedule`. MCP: `privy_write → unschedule_campaign`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `campaign_id` | string | yes | Scheduled campaign (id from list_campaigns) |

Does what Unschedule Campaign does in the Campaigns menu. Privy allows it only before preparation starts; after that, a time zone send needs Cancel send in Privy, which this tool does not do. It reaches no one and can be undone with send_email_campaign, so it does not wait for your OK.

Example response:

```json
{
  "campaign_id": "cmp_5b92",
  "status": "draft"
}
```

### pause_display

Pause a live popup or other display so visitors stop seeing it. Access: write. REST: `POST /api/v1/privy/displays/{display_id}/pause`. MCP: `privy_write → pause_display`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `display_id` | string | yes | Display to pause (id from list_displays) |

Does what Pause does in the Displays menu: the display stops appearing on your site and is not deleted. It reaches no visitor and launch_display undoes it, so it does not wait for your OK.

Example response:

```json
{
  "display_id": "dsp_19a4",
  "title": "Exit offer",
  "status": "paused"
}
```

### launch_display

Turn a paused display back on so visitors see it again. Access: write, asks the user first. REST: `POST /api/v1/privy/displays/{display_id}/launch`. MCP: `privy_write → launch_display`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `display_id` | string | yes | Paused display (id from list_displays) |

Does what Launch does in the Displays menu on a paused display. The display then shows to visitors on your site under the triggers and targeting it already has. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "display_id": "dsp_19a4",
  "title": "Exit offer",
  "status": "live"
}
```

### tag_contacts

Add a Privy tag to contacts, or remove it from them. Access: write, asks the user first. REST: `POST /api/v1/privy/contacts/tag`. MCP: `privy_write → tag_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `tag` | string | yes | Tag name. Privy saves bulk tag names in lowercase |
| `action` | string | yes | add or remove |
| `contact_ids` | array | yes | Contact ids from list_contacts |

Does what Bulk Actions > Tag Contacts does. A tag can start a flow set to Contact Tagged or Contact Untagged, and that flow can email or text those contacts, which is why this call waits for you. Tag-triggered flows fire only when the tag changes. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "tag": "sunset",
  "action": "add",
  "tagged": 2,
  "contacts": [
    "cus_91f2",
    "cus_a4c7"
  ]
}
```

## How do I connect Privy to Claude Code, Codex or Cursor?

Connecting Privy takes three steps: sign up, sign in to Privy once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Privy to your agent.

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

2. **Sign in to Privy in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Privy there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

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

```
Find the October sale email, make a segment of contacts who did not open it, copy the email with the subject "In case you missed it: our October sale", and schedule it for Thursday at 10:00.
```

### Call Privy 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 an endpoint under /api/v1/privy with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/privy/campaigns/cmp_5b92/email-campaigns \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"send_at":"2026-10-22T10:00:00-04:00"}'
```

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

```
{
  "campaign_id": "cmp_5b92",
  "status": "scheduled",
  "send_at": "2026-10-22T10:00:00-04:00",
  "send_in_recipient_timezone": false
}
```

## Why use Cotlet for Privy?

**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 Privy yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Privy changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Privy to Cotlet?

Yes. You sign in to Privy yourself, in your own Cloud Browser, and we never save your password. Your agents only get Privy once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Privy integration?**

No, Cotlet is independent of Privy. Privy's own API is too limited for this work. Cotlet works through your own Privy account, the way you use Privy in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Privy in your console: your agents lose access at once and you stay signed in. Signing out of Privy in the browser works too, and Reset browser deletes the whole profile.

## Is there a Privy MCP server on GitHub?

Privy's own Zapier app is available by invitation from Privy support and has four contact actions: create, find, find or create, and update. It has no step for campaigns, segments or popups. Cotlet works in your Privy dashboard, so it covers those jobs, and it sits next to Zapier: Zapier for contact sync, Cotlet for the marketing work.

|  | Zapier | Cotlet |
|---|---|---|
| Setup | Ask Privy support for access, then connect with OAuth, one connection per business | Sign up, sign in to Privy once, add one MCP server or API key |
| What it covers | Create, find and update contacts | Segments, email campaigns, displays and tags, plus reads of campaigns, flows and contacts |
| When Privy changes | Privy maintains its app | Our team tests it daily and fixes it for you; failed calls are free |
| Your Privy session | An OAuth connection kept by Zapier | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| Upkeep | Zaps you build and watch yourself | Nothing to host or update |
| Where it runs | Inside Zapier, triggered by other apps | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Zapier's own pricing; Privy's API needs a paid Privy plan | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### 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 Privy 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 your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Privy API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Privy API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

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

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Privy yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Privy only after you enable it. When Privy signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Privy, sign out of Privy in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. 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.
- **Privy's terms:** You use your own Privy account and stay responsible for following Privy's terms. Cotlet is independent and not affiliated with Privy. [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?**

Sign up free, open Privy in the console and press Request access. Then you create your API key and connect Privy there.

**Do I need to be technical?**

No. You sign in to Privy once in your Cloud Browser, a normal Chrome you open from the console, 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 it safe to connect Privy to Cotlet?**

Yes. You sign in to Privy yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Privy once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Privy sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Privy cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Privy's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Privy sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Privy login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Privy offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need a paid Privy plan?**

Privy's own API and MCP server need one, and only paid businesses show up in the MCP business picker. Cotlet works in your dashboard instead, so you need whatever your plan allows there. SMS campaigns, for example, need a plan that includes SMS and an approved toll-free number.

**Why are some people who opened my email in the Did not open segment?**

Privy tracks an open with an invisible image. If the recipient's client blocks images, Privy counts no open, so the segment holds some people who read the email. A resend to them is harmless but redundant.

**What can it not do in Privy?**

The tools do not edit an email or popup design, build or publish flows, send SMS campaigns, import contacts from CSV or delete contacts. You change a design in the Privy editor, and the agent sends the result. Reads cover campaigns, flows, displays, segments and contacts.

**Can my agent post or send messages in Privy without asking me?**

No. Every call to send_email_campaign, launch_display or tag_contacts waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_segment, duplicate_campaign, create_email_campaign, unschedule_campaign and pause_display run without asking, because they send nothing to anyone and one call undoes it.

**Can I use the Privy API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/privy from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

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](https://cotlet.dev/about.md)

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.