Today we're launching the SuprSend MCP server.
SuprSend's full notification stack, workflows, templates, tenants, preferences, channel orchestration, is now callable directly from Cursor, Claude, Windsurf, or any MCP client. You describe what you need; the AI builds it.
What it takes to ship real notifications
Sending an email from your code is easy.
But building a notification system that handles multiple channels, user preferences, multi-tenant branding, retries, deliverability, batching, and analytics is not. Most teams underestimate the gap, ship a quick integration, and then spend the next year maintaining a system that was never meant to scale.
The infrastructure itself was never the hard part. SuprSend already has the primitives – workflows, templates, tenants, preferences, objects, channel orchestration, tested at scale across thousands of customer setups. What cost teams weeks was the integration layer: mapping your product's events, users, and tenants onto those primitives, by hand, against the docs.
That layer is exactly what AI agents are now good at – and the reason it works is that the industry quietly standardized on how they connect. In under two years, MCP went from an Anthropic experiment to a vendor-neutral protocol governed by the Linux Foundation, adopted across every major AI client and thousands of production systems. It stopped being a bet and became infrastructure. SuprSend speaks it natively, so the integration that used to take weeks now ships in an afternoon.
Notifications, from a prompt
SuprSend MCP is a Model Context Protocol server that exposes SuprSend's full notification stack to your AI client. Run one command, connect Cursor, Claude, Windsurf or any other Agent harnesses and start prompting.
The AI reads SuprSend's actual schemas, calls the right tools, builds your workflows and templates, and generates the SDK trigger code that fits your codebase. The integration that used to take a week ships in an afternoon.
How the AI works with SuprSend
The MCP server exposes SuprSend's primitives as typed tools. Workflows, templates, users, tenants, preferences, objects, and delivery logs are all callable with validated schemas.
Three things make the generated code correct on the first run.
Skills load SuprSend domain context into the AI.
Skills are instruction packages that cover SuprSend's workflow shapes, preference cascade rules, channel configurations, and integration patterns. Without skills, the AI knows the protocol but not the product. With skills, it generates code that matches how SuprSend is actually used in production.
Schema validation happens before every call.
Every tool invocation is validated against SuprSend's real schemas. Hallucinated endpoints and malformed payloads fail at the schema layer, not at runtime.
Read-before-write protects your existing setup.
Update tools fetch the current state of a resource before modifying it, so the AI works with a delta instead of an overwrite. Editing a workflow or template never wipes config you already had in place.
.png)
Build for any use case
The same MCP server handles the full lifecycle — wiring SuprSend into your product, creating workflows and templates, setting up test data, and debugging what's already live.
Integrate SuprSend into your product
- Integrate SuprSend SDK Integration with a simple prompt in your codebase
- Add the in-app inbox or preference center to your app
- Setup up workflow or event triggers on product actions where you want to send notifications
- Map customer tenants to SuprSend tenants and sync them from codebase
- Add user identification call when user logs in or signs upMigrate templates from internal codebase or external tools
Setup your account and create test data
- Create a workflow for a product event — define the channels, steps, and routing from a description of when it should fire
- Generate templates for a workflow across channels (email, SMS, push, in-app) with consistent content and branding
- Configure a preference hierarchy: set category defaults, apply tenant-level overrides, then layer in user choices
- Seed test users with channel addresses, then subscribe them to objects so they inherit the right preferences
Query and debug
- User id 583 says they never got the notification — show me their available channels, and preferences
- How did the workflow do this week — sent, delivered, failed?
- How many users opted out of the newsletter category?
- Check what an error means and how to fix it
- Pull up a workflow to verify if it’s active and inspect its configuration
"We plugged SuprSend into Claude Code and forgot it was a separate product. Shipping notifications now feels as fast as shipping code. What used to take hours now takes minutes. This is the new standard"
Dinesh Singh, Co-Founder & CTO, Topmate
Add in-app inbox, check for user data, notification data, create events, create preferences wired into your product through simple prompting. Production controls hold throughout, scoped service tokens, the --tools flag for read-only environments in production, and no bulk deletes through AI.
Learn more about all the MCP tools
Read the docs to set up your first MCP session
