We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

SuprSend

MCP server by SuprSend

Manage SuprSend notification users, lists, workflows and templates from your AI assistant.

OAuth sign-in (You sign in with the vendor the first time you connect)Streamable HTTP

Connect to SuprSend

SuprSend needs sign-in. Connect with its own URL:

https://mcp.suprsend.com/mcp

Your client opens SuprSend’s sign-in the first time you use it. The token stays between your client and SuprSend.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/suprsend

About

Connects an MCP client to SuprSend, a notification infrastructure platform for email, SMS, push, Slack and in-app inbox. The hosted server exposes users, lists, workflows, templates and notification data.

It runs as a hosted streamable HTTP endpoint at https://mcp.suprsend.com/mcp. Access needs SuprSend credentials; the endpoint refuses anonymous requests.

What you can do

  • Work with SuprSend users and lists
  • Inspect and manage notification workflows
  • Work with notification templates
  • Read notification data

Tools

SuprSend lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.

Example prompts

  • List the workflows in my SuprSend workspace.

  • Show the notification templates used by my onboarding workflow.

  • Find the SuprSend user with ID user_123 and show their details.

  • Which lists do I have in SuprSend?

Set up

Every client connects to mcp.suprsend.com, and SuprSend asks you to sign in the first time. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http suprsend https://mcp.suprsend.com/mcp
  1. Start Claude Code, type /mcp, pick suprsend and choose Authenticate. A browser window opens for the SuprSend sign-in.

Add --scope user to make it available in every project, not just this one.

Claude Desktop

  1. Open Customize → Connectors, click + Add, then Add custom connector.
  2. Name it SuprSend and paste this URL:
https://mcp.suprsend.com/mcp
  1. Click Add, then Connect, and sign in when SuprSend asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

claude.ai

  1. Open the connector form on claude.ai. This button fills in the name and URL for you:
  1. Check that the URL reads https://mcp.suprsend.com/mcp and click Add.
  2. Click Connect and sign in when SuprSend asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under Organization settings → Connectors.

ChatGPT

  1. On chatgpt.com, go to Plugins, select +, then Add custom MCP server.
  2. Enter a name for the server.
  3. Under Connection, paste https://mcp.suprsend.com/mcp as the server URL, then for authentication choose OAuth. ChatGPT sends you to SuprSend to sign in.
  4. Check I understand and want to continue, then select Create as a plugin.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "suprsend": {
      "url": "https://mcp.suprsend.com/mcp"
    }
  }
}

Cursor shows Needs authentication next to the server. Click the button beside it to sign in.

VS Code

Or from a terminal:

code --add-mcp '{"name":"suprsend","type":"http","url":"https://mcp.suprsend.com/mcp"}'

Or commit it to the repo in .vscode/mcp.json:

.vscode/mcp.json
{
  "servers": {
    "suprsend": {
      "type": "http",
      "url": "https://mcp.suprsend.com/mcp"
    }
  }
}

VS Code asks you to sign in the first time the server starts.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "suprsend": {
      "serverUrl": "https://mcp.suprsend.com/mcp"
    }
  }
}
  1. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads serverUrl (or url) for remote servers.

Codex

codex mcp add suprsend --url https://mcp.suprsend.com/mcp
codex mcp login suprsend

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.suprsend]
url = "https://mcp.suprsend.com/mcp"

Gemini CLI

gemini mcp add --transport http suprsend https://mcp.suprsend.com/mcp

Then, inside Gemini CLI, run /mcp auth suprsend to sign in.

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients accept this shape. Some name the URL field differently: serverUrl in Devin Desktop, httpUrl in Gemini CLI’s settings file.

{
  "mcpServers": {
    "suprsend": {
      "type": "http",
      "url": "https://mcp.suprsend.com/mcp"
    }
  }
}

Zed puts servers under context_servers in its settings. Cline needs "type": "streamableHttp", or it assumes SSE.

Client only starts local servers? Bridge it with npx -y mcp-remote https://mcp.suprsend.com/mcp.

Embed

Show SuprSend in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![SuprSend on mcp.tc](https://mcp.tc/i/suprsend/badge.svg)](https://mcp.tc/i/suprsend)
HTML
<a href="https://mcp.tc/i/suprsend"><img src="https://mcp.tc/i/suprsend/badge.svg" alt="SuprSend on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/suprsend.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/suprsend" title="SuprSend on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/suprsend.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the SuprSend card to your site.

Markdown
Add the mcp.tc card for SuprSend, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/suprsend.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="suprsend"><a href="https://mcp.tc/i/suprsend">SuprSend on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![SuprSend on mcp.tc](https://mcp.tc/i/suprsend/badge.svg)](https://mcp.tc/i/suprsend)
```

Reference: https://mcp.tc/embed

Change history

Its tools are behind a sign-in, so we can’t read them. Edits by its owner show up here.

Follow SuprSend and we’ll email you when something changes.

Nothing recorded yet. Edits by the server’s owner will show up here.

FAQ

Can I paste mcp.tc/i/suprsend into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://mcp.suprsend.com/mcp, so your client talks to SuprSend directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does SuprSend need an API key or a sign-in?

Yes, you need a SuprSend account. The first time your client connects, it opens SuprSend’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.

Is SuprSend a remote or a local server?

Remote. SuprSend hosts it at https://mcp.suprsend.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can SuprSend do?

You can work with SuprSend users and lists, inspect and manage notification workflows and work with notification templates.

Which clients can use it?

Remote MCP clients that sign in with OAuth, as long as they are registered with SuprSend in advance or identify themselves with a Client ID Metadata Document (CIMD): SuprSend doesn’t offer open Dynamic Client Registration. Check SuprSend’s own setup guide for your client.

Does mcp.tc track changes to SuprSend?

Partly. SuprSend’s tools are behind a sign-in, so its History tab shows only edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read SuprSend’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with SuprSend. This page was built from SuprSend’s public metadata, last checked on 18 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.