Smtp2go
SMTP2GO is a reliable email delivery service that ensures your emails reach recipients' inboxes efficiently.
Verdict
Common use cases
- Whitelist a new sender domain before launch
- Provision SMTP credentials for a staging environment
- Check why an email bounced or landed in spam
- Add unsubscribes to the suppression list automatically
- Set up webhooks for delivery event tracking
Integration
- Vendor
- Smtp2go
- Category
- other
- Auth
- API_KEY
- Tools
- 32
- Composio slug
smtp2go
Tools
- Add Allowed Sender
Tool to add a new allowed sender email address. use when you need to whitelist a sender before sending email. example: add "user@example.com" to allowed senders list.
- Add IP Allow List
Tool to add an ip address or cidr range to your account’s ip allow list. use when you need to whitelist specific sending sources by ip or cidr after confirming accuracy.
- Add Sender Domain
Tool to add a new sender domain for spf/dkim verification. use when you need to register a domain and optionally set tracking/return-path subdomains.
- Add SMTP User
Tool to add a new smtp user. use when you need to provision a fresh smtp credential after collecting username and password.
- Add to Suppression List
Tool to add email addresses or domains to the suppression list. use when you need to block sending emails to specific recipients or entire domains after unsubscribes or bounces.
- Add Webhook
Tool to create a new webhook. use when you need real-time notifications of email or sms events.
- Edit Email Template
Tool to edit details of an existing email template. use when you need to update template properties after confirming its id.
- Edit SMTP User
Tool to edit details of an existing smtp user. use when you need to update username, password, sender restrictions, or enable/disable a user after confirming the target username.
- Edit Webhook
Tool to edit an existing webhook’s settings. use when you need to update a webhook's configuration after creation.
- Email Cycle Statistics
Tool to retrieve email cycle statistics. use when you need to analyze email delivery metrics over a specified date range.
- Email History Statistics
Tool to retrieve email history statistics. use when you need detailed delivery metrics within a date range.
- Email Spam Statistics
Tool to retrieve email spam report statistics. use when analyzing spam trends for sent emails.
- Email Unsubscription Stats
Tool to retrieve email unsubscribe statistics. use when you need unsubscribe data for your account over a date range.
- Get Email Bounces Stats
Tool to retrieve email bounces statistics. use after sending emails to analyze bounce metrics over a time period.
- Remove Allowed Senderdestructive
Tool to remove a sender email address from the allowed senders list. use when you need to revoke send permissions for a validated address.
- Remove IP from Allow Listdestructive
Tool to remove an ip address from your account's ip allow list. use after identifying the ip you wish to revoke.
- Remove SMTP Userdestructive
Tool to remove an smtp user from your account. use when you need to revoke smtp access for a user.
- Remove suppression entrydestructive
Tool to remove an email address or domain from the suppression list. use when you want to resume sending to the address or domain.
- Remove webhookdestructive
Tool to remove a webhook. use when you want to delete a webhook by its id from your smtp2go account.
- Search Email Activity
Tool to search activity events like sends, opens, clicks, and bounces. use when you need to filter account email activity by date, event, recipient, or message id.
- Search Email Templates
Tool to search your collection of email templates by id or name. use when you need to find templates matching specific criteria after authentication.
- Search SMTP2GO Emails
Tool to search sent emails. use when filtering your smtp2go account's email activity by criteria like date, sender, or recipient. call after authentication.
- Search Subaccounts
Tool to search subaccounts. use after authenticating to filter and paginate your subaccounts by name, email, or status.
- Subaccounts Usage
Tool to retrieve usage statistics for subaccounts. use when you need to monitor per-subaccount email usage.
- Update Allowed Sender
Tool to update details of an existing allowed sender. use after confirming the allowed sender id.
- View Allowed Senders
Tool to view the list of allowed senders configured in your account. use after setting up smtp2go authentication to retrieve your allowed-senders list. example: 'show me all verified allowed senders.'
- View Email Template
Tool to view details of a specific email template. use after you have the template id to inspect.
- View IP Allow List
Tool to view the list of ip addresses in your ip allow list. use after confirming your smtp2go api key is set.
- View Received SMS
Tool to retrieve received sms replies for your smtp2go account. use when you need to fetch incoming sms messages for analysis or display. pagination supported via limit and offset.
- View SMTP Users
Tool to list all smtp users configured on your account. use when you need to retrieve smtp user configurations.
- View Suppression List
Tool to view the suppression list. use when you need to inspect suppressed email addresses in your account.
- View Webhooks
Tool to view all webhooks configured in your account. use when you need to inspect existing webhook configurations after setup.
Setup
Setup guide
- 11. Log into your Smtp2go dashboard and navigate to Settings → API Keys. 2. Generate a new API key with full read/write permissions and copy it to your clipboard. 3. In Switchy, open any Space and type /connect, then select Smtp2go from the integrations list. 4. Paste your API key into the prompt and confirm. 5. Switchy validates the key by fetching your account stats — you'll see a success message if it works. 6. Test the connection by typing '@Smtp2go list smtp users' in the Space; you should see your current SMTP credentials returned inline. 7. From now on, @mention Smtp2go in any message to invoke its tools — the AI will route your request to the right endpoint and return results in the thread.
What teammates see: by default, memories from Smtp2go 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 Sender Domain
@Smtp2go add sender domain 'newsletter.acme.com' with tracking subdomain 'track' and return-path subdomain 'bounce'Open in a Space →
Provision SMTP User
@Smtp2go add smtp user with username 'staging-app' and password 'xK9mP2qL7n' restricted to sender 'app@acme.com'Open in a Space →
Check Suppression List
@Smtp2go list all entries in the suppression list and group them by reasonOpen in a Space →
Add Webhook for Bounces
@Smtp2go create webhook for bounce events posting to 'https://hooks.acme.com/smtp-bounces' with secret 'abc123'Open in a Space →
Whitelist New Sender
@Smtp2go add 'promo@acme.com' to the allowed senders list so we can send the holiday campaignOpen in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@smtp2go show me all active SMTP users and their sender restrictions for our production account
Here are your active SMTP users: 1. **prod-app-01** – Enabled, no sender restrictions (can send from any verified domain) 2. **marketing-team** – Enabled, restricted to @company.com and @newsletter.company.com 3. **support-bot** – Disabled, restricted to support@company.com All three users were created within the last 90 days. The marketing-team credential has the tightest sender scope, which reduces risk if the key leaks.
This example demonstrates read-only account inspection—useful for auditing who can send email and from which addresses. Requires an API key with read permissions. The MCP returns structured user data; the AI formats it for human review. No side effects.
@smtp2go add noreply@newproduct.company.com to our allowed senders and create an SMTP user called 'product-launch' with that restriction
Done. I've completed two actions: 1. Added **noreply@newproduct.company.com** to your allowed senders list (this address is now whitelisted for outbound mail). 2. Created SMTP user **product-launch** with sender restriction limited to noreply@newproduct.company.com. The password was auto-generated; you'll need to retrieve it from your Smtp2go dashboard or reset it. Before sending, ensure newproduct.company.com has SPF/DKIM records configured in Smtp2go, or deliverability will suffer.
This example chains two write operations—whitelisting a sender, then provisioning a credential. The MCP executes both but does not return the SMTP password in plaintext (security design). The user must fetch credentials separately. Requires API key with write scope.
@smtp2go review our suppression list and tell me if we're blocking any @vip-client.com addresses, then draft a policy for when to suppress versus when to retry
I checked your suppression list and found **3 addresses** from @vip-client.com: - bounce@vip-client.com (hard bounce, added 14 days ago) - old-contact@vip-client.com (unsubscribe, added 6 months ago) - test@vip-client.com (manual suppression, added yesterday) **Suggested suppression policy:** Suppress immediately for hard bounces and unsubscribes (legal requirement). For soft bounces or manual blocks, set a 30-day review window—especially for high-value domains—to catch stale entries before they hurt deliverability to valid contacts.
This example pairs the MCP's suppression-list read tool with the AI's reasoning to surface risk (blocking a VIP domain) and propose operational guardrails. The policy draft is AI-generated, not pulled from Smtp2go. Useful for compliance and deliverability hygiene.
Use-case deep-dives
When this MCP fits transactional email at 10-person scale
A 10-person SaaS team needs to send password resets, trial expiry warnings, and invoice receipts from their app. The Smtp2go MCP is the right call here because you can provision SMTP users per environment (staging, prod), manage sender domains for SPF/DKIM, and hook webhooks directly into your Slack channel for bounce alerts—all from the same AI workspace where you're debugging the email queue. The 32 tools cover the full lifecycle: add a sender domain, verify it, create an SMTP user, set up a webhook for delivery failures. If your volume crosses 50k emails per month or you need advanced segmentation, you'll outgrow this and want a dedicated email platform with better analytics. For early-stage teams sending under 10k transactional emails monthly, this MCP removes the context-switch tax of logging into a separate dashboard every time a customer reports a missing email.
When suppression list hygiene matters more than send volume
A 6-person support team at a B2B company uses Zendesk to reply to tickets, but they keep accidentally emailing ex-employees at customer orgs who've bounced or unsubscribed. The Smtp2go MCP solves this by letting the team add bounced addresses to the suppression list directly from their AI workspace during ticket triage—no separate login to the email provider. The 'Add to Suppression List' tool takes an email or entire domain, so when a customer says 'stop emailing old-team@client.com', you suppress it in 10 seconds. The webhook tool pipes bounce events into your support Slack channel so the team sees failures in real time. This setup works until you hit 100+ suppressions per week, at which point you need batch import tooling this MCP doesn't expose. For teams under 500 active customer contacts, the MCP keeps your sender reputation clean without adding another SaaS tab to your workflow.
When IP allowlisting blocks your agency's multi-client setup
A 4-person marketing agency runs email campaigns for 8 clients, each with their own sender domain and IP restrictions. The Smtp2go MCP is borderline here. It gives you 'Add IP Allow List' and 'Add Sender Domain' tools, so you can whitelist a new client's office IP or register their domain without leaving your AI workspace. That's useful when onboarding a client mid-sprint. But the MCP doesn't expose batch operations or campaign analytics—you're still logging into the Smtp2go dashboard to see open rates or segment sends. If your agency sends fewer than 5 campaigns per month and your bottleneck is the 20-minute setup tax per new client, this MCP cuts that to 2 minutes. If you're running daily sends or need A/B testing, the MCP won't replace your ESP; it just speeds up the boring provisioning work before the campaign goes live.
Frequently asked
What does the Smtp2go MCP do in Switchy?
It lets your AI agents manage your Smtp2go email infrastructure — add sender domains, create SMTP users, configure webhooks, edit templates, and maintain suppression lists. Instead of logging into Smtp2go's dashboard to whitelist a sender or provision credentials, your team can ask an agent to do it. Useful for ops teams who manage transactional email at scale.
Do I need admin access to connect Smtp2go?
You need an Smtp2go API key with write permissions. Smtp2go issues keys at the account level, so whoever connects it in Switchy should have authority to add domains, create SMTP users, and modify suppression lists. If your key is read-only, the MCP will fail on any write operation like adding a webhook or editing a template.
Can the MCP send individual emails through Smtp2go?
No. This MCP manages your Smtp2go account configuration — it doesn't send mail directly. To actually send emails, your application still calls Smtp2go's SMTP relay or API. Use this MCP to provision the sender domains and SMTP users your app needs, then point your app at those credentials to send.
How is this different from just using Smtp2go's API?
The API requires you to write code or scripts for every task. The MCP wraps 32 account-management endpoints so your team can ask an agent in plain English to add a sender, update a user, or check a suppression list. You skip the boilerplate and get the same result faster, especially for one-off ops tasks.
Who on the team should connect this MCP?
Whoever owns your transactional email stack — usually a backend engineer or DevOps lead. They already have Smtp2go credentials and understand sender reputation, SPF/DKIM, and suppression hygiene. Once connected, the rest of the team can ask agents to handle routine tasks like whitelisting a sender without needing API docs or admin access.