SuprSend MCP server (Beta)

Connect SuprSend MCP to your AI clients (Claude, ChatGPT, Codex, Gemini and more) so your team can run notifications from the tools they already work in, without logging in to the SuprSend dashboard.

Overview

SuprSend MCP exposes your SuprSend workspace (users, objects, tenants, lists, workflows, templates, preferences, translations, vendors and delivery data) as tools that an AI client such as Claude, ChatGPT, Codex or Gemini can call over OAuth. From natural-language prompts, it reads delivery logs and analytics, debugs why a notification didn’t reach a user, edits workflows, templates and translations as drafts, updates user and tenant preferences, sends test notifications, and publishes the changes to production. You run the whole notification lifecycle without writing SQL, calling the API or opening the SuprSend dashboard.

Use SuprSend MCP when you want an AI client to read and change your notifications with your account permissions. It uses the role on your SuprSend account, the same one the dashboard uses, so the agent can’t do more than you can.

Sign in with your SuprSend account from any MCP-capable client, such as Claude Code, the Claude app, ChatGPT, VS Code, Codex, Gemini CLI or Windsurf. The server is hosted, so there is nothing to install.

How to connect

The SuprSend MCP server is at https://mcp.suprsend.com/mcp. One endpoint works for every workspace, regardless of its data region.

The setup is the same in every client:

1. Pick your URL

   Start from https://mcp.suprsend.com/mcp. To pin a workspace, add its slug: https://mcp.suprsend.com/mcp/staging. To limit the tools, add a tools filter: https://mcp.suprsend.com/mcp/staging?tools=users_*,data_* gives only the user and data tools. See Scope the connection.

2. Add it to your AI client

   Add the URL as a remote MCP server, or as a custom connector in apps like Claude and ChatGPT.

3. Sign in with SuprSend

   On first connect, your client opens a browser window. Sign in with your SuprSend account and approve access for the client.

4. Check the connection

   Ask the agent: “List my SuprSend workspaces.” It should answer with your SuprSend workspaces.

For the exact steps in your client:

Claude Code

Connect from the claude terminal client.

Claude Desktop & Claude.ai

Add a custom connector in the Claude app.

ChatGPT and Codex

Add a custom MCP server in ChatGPT, or run codex mcp add in Codex CLI.

Cursor

Add it to ~/.cursor/mcp.json.

VS Code + GitHub Copilot

Run MCP: Add Server and use it in Copilot Chat’s Agent mode.

Gemini CLI

Add it to ~/.gemini/settings.json.

Devin (Windsurf)

Add an MCP in Devin’s web app, or run devin mcp add in the Devin CLI.

More clients that support remote MCP servers:

Replit

Add a custom MCP server to Replit Agent.

Lovable

Add a custom MCP server as a chat connector.

Figma Make

Create a custom MCP connector. Needs a paid Figma plan.

Grok

Add a custom connector in Grok, or run grok mcp add in Grok Build.

Kiro

Add it to ~/.kiro/settings/mcp.json and run /mcp auth suprsend in Kiro CLI.

What you can do with MCP

Use SuprSend MCP for these jobs:

• Integrate SuprSend into your product. In a coding client like Claude Code or VS Code, the agent reads the SuprSend docs and your workspace’s workflows, events and payload schemas, then writes the code: install or upgrade an SDK, identify users, add the Inbox, or adopt a new SuprSend feature.
• Build and edit notifications. Describe the notification you need, and the agent creates the workflow and its templates for every channel, then adds the matching workflow trigger or event call to your codebase with a payload that fits the schema. Changes stay drafts until you publish them, so you can test first.
• Debug a missed notification. Ask why a user didn’t get a message. The agent loads the workflow run first and finds the step where it stopped, then checks the user’s profile, active channels, preferences and subscriptions, and the vendor routing. If your role allows it, the agent can also preview the message that was sent, with codes and link tokens masked.
• Query analytics and logs. Ask questions in plain words: how many quote-expiring emails were delivered last week by tenant, which workflows failed most this month, or which API calls returned errors today. The agent writes read-only SQL over your logs and, in clients that support MCP Apps, shows the answer as a chart or table.
• Manage assets and data. Create and update users, objects and tenants, set user and tenant preferences, build static or dynamic lists, and edit translations, preference categories and schemas. Add vendors, set the primary vendor and fallbacks for each channel, and upload images and PDFs to the SuprSend CDN.
• Test notifications. Validate workflows and templates, dry-run a send to check the payload without sending, run a draft workflow for test recipients, send a test of a template to one user, and evaluate Handlebars, JSONNET and jq expressions on sample data.
• Send and control live notifications. Trigger a workflow for up to 100 recipients, track an event, or broadcast a template to a list, now or on a schedule. Cancel a broadcast or a pending run, or turn a workflow off.

Don’t use SuprSend MCP for these jobs:

• Ongoing product notifications. Notifications your product sends as users act, such as sign-up, payment or quote-expiring messages, belong in your code. Set them up with the API or an SDK. A one-off campaign or broadcast is fine to run from MCP.
• Automation in CI/CD. For changes that run in a pipeline without a person, use the SuprSend CLI. To copy a few workflows or templates from one workspace to another, MCP works: connect to /mcp without a workspace slug and ask the agent to copy them. The copies land as drafts, so review them before you publish. For a full workspace sync, use the CLI’s sync.
• Keys and workspace setup. API keys, workspace keys and signing keys, and new workspaces, are managed in the SuprSend dashboard. The server has no tools for them, so these keys never reach the model.

What comes with the connection

Everything below comes from the server when you connect. You don’t install or configure anything.

Tools

Tools are named <group>_<action>, for example users_get or workflows_publish. The groups:

Group	What the tools cover
users, objects, tenants	Profiles, channels, subscriptions and preferences
lists, broadcasts	Static and dynamic lists, and broadcasts to them
workflows, events, schemas	Workflow drafts, publishing, runs, events and payload schemas
templates, translations	Template content for every channel, test sends and translations
preferences	Preference categories and their translations
vendors	Vendors and per-channel routing with fallbacks
data, messages	Read-only SQL over logs and analytics, and sent-message previews
assets, expressions	Uploads to the SuprSend CDN, and testing Handlebars, JSONNET and jq
workspaces, docs	Your workspaces, SuprSend docs search and skills

See the full tool list for every tool, whether it reads, writes or sends, and which ones need write access.

Agent skills

Skills are packaged SuprSend knowledge that the agent reads before it writes JSON or SQL, so it gets the format right the first time. The server serves four:

Skill	What it teaches the agent
suprsend-workflow-schema	Workflow JSON and every node type
suprsend-template-schema	Template variant JSON for every channel
suprsend-semantic-layer	The tables, columns and SQL rules for data_query
suprsend-docs-support	How to read the SuprSend docs and get help

Clients with the MCP Skills extension load them directly. Other clients get the same files through the docs_get_skill tool, and the server instructions tell the model to read the matching skill first.

MCP Apps

In clients that support MCP Apps, two tools show interactive results instead of plain text:

• data_query shows the answer as a chart (metric, line, bar, stacked bar or pie) or a table, with a Refresh button that runs the query again.
• messages_get_content shows a preview of a sent email, Inbox, SMS or push message, with images and links off and codes masked. Slack messages show as JSON with a link to Slack’s Block Kit Builder.

In other clients, the same tools return text.

Server instructions

A short text the client puts in the model’s context: what SuprSend is, which tools to use, and the rules for workspaces, sends and drafts. It names only the tools on your connection.

The server is built for MCP spec 2026-07-28. Clients built against the 2025 spec also connect.

Scope the connection

The URL you connect to decides which workspace and which tools the agent gets. Scope can only take access away. Your SuprSend role still applies on top of it.

URL	Workspace	Tools
/mcp	Every workspace in your account. The agent names one on each call.	All tools your role allows
/mcp/staging	Only staging	All tools your role allows
/mcp/staging?tools=users_*	Only staging	Only the users tools
/mcp?tools=users_*,lists_*	Every workspace in your account	Only the users and lists tools

Add the path and filter to the endpoint, for example https://mcp.suprsend.com/mcp/staging. One sign-in works on every URL of the same server.

• Pin a workspace. With a slug in the path, the tools lose their workspace input and the agent can’t switch to another workspace. If the slug doesn’t match a workspace in your account, the server refuses the connection with 403 workspace_forbidden.
• Filter the tools. ?tools= takes a comma-separated list of exact tool names (users_get) or groups (users_*). Any other pattern, or one that matches no tool, fails with 400 invalid_tools_filter.
• Watch what a group includes. A group brings its write and send tools with it: templates_* includes templates_publish and templates_send_test. For a read-only connection, list the read tools by name.

For example, this URL lets an agent debug delivery in production without changing anything:

https://mcp.suprsend.com/mcp/production?tools=data_*,users_find,users_get,users_get_preferences,workflows_list,workflows_get

The server instructions follow the scope. They name only the tools on the connection, and on a pinned URL they name only that workspace.

Security and privacy

Data access

• The agent gets the same permissions your role has in the SuprSend dashboard. The server checks this on every call, and tools your role can’t use don’t appear in the client.
• Sign-in uses OAuth. The access token works only for the SuprSend MCP server, not for the SuprSend dashboard or API.
• API keys, workspace keys and signing keys aren’t available through MCP. Codes and link tokens in sent messages are masked before the model sees them.

Limit access with roles and scope

In addition to role-based access, you can scope a connection further with its URL:

• Pin one workspace, for example /mcp/staging, so the agent can’t touch production.
• Add a tools filter to hide the tools a job doesn’t need.
• Tools outside your scope don’t appear in the client, and the server refuses them if called.

See Scope the connection for the URL patterns.

Guardrails on changes and sends

Tools that update data or send notifications are marked as such, so your AI client asks for your approval before they run. Only the server’s guardrails below hold in every client.

Enforced by	Guardrail	How strong
The SuprSend server	A dry run sends nothing. A retry of workflows_trigger with the same idempotency key within 24 hours sends nothing again. Draft changes don’t go live until publish.	Holds in every client
The model	The server’s instructions tell the model to call send tools only when you ask to send, and to use production only when you ask for it.	Depends on the model following them
Your AI client	Asks you to approve each update and send, based on the tool’s marks.	Depends on your client and its approval settings. Don’t auto-approve send tools.

Privacy considerations

The AI client you connect, and the model behind it, processes the SuprSend data that the tools return, such as user profiles and delivery logs. Check your AI provider’s data policies and your own compliance requirements before you connect a production workspace.

The model can misread a result or pick the wrong tool. Review what the agent plans to change or send before you approve it.

Tell us what’s missing

SuprSend MCP is still evolving, and your feedback decides what we build next. Two tools send it straight to the SuprSend team from your chat:

• get_more_tools reports a tool the agent needed but didn’t have. Ask: “Tell SuprSend you need a tool to clone a workflow.”
• send_feedback reports a problem, or something that worked well. Ask: “Send SuprSend feedback that the template preview cut off my email.”

The agent can also call them on its own when it gets stuck. Feedback goes to the SuprSend team, along with your account and workspace, but never the results of your tool calls.

Next steps

Quickstart

Connect to a staging workspace and walk the steps from read to test send.

Recipes

Prompts for debugging users, building workflows and checking delivery.

Reference

Tools, skills, MCP Apps and the server instructions.

Troubleshooting

Fix sign-in, scope and send errors.