
SuprSend
io.github.suprsendPublished by GitHub account suprsendv1.0.1Updated Oct 24, 2026
Manage SuprSend entities — workflows, templates, users, objects, tenants — from your AI assistant.
The publisher's own server: SuprSend
Overview
Lets an assistant manage SuprSend notification workspace resources such as templates, workflows, schemas, events, and translations.
- What you can do
- SuprSend CLI doubles as an MCP server that exposes workspace operations over stdio, SSE, or HTTP. It covers resources including template, workflow, schema, event, category, translation, and workspace, each supporting list, get, pull, push, and commit against a local working directory. It can also sync assets between workspaces and generate typed payload code in several languages from event or workflow JSON Schemas.
- When to use it
- Use it when an assistant should read or change SuprSend notification content and configuration, or move assets between SuprSend workspaces, instead of editing them by hand in the dashboard.
- Requirements
- Runs locally as an npm package (npx suprsend start-mcp-server) and needs Node.js 18 or later; Homebrew and binary releases are also offered. A SuprSend service token is required via the SUPRSEND_SERVICE_TOKEN environment variable, created in the SuprSend dashboard under Developers, API Keys. SUPRSEND_BASE_URL and SUPRSEND_MGMNT_URL are only needed for BYOC or self-hosted instances.
Installation
In SourceWeft
- Open SuprSend in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
SuprSend CLI
SuprSend CLI is a command-line interface tool for interacting with the SuprSend API, written in Go. To connect AI agents (Claude, Cursor, VS Code, Gemini, etc.) to SuprSend, use the hosted SuprSend MCP server instead of the CLI.
What you can do with it
- Manage workspace resources —
template,workflow,schema,event,category,translation,workspace. Most supportlist,get,pull,pushandcommitagainst your local working directory (eventhas nocommit,categoryhas noget, andworkspaceonly haslist). - Sync between workspaces —
suprsend syncpulls assets from one workspace and pushes and commits them in another (changes go live in the destination), using a local directory (default./suprsend) as intermediate storage. - Generate typed payload code —
suprsend generate-typesemits typed code in Go, TypeScript, Python, Java, Kotlin, Swift, or Dart from your event / workflow JSON Schemas. - MCP server (deprecated) —
suprsend start-mcp-serverstill works but is deprecated. Use the hosted MCP server athttps://mcp.suprsend.com/mcp(for Claude Code:claude mcp add --transport http suprsend https://mcp.suprsend.com/mcp), or the suprsend/claude-plugin and suprsend/agent-plugin plugins. Gemini CLI: add"suprsend": {"httpUrl": "https://mcp.suprsend.com/mcp"}undermcpServersin~/.gemini/settings.json, then run/mcp auth suprsend(the Gemini CLI extension is retired). Keep usingstart-mcp-serveronly if you need service-token auth or a self-hosted (BYOC) instance. - Multi-account / multi-environment profiles —
suprsend profile add|modify|list|use|removestores per-account credentials and base URLs, so the same CLI works against public cloud, BYOC, staging, pre-prod, etc.
Full command reference: docs.suprsend.com/reference/cli-intro. Or run suprsend --help for the command tree.
Installation
npm / npx
Run without installing:
Or install globally:
Works on macOS, Linux, and Windows (x64 and arm64). Requires Node.js ≥ 18 (for npx).
Homebrew
You can install SuprSend CLI using Homebrew:
Binary Releases
Pre-compiled binaries for various platforms are available on the Releases page.
Building from Source
To build SuprSend CLI from source, follow these steps:
-
Ensure you have Go installed on your system (version 1.27.3 or later — see
go.mod). -
Clone the repository:
-
Build the binary:
-
The binary will be created in the current directory. You can move it to a location in your PATH for easy access:
Now you can use the suprsend command from anywhere in your terminal.
Usage
After installation, you can use the CLI by running the suprsend command. For example:
Documentation
Please refer to documentation here OR if you want to access the cobra generated docs those are here
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Generating build artifacts locally
make build compiles the embedded type-morph Deno binary (requires Deno), then generates CLI documentation in docs/ and AI skills in skills/.
A CI check on PRs to main verifies that docs/ and skills/ are up to date. Run make build and commit the output before opening a PR. Both are generated from the command definitions, so edit the command help text rather than the generated files.
Run the unit tests (after make build, which creates the embedded binary the packages compile against) with:
Removing local build artifacts
License
This project is licensed under the MIT License - see the LICENSE file for details.
Source: README.md at commit 4482b0d
Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts