documentation.searchLABSCO SUMMARY
The preference hierarchy is the part worth having a tool for.
Category defaults, tenant overrides and user choices interact in ways that are painful to reason about from a dashboard, and here you can read all three levels and find where a notification is being suppressed. The --tools flag matters for the same reason the write tools do: point it at a production workspace with a read-only subset rather than the whole surface.
What it is
A notification-infrastructure CLI that also runs as an MCP server. It exposes workflows, users, tenants, objects and preferences as tools, so an assistant can set up and debug notification delivery without the dashboard or hand-written API wrappers.
What you get
- workflows.list, workflows.get, workflows.create, workflows.update — the workflows behind your notifications, with channels, steps and routing
- workflows.trigger — fire a workflow for one or more recipients
- users.get and users.upsert — a user's profile, channel addresses and properties
- users.get_preferences, users.update_preferences, users.update_channel_preference — per-category preferences and global channel restrictions
- users.get_list_subscriptions and users.get_objects_subscriptions — what a user is subscribed to
- tenants.get, tenants.get_all, tenants.upsert — tenant configuration, branding and properties
- tenants.get_preferences and tenants.update_preferences — tenant-level preference defaults and overrides
- objects.get, objects.upsert, objects.get_preferences, objects.update_preferences, objects.update_channel_preference — the same model for objects
- documentation.search and documentation.fetch — search the product documentation and read a page
- A --tools flag that restricts which tools are exposed, accepting names or a wildcard per category
Requirements
A SuprSend workspace service token in SUPRSEND_SERVICE_TOKEN, created in the dashboard under Developers and API Keys. The server runs locally from the CLI — clients launch it with npx and the start-mcp-server subcommand, which needs Node.js 18 or higher. Self-hosted and bring-your-own-cloud instances set SUPRSEND_BASE_URL and SUPRSEND_MGMNT_URL as well.
Setup effort
One command plus a key — npx -y suprsend start-mcp-server, then supply credentials
USE CASES
01
Debugging "they never got the notification"
Read the user's profile and channel addresses, then check the preference at user, tenant and object level to find where it was suppressed.
02
Setting up a new tenant
Create the tenant with its branding, then set the category defaults it should start with.
03
Building a notification flow
Create the workflow with its channels and steps, then trigger it against a test recipient.
04
Seeding test data
Upsert users with channel addresses and subscribe them to objects so they inherit the right preferences.
05
Looking something up without leaving the editor
Search the documentation and read the page that answers it.
06
Restricting what a production workspace exposes
Start the server with only the read tools enabled, using names or a category wildcard.
24 tools
Listed in project docs. Your client may show a different list.
documentation.fetchusers.getusers.upsertusers.get_preferencesusers.update_preferencesusers.update_channel_preferenceusers.get_list_subscriptionsusers.get_objects_subscriptionstenants.gettenants.get_alltenants.upserttenants.get_preferencestenants.update_preferencesobjects.getobjects.upsertobjects.get_preferencesobjects.update_preferencesobjects.update_channel_preferenceworkflows.listworkflows.getworkflows.createworkflows.updateworkflows.triggerBEFORE YOU INSTALL
What to know first
Tools you get
24 tools named in the project's documentation. --events and --workflows each add one trigger tool per enabled event or workflow, and --tools can restrict the set. suprsend start-mcp-server list-tools prints what your configuration exposes.
Requires
SUPRSEND_SERVICE_TOKEN in your environment
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
Setup
TERMINAL
npm i -g suprsendOr brew tap suprsend/tap && brew install --cask suprsend, or download a binary release.
Generate a Service Token in the SuprSend dashboard
Add the mcpServers block to your client's mcp.json with SUPRSEND_SERVICE_TOKEN set
npx
TERMINAL
npx -y suprsend start-mcp-serverMCP Clients
Cursor, Claude Desktop, Windsurf
JSON
{
"mcpServers": {
"suprsend": {
"command": "npx",
"args": [
"-y",
"suprsend",
"start-mcp-server"
],
"env": {
"SUPRSEND_SERVICE_TOKEN": "<YOUR_SUPRSEND_SERVICE_TOKEN>"
}
}
}
}
