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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago