Connect Claude, Cursor, or your assistant to arrobaMail with Model Context Protocol and manage your campaigns, lists, and metrics in natural language — with secure control. It's already available: activate it with a single command.
Your AI
Your platform
The AI asks in plain language · MCP translates it into an action · arrobaMail executes it. Writes stay as drafts: nothing sends without your OK.
Model Context Protocol is an open standard that defines how an AI agent discovers capabilities and data in external systems, and how it invokes actions securely.
Instead of building a custom integration for every "agent-platform" combination, MCP is the common language. An agent that speaks MCP can operate against any MCP server, including arrobaMail's — which is already available.
The result: ask Claude from Cursor to "draft a campaign for the premium customers list" and it does it, within the guard-rails and permissions you define. Writes stay as drafts: nothing gets sent without your OK.
How the pieces connect
AI agent
Claude Code, Cursor, VS Code, Windsurf, or any compatible MCP client.
MCP server
arrobaMail exposes tools and resources with a structured schema.
Platform
Campaigns, lists, automations, metrics — the usual.
Three real ways to run arrobaMail with an AI agent on your team's side.
Vos decís
"Draft a campaign for the premium-customers list with the March promo."
Lo que pasa
The agent creates the draft with create_draft and leaves it ready in your account for you to review and publish. Nothing gets sent without your OK — all from chat, without opening the platform.
Vos decís
"How's the latest campaign doing? Show me opens, clicks, and reputation."
Lo que pasa
The agent queries get_campaign_stats and get_dashboard, gives you a clear summary, and suggests next steps. Read-only — nothing gets touched.
Vos decís
Triggered by your system: "120 new leads just came in from the form."
Lo que pasa
Your agent adds them to the right list with add_subscribers and confirms it to you. Adding and removing subscribers are allowed operations; sends never are — those you approve yourself.
The simple path is OAuth: paste your dashboard URL into your assistant and sign in, no keys. Developer clients can still use the API Key route. Works with the most popular clients — and with any other app that speaks MCP.
The same connector works in claude.ai, Claude Desktop, Cowork, and Claude Code.
claude mcp add --transport http arrobamail-com \
https://envios.arrobamail.com/v3/api/mcp
/mcp{
"mcpServers": {
"arrobamail-com": {
"command": "npx",
"args": [
"-y", "mcp-remote",
"https://envios.arrobamail.com/v3/api/mcp",
"--header", "Authorization:Bearer TU_API_KEY"
]
}
}
}Endpoint
{servidor}.arrobamail.com/v3/api/mcpTransport
Remote HTTP (Streamable) · stdio via mcp-remote
Authentication
OAuth 2.1 (recommended) · API Key for dev clients
Cursor, VS Code, and Windsurf support native remote MCP: add the server with that URL (OAuth or your API Key). The exact steps for each client are in your dashboard, in the MCP (AI) tab.
Giving an AI access to your marketing doesn't mean losing control. These four boundaries come built in.
The connection uses your API Key, which you generate and revoke from the dashboard whenever you want. No key, no access.
Every tool is marked as Read or Write. You know exactly what your AI can query and what it can touch.
The most sensitive part stays in your hands: the AI drafts campaigns (create_draft doesn't send). You approve and execute the send yourself.
MCP is an open protocol, with no proprietary extensions locking you in. What you connect today, you can keep connecting tomorrow.
39 tools across six families, each marked as Read or Write. Saving a draft sends nothing, and sensitive operations —sending, scheduling— always ask for your confirmation.
| Tool | What it does | Type |
|---|---|---|
| Campaigns | ||
list_campaigns | Lists campaigns with pagination and status filter | lectura |
get_campaign | Details of a campaign by ID | lectura |
get_campaign_stats | Delivery and engagement statistics for a campaign | lectura |
validate_campaign | Checks that a campaign is ready to send | lectura |
send_test_campaign | Sends a test to your own inbox | escritura |
schedule_campaign | Schedules the send for a date and time | escritura |
send_campaign_now | Triggers the immediate send | escritura |
stop_campaign | Stops a send in progress | escritura |
resume_campaign | Resumes a stopped send | escritura |
| Drafts and emails | ||
list_campaign_drafts | Lists campaign drafts | lectura |
get_campaign_draft | Details of a draft | lectura |
save_campaign_draft | Creates or updates a draft (doesn't send) | escritura |
list_emails | Lists saved email pieces | lectura |
get_email | Fetches the content of an email piece | lectura |
save_email | Saves the HTML of an email piece | escritura |
| Lists and subscribers | ||
list_lists | List of subscriber lists | lectura |
get_list | Details of a list by ID | lectura |
add_subscribers | Adds subscribers to a list (max 100) | escritura |
remove_subscriber | Unsubscribes a contact from a list | escritura |
| Segmentations | ||
list_segmentations | Lists a list's segmentations | lectura |
get_segmentation | Details of a segmentation | lectura |
get_segmentation_conditions | Conditions and rules of a segmentation | lectura |
preview_segmentation | Shows matching contacts before you use it | lectura |
count_segmentation | Counts how many contacts match | lectura |
create_segmentation | Creates a new segmentation | escritura |
update_segmentation | Modifies a segmentation's rules | escritura |
duplicate_segmentation | Duplicates a segmentation to try variants | escritura |
delete_segmentation | Deletes a segmentation | escritura |
| Automations | ||
list_automations | Lists the account's automations | lectura |
get_automation | Details of an automation | lectura |
get_automation_stats | Performance of an automation | lectura |
list_automation_enrollments | Who's enrolled and at which step | lectura |
create_automation_draft | Creates an automation draft | escritura |
update_automation_draft | Edits an automation draft | escritura |
activate_automation | Activates an automation | escritura |
pause_automation | Pauses an active automation | escritura |
archive_automation | Archives an automation | escritura |
| Account and reports | ||
get_dashboard | Overall summary: sends, opens, activity | lectura |
get_account_info | Account info: email, reputation, usage | lectura |
MCP covers the most common tasks in natural language. For everything else — and for custom integrations — there's the API v3, with 100+ endpoints and webhooks.
Yes, it's already available. You connect Claude, Cursor, VS Code, Windsurf, or any compatible assistant with a single command, from the "MCP (AI)" tab in your dashboard. And if you prefer the classic route, the API is still there.
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've given it. The API is for custom integrations; MCP is for day-to-day work. Both coexist.
Today it can list and view your campaigns with their statistics, check your dashboard and account data, view your lists, create campaign drafts, and add or remove subscribers. Every tool is marked as Read or Write, so you know exactly what it can query and what it can touch.
Yes. You authorize it with your API Key — which you generate and revoke whenever you want — and permissions are set by operation type. Most importantly: the AI can prepare drafts, but it doesn't trigger sends. You always press the send button yourself.
Claude, Cursor, VS Code, and Windsurf have their own instructions in your dashboard; and any other assistant that speaks the MCP standard can connect too. It's an open protocol, with no ties to a single provider.
No. Amanda IA is arrobaMail's own artificial intelligence and lives inside the product: it generates campaigns, subject lines, and images. MCP is for external assistants (Claude, Cursor, or your own) to operate on your account with permissions. They're different, complementary things.
The simplest way is OAuth, no code: copy the URL from your dashboard ("MCP (IA)" tab), paste it into your assistant as a custom connector, and sign in with your account. Developer clients also accept the API Key connection. We explain it step by step, with screenshots, in the tutorial.
Free plan, AI generations included, no credit card required — and real support from a real team.