Posylai — AI Email Builder MCP server

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 — the password is emailed to you.
2. Sign in to .
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

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

Claude Desktop, Cursor, VS Code, Codex, Windsurf

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

Per-client file locations are in examples/.

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

Typical flow

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

Tools — 29 total

Brand and style (9) unifiedbrands · unifieddesignsystem · unifiedbrandquestionnaire · unifiedbranddesigncode · unifiedbrandsketch · unifiedbrandsketchstatus · unifiedbrandsketchedit · unifiedbrandbriefsubmit · unifiedbrand_create

Campaign build (6) unifiedmasters · unifiedplanstart · unifiedjobstatus · unifiedapplydc · unifiedrender · unified_rerender

Quality checks (4) unifiedqareport · unifiedqarun · unifiedgate · unifiedsection_images

Edits (9) unifiedslotset · unifiedsectionget · unifiedsectionput · unifiedsectionupdate · unifiedfixfinding · unifiedsectiondisable · unifieduploadasset · unifieddcget · unifieddcput

Export (1) unified_export

What it does not do

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

through your ESP — Unisender, Sendsay, Mindbox, Mailganer or any other.

• It does not send campaigns to a list. It returns HTML; sending happens

site or brand book, not made up.

• 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

Shortened. The full README is on GitHub.