posylai-mcp

# Posylai MCP — AI Email Builder

Build production-ready HTML email campaigns from any brand website.

Posylai MCP lets Claude, Cursor, Codex and other MCP-compatible agents analyze a
brand website, build an email design system from it, assemble responsive
campaigns, QA the rendering and export production HTML.

**Remote MCP endpoint**

```
https://mcp.posylai.ru/mcp
```

Transport: streamable HTTP. Authentication: personal bearer token.

---

## What it does

Most email tooling starts from a blank template. Posylai starts from the brand's
own website: it reads the real markup — typography, palette, spacing rhythm,
button shapes, image treatment — and turns it into a reusable master template.
Campaigns are then assembled from that template's blocks, so every email looks
like the brand instead of like a generic newsletter.

The rendered result is checked before it is handed back: mobile column, alt
texts, unsubscribe link, message weight, appearance across mail clients.

Typical timings on our pipeline: ~15 minutes to build a master template from a
site, ~10 minutes per campaign after that.

## Getting a token

1. Register at <https://posylai.ru/login.html#reg> — the password is emailed to you.
2. Sign in to <https://posylai.ru/account/>.
3. Issue an MCP token there.

Tokens are per user, not per server: the endpoint answers nothing without a
valid one, and revoking a token in the dashboard takes effect immediately
without affecting anyone else.

The first template is free.

## Client configuration

### Claude Code

```bash
claude mcp add --transport http posylai https://mcp.posylai.ru/mcp \
  --header "Authorization: Bearer YOUR_TOKEN"
```

### Claude Desktop, Cursor, VS Code, Codex, Windsurf

```json
{
  "mcpServers": {
    "posylai": {
      "type": "http",
      "url": "https://mcp.posylai.ru/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN"
      }
    }
  }
}
```

Per-client file locations are in [`examples/`](examples/).

Any client that speaks streamable HTTP MCP with a bearer header will work; there
is nothing client-specific in the server.

## Typical flow

| Step | Tool | What happens |
|---|---|---|
| 1 | `unified_brands` | List brands already set up |
| 2 | `unified_brand_design_code` | Extract the visual language from a website |
| 3 | `unified_brand_sketch` | Draft a master template prototype |
| 4 | `unified_brand_create` | Create the brand from the prototype |
| 5 | `unified_plan_start` | Assemble a campaign from a brief |
| 6 | `unified_job_status` | Poll until it is ready |
| 7 | `unified_render` | Render the email to images |
| 8 | `unified_gate` | Pre-send checks |
| 9 | `unified_export` | Take the production HTML |

Status tools report progress, so an agent never has to wait blind.

## Tools — 29 total

**Brand and style (9)**
`unified_brands` · `unified_design_system` · `unified_brand_questionnaire` ·
`unified_brand_design_code` · `unified_brand_sketch` ·
`unified_brand_sketch_status` · `unified_brand_sketch_edit` ·
`unified_brand_brief_submit` · `unified_brand_create`

**Campaign build (6)**
`unified_masters` · `unified_plan_start` · `unified_job_status` ·
`unified_apply_dc` · `unified_render` · `unified_rerender`

**Quality checks (4)**
`unified_qa_report` · `unified_qa_run` · `unified_gate` · `unified_section_images`

**Edits (9)**
`unified_slot_set` · `unified_section_get` · `unified_section_put` ·
`unified_section_update` · `unified_fix_finding` · `unified_section_disable` ·
`unified_upload_asset` · `unified_dc_get` · `unified_dc_put`

**Export (1)**
`unified_export`

## What it does not do

Worth stating plainly so an agent does not plan around it:

- **It does not send campaigns to a list.** It returns HTML; sending happens
  through your ESP — Unisender, Sendsay, Mindbox, Mailganer or any other.
- **It does not store subscribers** and does not segment them.
- **It does not invent a visual identity.** The style is taken from the brand's
  site or brand book, not made up.

## Discovery

Machine-readable manifest, open without a token:

```
https://mcp.posylai.ru/.well-known/mcp.json
```

Human documentation: <https://posylai.ru/mcp/>

## Support

<hello@crmlove.ru>

---

## По-русски

**Posylai MCP** даёт ИИ-агентам 29 инструментов для сборки email-писем по адресу
сайта бренда: снять фирменный стиль, собрать мастер-шаблон, сформировать письмо
по заданию, проверить вёрстку и забрать готовый HTML.

Адрес сервера — `https://mcp.posylai.ru/mcp`, транспорт streamable HTTP,
авторизация личным токеном. Токен выпускается в
[личном кабинете](https://posylai.ru/account/) после
[регистрации](https://posylai.ru/login.html#reg); первый шаблон бесплатный.

Токен привязан к учётной записи: без действующего токена сервер не отвечает.
Отозвать его можно в кабинете, старый перестаёт работать сразу.

Сервер не рассылает письма по базе и не хранит подписчиков — он отдаёт готовый
HTML, а отправка идёт через ваш сервис рассылок. Подробная документация
на русском: <https://posylai.ru/mcp/>

## License

MIT — see [LICENSE](LICENSE).

This repository contains the public manifest, documentation and client
configuration examples. The server itself is a hosted service.