SuprSend MCP Server
# SuprSend CLI
[](https://glama.ai/mcp/servers/suprsend/cli)
SuprSend CLI is a command-line interface tool for interacting with the SuprSend API, written in Go. It also doubles as an MCP server so AI agents (Claude, Cursor, Gemini, etc.) can drive your workspace through the same set of operations.
## What you can do with it
- **Manage workspace resources** — `template`, `workflow`, `schema`, `event`, `category`, `translation`, `workspace`. Each supports `list`, `get`, `pull`, `push`, `commit` against your local working directory.
- **Sync between workspaces** — `suprsend sync` pulls assets from one workspace and pushes to another, with an optional local directory as intermediate storage.
- **Generate typed payload code** — `suprsend generate-types` emits typed code in Go, TypeScript, Python, Java, Kotlin, Swift, or Dart from your event / workflow JSON Schemas.
- **Run as an MCP server** — `suprsend start-mcp-server` exposes tools over stdio/SSE/HTTP. Installable directly from the [MCP Registry](https://modelcontextprotocol.io/registry) (`npx -y suprsend start-mcp-server`), or wire it into Claude Code / Cursor / Gemini CLI manually.
- **Multi-account / multi-environment profiles** — `suprsend profile add|modify|list|use|remove` stores 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](https://docs.suprsend.com/reference/cli-intro). Or run `suprsend --help` for the command tree.
## Installation
### npm / npx
Run without installing:
```bash
npx suprsend --help
```
Or install globally:
```bash
npm i -g suprsend
suprsend --help
```
Works on macOS, Linux, and Windows (x64 and arm64). Requires Node.js ≥ 18 (for `npx`).
### Homebrew
You can install SuprSend CLI using Homebrew:
```bash
brew tap suprsend/tap
brew install --cask suprsend
```
### Binary Releases
Pre-compiled binaries for various platforms are available on the [Releases page](https://github.com/suprsend/cli/releases).
### Building from Source
To build SuprSend CLI from source, follow these steps:
1. Ensure you have Go installed on your system (version 1.25 or later — see `go.mod`).
2. Clone the repository:
```bash
git clone https://github.com/suprsend/cli.git
cd cli/cmd/suprsend
```
3. Build the binary:
```bash
go build -o suprsend
```
4. The binary will be created in the current directory. You can move it to a location in your PATH for easy access:
```bash
sudo mv suprsend /usr/local/bin/
```
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:
```bash
suprsend --help
```
## Documentation
Please refer to documentation [here](https://docs.suprsend.com/reference/cli-intro) OR if you want to access the cobra generated docs those are [here](docs/suprsend.md)
## 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](https://deno.land/)), then generates CLI documentation in `docs/` and AI skills in `skills/`.
```bash
make build
```
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.
### Removing local build artifacts
```bash
make clean
```
## License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
TDQS
Scored across 22 tools
Each tool targets a distinct resource-action pair, and the descriptions include explicit
The vast majority of tools follow a clear snake_case verb_suprsend_entity pattern (upsert_suprsend_user, get_suprsend_object_preferences). There are minor irregularities such as list_workflows and get_tenant_default_preference missing the suprsend prefix, and update_suprsend_users_preferences is awkwardly plural.
With 22 tools, the set falls into the borderline-heavy range. Many tools are individually justified by the breadth of the domain, but the preference and subscription families alone account for a large number of similar-purpose tools.
The server covers core reads, upserts, preference management, and subscription listing/creation across users, objects, and tenants. It has notable gaps: no remove/delete tools for subscriptions, users, or objects, no workflow create/update/trigger tools, and no way to actually send a notification, which means several real-world workflows hit dead ends.