arrobaMail
Integrations

Connect arrobaMail to everything:
your AI and your code

From your AI assistant to your own system. arrobaMail integrates via Model Context Protocol (MCP), REST API v3, and webhooks. Choose the path that fits your team.

Want to try them out? Create your free account — includes API and MCP, no card required.

Prefer a step-by-step guide? Check out the implementation guides.

AI IntegrationNew

Connect your AI to arrobaMail (MCP)

Plug in Claude, Cursor, or your assistant and run your campaigns, lists, and metrics in natural language — with safe control: the AI drafts, it doesn't send.

Claude CodeCursorVS CodeWindsurf+ other apps
See AI Integration
For developers

REST API v3 and webhooks

Programmatic control: 100+ documented endpoints, JWT authentication, and bidirectional webhooks to integrate arrobaMail with your own stack.

  • REST v3
  • JWT
  • 100+ endpoints
  • Webhooks
  • Standard HTTP
Which one should I pick?

Four paths, one for every case

You don't have to choose just one: they combine. But if you're getting started, this quick guide tells you which one fits what you need — and where to go for the details.

MCP

Ideal for
Your day-to-day with an AI assistant (Claude, Cursor, VS Code).
How it's used
Natural language, no code required. The AI queries and drafts; you approve.

REST API v3

Ideal for
Custom integrations with your e-commerce, CRM, or in-house system.
How it's used
Code over REST/JSON with JWT authentication. 100+ documented endpoints.

Webhooks

Ideal for
Having an external event (a purchase, a signup) trigger a flow in arrobaMail.
How it's used
Your system notifies over HTTP and arrobaMail reacts: starts an automation, adds a tag, sends.

Transactional

Ideal for
One-to-one emails: confirmations, receipts, password resets.
How it's used
Triggered by your system from a separate sender, to protect the reputation of both channels.
Why it matters

MCP + API + events = real automation

It's not about choosing one. The three layers work together so your marketing connects with your AI, your store, and your system.

MCP

The everyday stuff, by talking

Your AI checks metrics, manages lists, and drafts content in natural language. Zero code.

API v3

Everything else, custom-built

100+ endpoints + JWT to integrate arrobaMail with your system, with technical control and documentation.

Webhooks + Pixel

Real-time events

React to what's happening: opens, clicks, on-site conversions. To trigger your flows.

Frequently asked questions

What people ask most about integrations

It depends on the path. To run your account with an AI assistant (MCP), no code is needed: you connect it with a command and talk to it in natural language. To connect your e-commerce, your CRM, or a custom app (API and webhooks), it does help to have someone technical.

If you want to query and manage from an AI assistant, MCP. If your system needs to create contacts or send automatically, the API. If you want an external event (a purchase, a signup) to trigger a flow, webhooks. And for one-to-one emails — confirmations, receipts — transactional. They're not mutually exclusive: they combine.

Yes. The connection uses your API Key, which you generate and revoke whenever you want, and permissions are set per operation type. Most importantly: the AI can prepare drafts, but it never sends. You always press the send button yourself.

Yes, and it's common. The same business can use the API to sign up contacts from its store, webhooks to trigger a welcome message, and MCP so the team can check metrics with their assistant. The layers complement each other.

No. The API and MCP are included in your account. In fact, the Free Plan works as a testing environment: you can try the full integration, no card required, before moving to production.

Get started with arrobaMail
in under 5 minutes.

Free plan, AI generations included, no credit card required — and real support from a real team.

Try it free now
WhatsAppOur team replies