otherapi_key

Elastic Email

Elastic Email provides transactional email delivery, email marketing, contact and campaign management, reporting, verification, and account administration APIs.

Verdict

Elastic Email's MCP exposes 50 tools for managing email campaigns, contacts, and deliverability directly from Switchy. @mention it to add contacts to lists, create campaigns, adjust subaccount credits, or check domain restrictions without opening the Elastic Email dashboard. Marketing teams running drip campaigns get the most value — you can draft copy in a Project, then push it straight to a campaign. The MCP requires an API key with full account access, so treat it like a production credential. Campaign sends are immediate and irreversible once scheduled.

Common use cases

  • Draft campaign copy and push to Elastic Email
  • Bulk-add leads from spreadsheet to contact lists
  • Check domain reputation before cold outreach
  • Adjust subaccount credits for client campaigns
  • Suppress bounced addresses after failed sends

Integration

Vendor
Elastic Email
Category
other
Auth
API_KEY
Tools
50
Composio slug
elastic_email

Tools

  • Add Contact List Members

    Add selected existing contacts to a named Elastic Email contact list.

  • Add Contacts

    Add up to 1000 Elastic Email contacts and optionally assign them to existing lists.

  • Add Suppressions

    Add up to 1000 email addresses to Elastic Email's bounce, complaint, or unsubscribe suppression records.

  • Adjust Subaccount Credits

    Add or remove email credits from a managed Elastic Email subaccount. Requires an Elastic Email PRO plan. The signed adjustment is not idempotent; a retry can apply the adjustment twice.

  • Check Domain Restriction

    Check whether Elastic Email restricts a domain or identifies it as a free-provider domain.

  • Create Campaign

    Create a campaign. An active or scheduled campaign may initiate email delivery, and sent messages cannot be recalled.

  • Create Contact List

    Create a contact list, optionally with initial email members.

  • Create Domain

    Create a sending or tracking domain in the connected Elastic Email account.

  • Create Inbound Route

    Create a new inbound email route.

  • Create Segment

    Create a dynamic contact segment from a name and SQL-like rule.

  • Create Subaccount

    Create a managed subaccount with optional initial email settings. An activation email can be sent; when activation email delivery is disabled, the subaccount is activated immediately. Requires an Elastic Email PRO plan.

  • Create Template

    Create a new email template with its name, content, and scope.

  • Create Webhook

    Create a webhook subscription for selected email events.

  • Delete Campaign
    destructive

    Delete one campaign by exact name. This does not cancel email already in progress.

  • Delete Contact
    destructive

    Delete one contact by exact email address.

  • Delete Contact List
    destructive

    Delete one contact list by exact name. Contacts that belonged to the list are removed from it but are not deleted.

  • Delete Contacts
    destructive

    Permanently delete 1-10 contacts by exact email address. This destructive action sends one targeted deletion per address and reports partial failures; it does not use rule-based bulk deletion.

  • Delete Domain
    destructive

    Delete one configured domain from the connected Elastic Email account.

  • Delete Email Verification
    destructive

    Delete one saved email verification result by exact email address.

  • Delete File
    destructive

    Permanently delete one stored file by its exact name.

  • Delete Inbound Route
    destructive

    Permanently delete one inbound email route by its public ID.

  • Delete Segment
    destructive

    Delete one Elastic Email dynamic contact segment by its exact name.

  • Delete Suppression
    destructive

    Remove one email address from Elastic Email suppression records. This can allow sending to resume, so use only with documented recipient consent.

  • Delete Template
    destructive

    Delete one Elastic Email template by its exact name.

  • Delete Verification File
    destructive

    Delete one uploaded verification file job by its VerificationID.

  • Delete Webhook
    destructive

    Delete one webhook subscription by its public WebhookID.

  • Download File

    Download a stored Elastic Email file by its exact name.

  • Download Verification File Results

    Download the ZIP result archive for a completed verification file job.

  • Get Account Statistics

    Return aggregate Elastic Email delivery statistics for a time interval.

  • Get Campaign

    Return one Elastic Email campaign by its exact name.

  • Get Contact

    Return one Elastic Email contact by email address.

  • Get Contact Export Status

    Get the current status of an asynchronous contact export job.

  • Get Contact List

    Return one Elastic Email contact list by its exact name.

  • Get Credential Metadata

    Get one Elastic Email API-key or SMTP credential's audit metadata without returning its secret token.

  • Get Domain

    Return detailed DNS and certificate state for one Elastic Email domain.

  • Get Email Job Status

    Return delivery status and optional recipient-level details for an Elastic Email transaction.

  • Get Email Preview

    Return the rendered preview, attachment metadata, and delivery status for an Elastic Email message ID.

  • Get Email Verification

    Return the saved Elastic Email verification result for one email address.

  • Get Event Export Status

    Get the current status of an asynchronous global or channel event export. Use export_scope='global' when Start Event Export had no channel, and export_scope='channel' when it targeted a channel.

  • Get File Info

    Return metadata for a stored Elastic Email file without downloading it.

  • Get Inbound Route

    Return one Elastic Email inbound route by its public ID.

  • Get Segment

    Return one Elastic Email dynamic contact segment by its exact name.

  • Get Statistics Breakdown

    Return one Elastic Email campaign or channel delivery summary by exact name.

  • Get Subaccount

    Return one managed Elastic Email subaccount by its login email. Requires an Elastic Email PRO plan.

  • Get Suppression

    Return suppression details for one Elastic Email address.

  • Get Template

    Return one Elastic Email template by its exact name.

  • Get Verification File Results

    Return one page of detailed results and metadata for a verification file.

  • Get Webhook

    Return one Elastic Email webhook subscription by its public ID.

  • Import Contacts

    Start an asynchronous contact import using exactly one source: an uploaded CSV file or a provider-accessible CSV URL.

  • Import Suppressions

    Upload CSV content containing bounced, complained, or unsubscribed email addresses for asynchronous suppression import.

Setup

Setup guide

  1. 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Click 'Add MCP Integration' and select Elastic Email from the list. 3. Log into your Elastic Email account, go to Settings → API, and generate a new API key with full permissions. 4. Paste the API key into Switchy's connection form and click 'Connect'. 5. Switchy will verify the key by fetching your account details — if successful, you'll see 'Connected' next to Elastic Email. 6. Open any Project, type '@Elastic Email list my contact lists' in the chat, and confirm the MCP returns your existing lists to verify the connection works. 7. You can now invoke any of the 50 tools by @mentioning Elastic Email and describing the task in plain language.

What teammates see: by default, memories from Elastic Email are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.

Works well with

Top models

Compatibility data appears once enough Projects have used this MCP together with a given model.

How Switchy teams use it

Not enough Projects yet to publish anonymised usage stats (we require ≥ 50 Projects per week).

Starter prompts

List Active Campaigns

@Elastic Email show me all active and scheduled campaigns in my account, including their names, statuses, and scheduled send times.

Add Contacts to List

@Elastic Email add these email addresses to my 'Q1 Leads' contact list: john@example.com, sarah@example.com, mike@example.com.

Create Drip Campaign

@Elastic Email create a new campaign called 'Product Launch Announcement' with subject 'Introducing Our New Feature' and the email body I drafted above. Use my verified sender address.

Check Domain Restrictions

@Elastic Email check if the domain 'newclient.com' is restricted or marked as a free provider in your system.

Suppress Bounced Emails

@Elastic Email add these addresses to the bounce suppression list: bounce1@example.com, bounce2@example.com, bounce3@example.com.

Example outputs

Illustrative - representative of the model's voice and quality, not literal recordings.

Prompt

@elastic-email show me all contact lists with more than 500 members and their engagement rates from the last 30 days

Output

Found 4 contact lists exceeding 500 members: • Newsletter Subscribers (1,247 members) – 24.3% open rate, 3.1% click rate • Product Updates (892 members) – 31.7% open rate, 5.8% click rate • Webinar Attendees (654 members) – 28.9% open rate, 4.2% click rate • Trial Users (531 members) – 19.4% open rate, 2.3% click rate Engagement calculated from campaigns sent between Dec 15, 2024 – Jan 14, 2025. This is an illustrative example; actual list sizes and metrics will reflect your account's current state.

Notes

This read-heavy example demonstrates list retrieval and engagement analysis. Requires API key with read access to contacts and campaign statistics. Rate limits apply to bulk contact queries—fetching detailed metrics for large lists may take several seconds.

Prompt

@elastic-email create a new campaign called 'Q1 Feature Launch' targeting the Product Updates list, subject line 'Three new tools to try today', scheduled for January 20 at 9am EST

Output

Campaign 'Q1 Feature Launch' created successfully. • Campaign ID: cmp_8x4k2n9p • Target: Product Updates list (892 contacts) • Subject: Three new tools to try today • Scheduled: January 20, 2025 at 09:00 EST (14:00 UTC) • Status: Scheduled Note: This campaign will send 892 emails when triggered. You can edit or cancel it before the scheduled time through your Elastic Email dashboard. This is an illustrative example showing the confirmation structure.

Notes

This write example shows campaign creation with scheduling. Once a campaign sends, messages cannot be recalled—verify list targeting and content before scheduling. Requires API key with campaign creation permissions. Subaccounts need sufficient email credits allocated.

Prompt

@elastic-email analyze bounce and complaint rates across all campaigns from December, identify the three worst-performing subject lines, and draft recommendations to improve deliverability

Output

December 2024 Campaign Analysis: Worst-performing subject lines by bounce + complaint rate: 1. 'URGENT: Limited Time Offer!!!' – 8.2% bounce, 1.4% complaint 2. 'You Won't Believe This Deal' – 6.7% bounce, 1.1% complaint 3. 'RE: Your Account Status' – 5.9% bounce, 0.9% complaint **Deliverability Recommendations:** • Remove excessive punctuation and all-caps from subject lines • Avoid misleading 'RE:' prefixes that imply prior conversation • Test subject lines with spam-score tools before sending • Segment lists to remove contacts with prior bounces This illustrative example combines campaign metrics with AI reasoning to surface actionable patterns.

Notes

This synthesis example pairs Elastic Email's campaign statistics with AI analysis to identify patterns and generate recommendations. Requires read access to campaign data and suppression lists. The AI cannot directly modify campaigns—recommendations must be manually implemented in future sends.

Use-case deep-dives

SaaS onboarding drip campaigns

When Elastic Email beats Mailchimp for product-led onboarding

A 6-person SaaS team running a freemium product needs to send 40,000 onboarding emails per month—welcome sequences, feature tips, upgrade nudges—without paying Mailchimp's per-contact premium. Elastic Email wins here because the MCP's 50 tools let you script the entire flow: create contact lists by signup cohort, add new users in batches of 1000, launch campaigns on a schedule, and adjust subaccount credits when your agency client needs their own sending pool. The API_KEY auth means any team member can trigger sends from a shared Switchy workspace without logging into the Elastic dashboard. If your onboarding logic changes weekly and you need version-controlled campaign templates, this MCP is the right call. Buy Elastic Email if you send more than 10,000 emails a month and your team already lives in code or AI workspaces.

Agency client email reputation management

Managing multi-client suppression lists at agency scale

A 3-person email marketing agency manages 12 client accounts, each with its own suppression rules—one client scrubs all Gmail addresses, another maintains a manual complaint list from customer service tickets. The Elastic Email MCP handles this because you can add up to 1000 suppressions per call and check domain restrictions in batch before a send, all from a single Switchy workspace where the team reviews client campaigns together. The subaccount credit adjustment tool means you can top up a client's send quota mid-month without opening a support ticket. The trade-off: if a client needs real-time bounce webhooks or advanced segmentation beyond list membership, you'll hit the MCP's ceiling and need to write custom integrations. This setup works when your clients care more about deliverability hygiene than marketing automation bells and whistles.

Event registration confirmation sends

Why this MCP is overkill for one-off event emails

A 2-person nonprofit running a quarterly fundraiser gala needs to send 800 ticket confirmations and 200 last-minute reminders. Elastic Email's MCP can do it—create a contact list, add the registrants, launch a campaign—but the 50-tool surface area is wasted when you only need three actions twice a year. The API_KEY setup and credit management tools assume you're sending at scale or managing multiple accounts, not firing off a few hundred emails per quarter. If your event volume stays under 2,000 sends per year and you don't need suppression list hygiene between events, a simpler transactional email MCP or even a manual Elastic Email dashboard session is faster. Buy this MCP when you run 6+ events annually or when your registration flow needs to trigger follow-up sequences that change based on attendee behavior.

Frequently asked

What does the Elastic Email MCP do in Switchy?

It connects your Elastic Email account so AI agents can manage contacts, create campaigns, adjust subaccount credits, and handle suppression lists without leaving Switchy. The MCP exposes 50 tools covering list management, domain setup, and campaign creation. You authenticate once with an API key, then agents can execute bulk operations like adding 1000 contacts or checking domain restrictions on demand.

Do I need admin access to connect Elastic Email?

You need an Elastic Email API key with sufficient permissions for the operations you want agents to perform. Some tools—like adjusting subaccount credits—require an Elastic Email PRO plan. The API key acts as a bearer token, so whoever generates it controls which resources the MCP can touch. Store it in Switchy's credential vault; don't share it in chat.

Can the MCP recall or cancel a campaign after it starts sending?

No. Once a campaign is active or scheduled, Elastic Email begins delivery and sent messages cannot be recalled. The Create Campaign tool warns about this explicitly. If you need to stop a campaign, pause it in the Elastic Email dashboard before messages go out. The MCP is for setup and triggering, not mid-flight cancellation.

How does this compare to using Elastic Email's dashboard or API directly?

The MCP wraps Elastic Email's REST API so agents can execute multi-step workflows—like creating a list, adding contacts, then launching a campaign—in a single conversation. You skip manual API calls and credential juggling. Trade-off: the MCP doesn't expose every Elastic Email endpoint, and retrying certain tools (like Adjust Subaccount Credits) can double-apply changes because they're not idempotent.

Who on the team should connect this MCP?

Whoever owns your Elastic Email account and can generate API keys with the right scopes. Marketing ops or a technical admin is typical. Once connected, any Switchy workspace member can invoke the tools through agents, so lock down the API key's permissions to match your team's trust boundaries. The MCP doesn't enforce per-user access control inside Elastic Email.

More other MCPs

See all other MCPs →

Data last verified 61 hours ago.Sources aggregated hourly to weekly. See docs/architecture/model-directory.md.