Suprsend Mcp Server

Created By
SuprSend2 months ago
Manage your entire notification infrastructure using natural language. Trigger workflows, create users, manage preferences, update tenant branding, and access documentation — all from Cursor, Claude Desktop, or Windsurf. 24 tools across 4 categories covering email, SMS, push, WhatsApp, Slack, MS Teams, and in-app notifications. Zero context switching between your IDE and dashboard.
Overview

SuprSend MCP Server

SuprSend MCP Server lets you manage your entire notification infrastructure using natural language inside your AI coding tool.

What you can do

  • Trigger notification workflows
  • Create and update users
  • Manage notification preferences
  • Update tenant branding (logo, colors)
  • Access SuprSend documentation and code examples

Supported channels

Email, SMS, Push (mobile + web), WhatsApp, Slack, MS Teams, In-App

Supported AI tools

Cursor, Claude Desktop, Windsurf, Claude Code, any MCP-compatible client

Setup

Install SuprSend CLI via Homebrew: brew tap suprsend/tap && brew install --cask suprsend

Get your service token from SuprSend Dashboard → Account Settings → Service Tokens

Docs

https://docs.suprsend.com/reference/mcp-quickstart

Server Config

{
  "mcpServers": {
    "suprsend": {
      "command": "suprsend",
      "args": [
        "start-mcp-server"
      ],
      "env": {
        "SUPRSEND_SERVICE_TOKEN": "<YOUR_SERVICE_TOKEN>"
      }
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
SuprSend
Star
-
Language
-
License
-
Category

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago