Integrations and development

Yes, it's already available via MCP (Model Context Protocol). You connect Claude, Cursor, VS Code, Windsurf, or any compatible assistant with one command, from the "MCP (AI)" tab in your panel, and talk to it in natural language. It's an open protocol, so you're not locked into one provider.

With the API, you (or your developer) write the code that tells arrobaMail what to do. With MCP, you talk to your AI assistant in natural language and it handles it, within the permissions you granted it. The API is for custom integrations; MCP is for day-to-day work. The two coexist.

It can list and view your campaigns with their statistics, check your panel and your lists, create drafts, and subscribe or unsubscribe contacts. Every tool is marked as Read or Write. You authorize with your API Key —which you generate and revoke whenever you want— and, most importantly: the AI prepares drafts, but never triggers a send. You always press the send button.

Yes. The REST API v3 documents over 100 endpoints (auth, campaigns, lists, segmentations, senders, templates, automations, and more) with JWT authentication. Webhooks connect events —opens, clicks, bounces, complaints, unsubscribes, subscribes— so an external event can trigger a flow.

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

No. The API and MCP are included with 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.