Integrations, API & MCP
Connect SendOps without rewriting your sending code
Keep sending through Amazon SES exactly as you do today. SendOps connects to AWS, GitHub, Slack, and webhooks, with a Public API for your applications and a native MCP server for authorized AI agents.
The problem
Most email tools force an expensive, risky code migration.
Switching email vendors typically requires replacing your SDKs, modifying every sending endpoint, and trusting third-party relays with your application mail.
Building custom logging and alert infrastructure internally takes months of engineering work away from your core product.
SendOps connects directly to your existing Amazon SES account in 2 minutes, reading delivery events automatically without touching your sending code.
How it connects
Five integration points. Zero changes to your sending code.
SendOps connects to your AWS account, your Git repository, and the channels where your team works. Applications integrate through the Public API; AI clients use the native MCP server. Your application keeps sending through SES exactly the way it does today.
AWS SES
How it connects: A single CloudFormation template configures EventBridge rules that route every SES event — delivery, bounce, complaint, open, click — to SendOps automatically.
What flows: Event metadata — timestamps, statuses, engagement signals. The bodies of emails your application sends never pass through SendOps.
What you get: Real-time observability dashboard, message search, delivery metrics, alerting — all without writing a single CloudWatch query or Lambda function.
GitHub
How it connects: Connect your repository in the SendOps dashboard. SendOps watches for template changes on your branches.
What flows: Template source (React Email TSX, compiled to SES-native Handlebars on deploy) — and lists, segments, topics, and workflows, which can live as definitions in the same repo and sync the same way. SendOps validates, previews, and deploys on merge, reviews PR diffs on demand, and writes in-app edits back to your repo as pull requests.
What you get: Git-native template management. Pull requests, code review, rendered previews, automatic deployment. Marketing edits templates, engineering reviews — SendOps handles the rest.
Slack + Webhooks
How it connects: Add a Slack workspace or webhook URL in the SendOps dashboard. Choose which alerts go where.
What flows: Alert payloads — metric name, threshold, current value, affected domain or channel, and a link back to the SendOps dashboard.
What you get: Bounce rate spikes, complaint rate warnings, sending quota alerts, and domain verification events delivered to Slack, email, or any HTTP endpoint. Trigger PagerDuty, OpsGenie, or your own internal automation.
Public API
How it connects: Create an API key in the SendOps dashboard. API v1 is plain HTTPS and JSON — no SDK required.
What flows: Contacts, lists, audience definitions, activities, templates, workflows, broadcasts, reporting, message data, suppressions, and domain-authentication posture—subject to the scopes granted to the client.
What you get: Build backend integrations in ordinary HTTPS and JSON: synchronize customer data, record product activity, manage email operations, and read results without adopting a SendOps SDK.
MCP for AI agents
How it connects: Authorize an MCP-compatible client through OAuth 2.1. The client receives only the SendOps permissions you approve, scoped to your organization.
What it can do: Check sending readiness, inspect suppressions and deliverability, search and diagnose messages, preview audiences, manage contacts and lists, author templates and workflows, compose broadcasts, and review DMARC posture through native tools.
What stays controlled: Consequential actions require confirmation. A broadcast shows its audience before it sends, workflow activation shows the enrollment impact, and a git-backed template change opens a pull request for human review.
0
SDKs to install
0
Lines of application code to change
0
sSeconds from SES event to SendOps dashboard
0
AWS keys stored by SendOps
Privacy
Your data. Your account. Your call.
The email your application sends stays between your application and SES — SendOps observes event metadata, not message bodies. The data you bring to the platform — contacts, lists, segments, templates, assets — is stored scoped to your organization, exportable at any time, and deleted with your account. And every email, yours or SendOps-authored, goes out through your own SES.
What SendOps stores
- Delivery, bounce, complaint, open, and click event data
- Contacts, lists, and segments you create or import
- Template source and uploaded assets
- Consent, topics, and suppression state
What SendOps never touches
- The bodies of emails your application sends
- Your application databases
- Long-lived AWS credentials — access is via short-lived STS tokens
- Shared sending infrastructure — every send uses your SES
Agent-ready
A native integration surface for AI agents
Connect an MCP-compatible client and let it work with SendOps through tools designed for the job. It can inspect live sending health, investigate a message, preview an audience, maintain contacts and lists, author email assets, and prepare campaigns without scraping a dashboard or guessing at an API shape. OAuth scopes limit what the client can access, and SendOps preserves the same consent, suppression, approval, and audit controls used in the dashboard.
- Native MCP tools cover sending health, messages, audiences, templates, workflows, broadcasts, and DMARC
- OAuth 2.1 authorization keeps access scoped to the organization and permissions you approve
- Irreversible sends and consequential workflow activation require an explicit confirmation step
- Git-backed template changes become pull requests—reviewed and merged by a human before they are live
Integrations that match how each team works
SendOps meets each team where it already works: Git for developers, Slack and webhooks for operations, and a dashboard for marketing and support.
Developers
Templates and campaign definitions live in GitHub, backend systems use the Public API, and AI agents connect through the native MCP server. SendOps adds validation, previews, scoped permissions, and confirmation gates without changing how your application sends through SES.
Marketing
No AWS console or Git required. The SendOps dashboard covers template previews, audiences, broadcasts, and campaign performance end to end.
Operations
Alerts go to Slack, email, or webhooks. Every alert includes the metric, threshold, current value, and a direct link to the relevant dashboard view.
Connect your stack—and your agents—without changing how you send.
Free plan available. No sending SDK migration and no change to your SES delivery path.