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

# SimpleTexting API and MCP server

> Yes, SimpleTexting has a REST API on any paid plan, but only on approval, and it has no official MCP server (checked 23 Oct 2026). You send support your use case and a written acknowledgment of the terms, and a token follows.

SMS marketing and texting platform for businesses in the US and Canada: campaigns, a two-way Inbox, contact lists, keywords and autoresponders.

## What is the SimpleTexting API?

Cotlet's SimpleTexting API exposes 12 endpoints for your own SimpleTexting account: list conversations, get conversation, list contacts, list contact lists, list segments, list campaigns, list keywords, send message, schedule message, schedule campaign, add contact to list and assign conversation. The list_conversations endpoint returns conversations in the Inbox with the last message of each. Each endpoint takes simple JSON inputs like list, limit or cursor and works both as an operation of the simpletexting_read or simpletexting_write MCP tool for agents and as a REST call for scripts.

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

Yes, SimpleTexting has a REST API on any paid plan, but only on approval, and it has no official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for SimpleTexting with 12 endpoints (7 read, 5 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does SimpleTexting have an official API?

Yes, SimpleTexting has a REST API on any paid plan, but only on approval, and it has no official MCP server (checked 23 Oct 2026). You send support your use case and a written acknowledgment of the terms, and a token follows.

| Task | SimpleTexting official | Cotlet |
|---|---|---|
| Read Inbox conversations | No: The documentation lists no Inbox endpoint; Zapier has a New Incoming Message trigger | Yes |
| Send a text to one contact | Yes | Yes |
| Schedule a text to one contact | Partly: The API page lists Send, not a send time | Yes |
| Schedule a campaign | Partly: The API page lists Send, Get and Get All for campaigns, not a send time | Yes |
| Add a contact to a list | Yes | Yes |
| Read contacts and lists | Yes | Yes |
| Read keywords | Partly: The older v1 documentation has keyword calls | Yes |
| Assign a conversation to a team member | No | Yes |

Sources: [SimpleTexting: SMS API and how to get a token](https://simpletexting.com/api/), [SimpleTexting: API documentation](https://simpletexting.com/api/docs/), [SimpleTexting on Zapier MCP](https://zapier.com/mcp/simpletexting), [SimpleTexting: Scheduled texts](https://simpletexting.com/features/scheduled-texts/)

## Quick reference

```text
Yes, SimpleTexting has a REST API on any paid plan, but only on approval, and it has no official MCP server (checked 23 Oct 2026). You send support your use case and a written acknowledgment of the terms, and a token follows.
Cotlet provides a hosted MCP server and REST API for SimpleTexting: 12 tools (7 read, 5 write).
Access       Sign up at https://cotlet.dev/app/signup?app=simpletexting, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    simpletexting_read, simpletexting_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/simpletexting, each operation at its own route, e.g. POST /api/v1/simpletexting/campaign/schedule
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_conversations, get_conversation, list_contacts, list_lists, list_segments, list_campaigns, list_keywords, send_message, schedule_message, schedule_campaign, add_contact_to_list, assign_conversation
Confirm      send_message, schedule_message, schedule_campaign, add_contact_to_list (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/simpletexting-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=simpletexting, requests SimpleTexting in the Cotlet console and creates an API key there.
2. The user signs in to SimpleTexting once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables SimpleTexting 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 SimpleTexting server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source SimpleTexting MCP server instead.

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 SimpleTexting 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 SimpleTexting 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 SimpleTexting 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 SimpleTexting's terms; Cotlet is not affiliated with SimpleTexting.
```

## What can an AI agent do in SimpleTexting?

Cotlet is best for small businesses and agencies who text customers through SimpleTexting and want their agent to handle the Inbox, scheduled sends and lists without running or fixing a server.

- **[Schedule a text campaign](https://cotlet.dev/integrations/simpletexting-api-mcp-server/schedule-text-campaigns.md)** (runs: weekly): "Schedule a text campaign to the Overdue for a cleaning segment of the Patients list for Monday at 9:00, with this wording, and tell me how many people it reaches." → `list_lists`, `list_segments`, `list_campaigns`, `schedule_campaign`
- **[Answer texts waiting in the Inbox](https://cotlet.dev/integrations/simpletexting-api-mcp-server/reply-to-inbox-texts.md)** (runs: daily): "Go through my SimpleTexting Inbox. Reply to simple scheduling questions from my hours and open slots, and list everything else for me." → `list_conversations`, `get_conversation`, `send_message`, `assign_conversation`
- **[Add customers to a text list](https://cotlet.dev/integrations/simpletexting-api-mcp-server/add-customers-to-a-text-list.md)** (runs: weekly): "Add everyone from this sign-up sheet who ticked the text reminders box to the Class reminders list, and tell me who was new." → `list_lists`, `list_contacts`, `add_contact_to_list`
- **Schedule a reminder text to one contact**: "Text Marcus Lee on Monday at 8:00 that his class is at 5 pm Tuesday." → `list_contacts`, `schedule_message`
- **Route new texts to the right team member** (runs: daily): "Assign each unassigned conversation in the Inbox to Priya Nair if it mentions billing, and leave the rest." → `list_conversations`, `get_conversation`, `assign_conversation`

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

Yes. Cotlet does not replace your automation platform: it gives it a SimpleTexting 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 text 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/simpletexting/lists. | 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/simpletexting/lists with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 12 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 SimpleTexting.

### list_conversations

Conversations in the Inbox with the last message of each. Access: read. REST: `GET /api/v1/simpletexting/conversations`. MCP: `simpletexting_read → list_conversations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Contact name or phone number. |
| `assigned_to` | string | no | Name of a team member. Leave out for all conversations. |
| `limit` | integer | no | Page size. |
| `cursor` | string | no | next_cursor from the previous call. |

Reads the Inbox as it shows it: one row per contact with the last message, its direction (incoming or outgoing) and who the conversation is assigned to. Replies to campaigns are included, because SimpleTexting delivers them to the Inbox. Filter by a search on the contact or by assignee. Page with next_cursor.

Example response:

```json
{
  "conversations": [
    {
      "conversation_id": "c_8f21a6",
      "contact": {
        "name": "Dana Whitfield",
        "phone": "+12125550147"
      },
      "last_message": {
        "direction": "incoming",
        "text": "Can I move my cleaning to Friday?",
        "at": "2026-10-23T09:12:00-04:00"
      },
      "assigned_to": null
    },
    {
      "conversation_id": "c_5b09d3",
      "contact": {
        "name": "Marcus Lee",
        "phone": "+12125550163"
      },
      "last_message": {
        "direction": "outgoing",
        "text": "See you at 3 pm.",
        "at": "2026-10-22T16:40:00-04:00"
      },
      "assigned_to": "Priya Nair"
    }
  ],
  "next_cursor": null
}
```

### get_conversation

All messages and private notes of one Inbox conversation. Access: read. REST: `GET /api/v1/simpletexting/conversations/{conversation_id}`. MCP: `simpletexting_read → get_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | string | yes | conversation_id from list_conversations. |

Reads one conversation by id: the contact, every text in it with its direction and time, attachments by name, and the private notes team members left. Reading does not change the conversation. Use it before send_message so a reply answers the whole thread, not only the last text.

Example response:

```json
{
  "conversation_id": "c_8f21a6",
  "contact": {
    "name": "Dana Whitfield",
    "phone": "+12125550147"
  },
  "assigned_to": null,
  "messages": [
    {
      "direction": "outgoing",
      "text": "Reminder: your cleaning is Thursday at 10 am.",
      "at": "2026-10-22T10:00:00-04:00"
    },
    {
      "direction": "incoming",
      "text": "Can I move my cleaning to Friday?",
      "at": "2026-10-23T09:12:00-04:00"
    }
  ],
  "notes": []
}
```

### list_contacts

Contacts of the account, filtered by list, segment or search. Access: read. REST: `GET /api/v1/simpletexting/contacts`. MCP: `simpletexting_read → list_contacts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `list` | string | no | Name of a contact list. |
| `segment` | string | no | Name of a segment, from list_segments. |
| `query` | string | no | Name, phone number or email. |
| `limit` | integer | no | Page size. |
| `cursor` | string | no | next_cursor from the previous call. |

Reads the Contacts page: name, phone number, email, the lists the contact belongs to and whether the contact is subscribed. Filter by list name, by segment name or by a search. Page with next_cursor. The call reads only; it never texts anyone.

Example response:

```json
{
  "contacts": [
    {
      "name": "Dana Whitfield",
      "phone": "+12125550147",
      "email": "dana.whitfield@example.com",
      "lists": [
        "Patients"
      ],
      "subscribed": true
    },
    {
      "name": "Marcus Lee",
      "phone": "+12125550163",
      "email": "marcus.lee@example.com",
      "lists": [
        "Patients",
        "Class reminders"
      ],
      "subscribed": true
    }
  ],
  "next_cursor": null
}
```

### list_lists

The contact lists of the account with their size. Access: read. REST: `GET /api/v1/simpletexting/lists`. MCP: `simpletexting_read → list_lists`.

No parameters.

Reads the lists that campaigns, keywords and autoresponders send to: name and number of contacts. A list name from here is what schedule_campaign and add_contact_to_list expect.

Example response:

```json
{
  "lists": [
    {
      "name": "Patients",
      "contacts": 248
    },
    {
      "name": "Class reminders",
      "contacts": 61
    }
  ]
}
```

### list_segments

Saved segments under Contacts, within one list or across all contacts. Access: read. REST: `GET /api/v1/simpletexting/segments`. MCP: `simpletexting_read → list_segments`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `list` | string | no | Only segments created within this list. Leave out for all. |

Reads the segments saved under Contacts > Segments: name, the list it belongs to (or all contacts) and how many contacts match now. Segments can be used in campaigns and autoresponders, so a segment name from here works as the segment of schedule_campaign.

Example response:

```json
{
  "segments": [
    {
      "name": "Overdue for a cleaning",
      "list": "Patients",
      "contacts": 120
    },
    {
      "name": "New this month",
      "list": null,
      "contacts": 34
    }
  ]
}
```

### list_campaigns

Campaigns of the account, sent and scheduled, with recipients and send time. Access: read. REST: `GET /api/v1/simpletexting/campaigns`. MCP: `simpletexting_read → list_campaigns`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `limit` | integer | no | Page size. |
| `cursor` | string | no | next_cursor from the previous call. |

Reads the Campaigns page: name, the list or segment it goes to, the number of recipients, the send time and whether it is scheduled or sent. Use it before schedule_campaign to avoid a second campaign to the same list on the same day.

Example response:

```json
{
  "campaigns": [
    {
      "campaign_id": "cp_41c7e0",
      "name": "Flu shot reminder",
      "list": "Patients",
      "segment": "Overdue for a cleaning",
      "recipients": 120,
      "send_at": "2026-10-26T09:00:00-04:00",
      "status": "scheduled"
    },
    {
      "campaign_id": "cp_39ab12",
      "name": "October hours",
      "list": "Patients",
      "segment": null,
      "recipients": 248,
      "send_at": "2026-10-01T09:00:00-04:00",
      "status": "sent"
    }
  ],
  "next_cursor": null
}
```

### list_keywords

Keywords of the account with the list each one adds people to. Access: read. REST: `GET /api/v1/simpletexting/keywords`. MCP: `simpletexting_read → list_keywords`.

No parameters.

Reads the Keywords page: the keyword, the list a person who texts it joins, the auto confirmation message and the Engagement count. Read-only: creating or editing a keyword stays in SimpleTexting.

Example response:

```json
{
  "keywords": [
    {
      "keyword": "CLASS",
      "list": "Class reminders",
      "confirmation": "You are in! Class reminders are on. Reply STOP to opt out.",
      "engagement": 61
    }
  ]
}
```

### send_message

Send a text to one contact, as a reply in the Inbox or as a new conversation. Access: write, asks the user first. REST: `POST /api/v1/simpletexting/messages`. MCP: `simpletexting_write → send_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_phone` | string | yes | Phone number of the contact, with country code. |
| `text` | string | yes | Message text. |

Sends one text to a contact from the account number, in the contact's conversation. Returns the message id and its time. A sent text cannot be taken back. The agent should read the thread with get_conversation first. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "message_id": "m_77d0c4",
  "conversation_id": "c_8f21a6",
  "contact_phone": "+12125550147",
  "direction": "outgoing",
  "status": "sent",
  "at": "2026-10-23T09:30:00-04:00"
}
```

### schedule_message

Schedule a text to one contact for a date and time. Access: write, asks the user first. REST: `POST /api/v1/simpletexting/message/schedule`. MCP: `simpletexting_write → schedule_message`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `contact_phone` | string | yes | Phone number of the contact, with country code. |
| `text` | string | yes | Message text. |
| `send_at` | datetime | yes | When to send, ISO 8601 with offset. |

Does what the Clock icon in the Inbox does: the text goes to one contact at the time you give. Returns the scheduled message id. SimpleTexting does not let you edit a scheduled message, so a change means deleting it in the app (three dots, delete) and scheduling a new one. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "scheduled_message_id": "sm_2e90b1",
  "contact_phone": "+12125550163",
  "send_at": "2026-10-27T08:00:00-04:00",
  "status": "scheduled"
}
```

### schedule_campaign

Create a text campaign for a list or segment and schedule it. Access: write, asks the user first. REST: `POST /api/v1/simpletexting/campaign/schedule`. MCP: `simpletexting_write → schedule_campaign`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `name` | string | yes | Internal campaign name, subscribers do not see it. |
| `list` | string | yes | Name of the contact list, from list_lists. |
| `segment` | string | no | Name of a segment of that list, from list_segments. |
| `text` | string | yes | Message text. |
| `send_at` | datetime | yes | When to send, ISO 8601 with offset. |

Walks Campaigns > New: names the campaign, picks the recipients, writes the text, sets Send on to Scheduled with your date and time and clicks Schedule. Returns the campaign id and the number of recipients. The text of a scheduled campaign cannot be edited afterwards, only its time or deletion. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "campaign_id": "cp_41c7e0",
  "name": "Flu shot reminder",
  "list": "Patients",
  "segment": "Overdue for a cleaning",
  "recipients": 120,
  "send_at": "2026-10-26T09:00:00-04:00",
  "status": "scheduled"
}
```

### add_contact_to_list

Add a contact to a list, creating the contact if the number is new. Access: write, asks the user first. REST: `POST /api/v1/simpletexting/contact-to-lists`. MCP: `simpletexting_write → add_contact_to_list`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `list` | string | yes | Name of the contact list, from list_lists. |
| `contact_phone` | string | yes | Phone number, with country code. |
| `first_name` | string | no | First name. |
| `last_name` | string | no | Last name. |

Adds the number to the list and fills the name if you give it. An autoresponder set on that list fires when a contact joins, so adding a contact can send a text within minutes or after the autoresponder's delay. Returns the contact and its lists. Add only people who gave consent to be texted. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "contact": {
    "name": "Sam Okafor",
    "phone": "+12125550182",
    "lists": [
      "Class reminders"
    ],
    "created": true
  },
  "list": "Class reminders",
  "contacts_in_list": 62
}
```

### assign_conversation

Assign an Inbox conversation to a team member. Access: write. REST: `POST /api/v1/simpletexting/conversations/{conversation_id}/assign`. MCP: `simpletexting_write → assign_conversation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | string | yes | conversation_id from list_conversations. |
| `assignee` | string | yes | Name of the team member, as the Team page shows it. |

Picks the team member from the dropdown at the top of the conversation. The member must have accepted the invitation under Team. Nothing is sent to the contact, and assigning it to someone else undoes it in one call, so it does not wait for your OK.

Example response:

```json
{
  "conversation_id": "c_8f21a6",
  "assigned_to": "Priya Nair"
}
```

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

Connecting SimpleTexting takes three steps: sign up, sign in to SimpleTexting 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 SimpleTexting to your agent.

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

2. **Sign in to SimpleTexting in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to SimpleTexting 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 SimpleTexting 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.

```
Schedule a text campaign to the Overdue for a cleaning segment of the Patients list for Monday at 9:00, with this wording, and tell me how many people it reaches.
```

### Call SimpleTexting 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/simpletexting 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/simpletexting/campaign/schedule \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"Flu shot reminder","list":"Patients","segment":"Overdue for a cleaning","text":"Hi from Bright Smile Dental: flu shots are open this week. Reply YES and we will book yours.","send_at":"2026-10-26T09:00:00-04:00"}'
```

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

```
{
  "campaign_id": "cp_41c7e0",
  "name": "Flu shot reminder",
  "list": "Patients",
  "segment": "Overdue for a cleaning",
  "recipients": 120,
  "send_at": "2026-10-26T09:00:00-04:00",
  "status": "scheduled"
}
```

## Why use Cotlet for SimpleTexting?

**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 SimpleTexting 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 SimpleTexting changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect SimpleTexting to Cotlet?

Yes. You sign in to SimpleTexting yourself, in your own Cloud Browser, and we never save your password. Your agents only get SimpleTexting 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 SimpleTexting integration?**

No, Cotlet is independent of SimpleTexting. SimpleTexting's own API is too limited for this work. Cotlet works through your own SimpleTexting account, the way you use SimpleTexting 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 SimpleTexting in your console: your agents lose access at once and you stay signed in. Signing out of SimpleTexting in the browser works too, and Reset browser deletes the whole profile.

## Is there a SimpleTexting MCP server on GitHub?

Yes. Community MCP servers for SimpleTexting exist on GitHub, usually maintained by one person. They sit on the same approval-only API, so you need a token first, install the server yourself and fix it when something changes. They cover what the API covers. Cotlet hosts a server for you that works in your own account, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Ask support for an API token, clone the repo, install it, add it to each MCP client | Sign up, sign in to SimpleTexting once, add one MCP server or API key |
| When SimpleTexting changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your SimpleTexting access | An API token in a file on your computer, readable by any program you run | Your own Cloud Browser in the EU, session encrypted, only for the apps you enable, disabled for agents in one click |
| When access ends | Tools fail until you replace the token | Your Cloud Browser keeps you signed in; if SimpleTexting logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | 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 SimpleTexting 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 SimpleTexting API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the SimpleTexting 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 SimpleTexting 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 SimpleTexting 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 SimpleTexting only after you enable it. When SimpleTexting 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 SimpleTexting, sign out of SimpleTexting 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.
- **SimpleTexting's terms:** You use your own SimpleTexting account and stay responsible for following SimpleTexting's terms. Cotlet is independent and not affiliated with SimpleTexting. [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 SimpleTexting in the console and press Request access. Then you create your API key and connect SimpleTexting there.

**Do I need to be technical?**

No. You sign in to SimpleTexting 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 SimpleTexting to Cotlet?**

Yes. You sign in to SimpleTexting yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get SimpleTexting 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 SimpleTexting 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 SimpleTexting 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 SimpleTexting's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. SimpleTexting 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 SimpleTexting 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?**

SimpleTexting 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 SimpleTexting API token?**

No. Cotlet works in your own SimpleTexting account, so you skip the approval step. SimpleTexting gives its API only under approval, on any paid plan: you send support a few sentences on your use case and a written acknowledgment of its terms, and it usually reviews the request within 1 to 2 business days.

**Does my agent text people who did not agree to it?**

Cotlet does not add consent. SimpleTexting tells you to have express consent before you text contacts, and your agent works on the lists and segments you name. Say in the prompt which rows count as consent, and keep the confirmation on for send and campaign tools.

**Which countries does it cover?**

SimpleTexting serves businesses in the US and Canada, and its API page names the US, Canada, Puerto Rico and some Caribbean countries as coverage. Your agent works in the account you sign in to, so the same limits apply.

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

No. Every call to send_message, schedule_message, schedule_campaign or add_contact_to_list waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. assign_conversation runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the SimpleTexting 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/simpletexting 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.