Sender
Email marketing platform for creating campaigns, automating workflows, and tracking results
Verdict
Common use cases
- Add new subscribers from chat during events
- Check campaign delivery stats before standups
- Audit custom fields for segmentation cleanup
- Retrieve subscriber details for support tickets
- Review automation workflows before launches
Integration
- Vendor
- Sender
- Category
- other
- Auth
- API_KEY
- Tools
- 9
- Composio slug
sender
Tools
- Create Field
Tool to create a new custom subscriber field in Sender.net. Use when you need to add custom fields for email personalization, segmentation, or storing additional subscriber information like company name, birthday, job title, or other custom
- Create Or Update Subscriber
Tool to create a new subscriber or update an existing one in Sender.net. Use when you need to add new subscribers to your email list or update existing subscriber information. This performs an upsert operation - creates if the email doesn't
- Get All Fields
Tool to retrieve a list of all custom subscriber fields configured in the Sender.net account. Use when you need to view available fields for email personalization, segmentation, or managing subscriber data.
- Get All Workflows
Tool to retrieve a list of all automation workflows in the Sender account. Use when you need to view or manage automation workflows.
- Get Campaign By ID
Tool to retrieve a specific campaign by its unique ID from Sender. Use when you need detailed information about a campaign including delivery metrics and engagement statistics.
- Get Group By ID
Tool to retrieve a specific subscriber group by its unique ID from Sender. Use when you need detailed information about a single group including subscriber counts.
- Get Subscriber By Email
Tool to retrieve a specific subscriber by their email address from Sender. Use when you need to fetch detailed information about a single subscriber including their status, groups, and custom fields.
- Get Subscriber By ID
Tool to retrieve a specific subscriber by their unique ID from Sender. Use when you need to fetch detailed information about a single subscriber including their status, groups, and custom fields.
- Update Subscriber Fields
Tool to update custom fields and information for an existing subscriber in Sender.net. Use when you need to modify subscriber details such as email, first name, last name, groups, or custom fields for email personalization and segmentation.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations section. 2. Click 'Add Integration' and select Sender from the list. 3. Log into your Sender account, go to Settings > API, and generate a new API key with full read/write permissions. 4. Copy the key and paste it into the Switchy connection dialog, then click 'Connect'. 5. Switchy will validate the key and confirm the connection — you'll see a green checkmark when it succeeds. 6. Open any Space, type '@Sender get all workflows' in the chat, and hit send to test the connection. 7. If you see a list of your automation workflows, the integration is live and ready to use.
What teammates see: by default, memories from Sender are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Add Event Attendees
@Sender create or update subscribers for these emails: alice@example.com, bob@example.com, carol@example.com. Set their source field to 'Webinar Q1 2024'.Open in a Space →
Check Campaign Performance
@Sender get campaign by ID 12345 and summarize the open rate, click rate, and total recipients.Open in a Space →
Audit Custom Fields
@Sender get all fields and show me their names, types, and whether they're required.Open in a Space →
Lookup Subscriber Status
@Sender get subscriber by email support@customer.com and tell me their subscription status and which groups they belong to.Open in a Space →
Review Active Workflows
@Sender get all workflows and list their names, trigger types, and whether they're currently active.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Sender show me the subscriber details for alice@example.com including which groups she's in and her custom field values
Found subscriber Alice Johnson (ID: sub_8x9k2m). Status: Active. Member of 2 groups: 'Product Updates' and 'Weekly Newsletter'. Custom fields: company='Acme Corp', signup_source='landing_page_q4', last_purchase_date='2024-01-15'. Email verified on 2023-11-02. This illustrative example shows how Sender returns subscriber profile data including group memberships and any custom fields you've configured for segmentation.
This read operation requires an API key with subscriber read permissions. Useful for checking subscriber status before sending targeted campaigns or debugging why someone isn't receiving emails. The custom fields returned depend entirely on what your Sender account has configured—this example assumes you've created 'company', 'signup_source', and 'last_purchase_date' fields.
@Sender add bob@startup.io to our mailing list with custom fields: company='StartupXYZ', role='CTO', and add him to the 'Enterprise Tier' group
Subscriber created successfully. Email: bob@startup.io, ID: sub_9p4n7q. Custom fields set: company='StartupXYZ', role='CTO'. Added to group 'Enterprise Tier' (group_5k8m). Status: Active, pending email verification. This illustrative example shows Sender's upsert behavior—if bob@startup.io already existed, his fields would be updated instead. The subscriber will receive a confirmation email per your account's double opt-in settings.
This write operation modifies your subscriber list and may trigger automation workflows if you have welcome sequences configured. Requires API key with subscriber write permissions. Be aware that adding subscribers without proper consent violates anti-spam regulations—ensure you have opt-in records. The 'Enterprise Tier' group must already exist in your Sender account.
@Sender list all my automation workflows and tell me which ones are currently active and what their trigger conditions are
Found 4 automation workflows in your Sender account. Active: 'Welcome Series' (trigger: new subscriber joins any group, 3-email sequence over 7 days), 'Cart Abandonment' (trigger: custom field 'cart_status'='abandoned', sends reminder after 2 hours). Paused: 'Re-engagement Campaign' (trigger: subscriber inactive >90 days), 'Birthday Emails' (trigger: custom field 'birthday' matches current date). This illustrative example shows how you can audit your automation setup to understand what's running and what conditions fire each workflow.
This read operation helps you understand your automation landscape before making changes or diagnosing why subscribers aren't receiving expected emails. Useful when paired with the AI to identify gaps—for example, asking 'do I have a workflow for trial expiration?' The actual workflow details depend on what you've configured in Sender's automation builder. No side effects, but requires API key with workflow read permissions.
Use-case deep-dives
When Sender wins for event-driven email automation at small scale
A 3-person SaaS team runs monthly webinars and needs to sync registrants from Typeform into Sender, then trigger a 5-email nurture sequence. The Create Or Update Subscriber tool handles the upsert in one call—no duplicate checking logic required. Create Field lets you store webinar topic or attendance status for segmentation. Get All Workflows confirms your automation is live before the event. This works cleanly if you're syncing under 500 contacts per event and your webinar cadence is weekly or slower. Above that volume or if you need real-time sync under 60 seconds, you'll hit API rate limits and need a dedicated integration platform. For most early-stage teams running occasional events, Sender's MCP keeps the stack simple and the sync reliable.
When this MCP is overkill for support workflows
A 6-person support team wants to pull email engagement data into their helpdesk to see if a customer opened recent product updates before replying to their ticket. Get Subscriber By Email and Get Campaign By ID can surface that context, but the workflow is clunky: you're making two API calls per ticket, and Sender doesn't expose click-level heatmaps or inbox placement data that would actually change your reply strategy. If your support volume is under 20 tickets a day and you're already in Sender for lifecycle emails, the MCP gives you a lightweight lookup option. Beyond that threshold, or if you need behavioral scoring that influences routing or SLA, a proper CDP or customer data tool will serve you better. Sender's MCP is built for email operations, not support intelligence.
When Sender's MCP handles list hygiene at team scale
A 4-person content team sends a monthly newsletter to 8,000 subscribers and needs to audit inactive contacts every quarter before a re-engagement campaign. Get All Fields pulls your custom engagement tags, Get Subscriber By ID lets you spot-check high-value contacts, and Get Group By ID confirms which segments are growing or shrinking. The 9-tool set is enough to script a basic health check without logging into the Sender dashboard. This works if your list is under 15,000 contacts and you're auditing manually or on a slow cron job. If you're managing multiple brands, need automated suppression rules, or your list tops 25,000, you'll want a dedicated email ops platform with bulk export and advanced segmentation APIs. For single-brand teams at this scale, Sender's MCP keeps quarterly hygiene tasks in your existing workflow.
Frequently asked
What does the Sender MCP let me do in Switchy?
It connects your Sender.net email marketing account so AI agents can create and update subscribers, manage custom fields, pull campaign metrics, and check automation workflows. You can ask an agent to add someone to your list, retrieve engagement stats for a campaign, or audit which custom fields exist — without opening Sender's dashboard.
Do I need admin access to connect Sender MCP?
You need an API key from your Sender.net account, which typically requires admin or account-owner permissions to generate. Once you paste that key into Switchy, the MCP can read and write subscriber data, create fields, and fetch campaign details. If your Sender account restricts API access by role, check with your account owner first.
Can the Sender MCP send or schedule email campaigns?
No. The MCP reads campaign details and workflow lists but doesn't trigger sends or schedule new campaigns. It's designed for subscriber management and reporting — adding people to lists, updating custom fields, pulling delivery metrics. To actually send a campaign, you still log into Sender.net or use their separate campaign API endpoints.
Why use this MCP instead of Sender's web app or API?
The MCP wraps Sender's API so AI agents can handle repetitive subscriber tasks in natural language — no manual CSV uploads or API scripting. If you're already comfortable in Sender's UI or have custom integrations, you might not need it. The win is speed: ask an agent to update fifty subscribers' company fields instead of clicking through forms.
Who on my team should connect the Sender MCP?
Whoever owns your email list or manages Sender.net day-to-day. That person generates the API key and pastes it into Switchy. Once connected, any teammate in your Switchy workspace can ask agents to query subscribers or update fields — but the API key's permissions apply to everyone, so choose someone who understands your data-access policies.