How do I use @sendbyte/mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@@sendbyte/mcp Send email to user@example.com: Subject 'Welcome', body 'Hello!'" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

@sendbyte/mcp

Official

by Sendbyte-Africa

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

@sendbyte/mcp

The official SendByte MCP server. It lets AI agents and coding tools (Claude Desktop, Claude Code, Cursor, Continue, and any Model Context Protocol client) send email and manage sending domains, templates, analytics, and content checks through your SendByte account.

It speaks MCP over stdio and authenticates with your own SendByte API key.

Quick start

You need a SendByte API key. Create one in the dashboard under API keys (use a sk_test_ key while you experiment; it sandboxes every send).

No global install is needed. Point your MCP client at npx @sendbyte/mcp and set SENDBYTE_API_KEY in its environment.

Claude Desktop

Edit claude_desktop_config.json (Settings, Developer, Edit Config):

{
  "mcpServers": {
    "sendbyte": {
      "command": "npx",
      "args": ["-y", "@sendbyte/mcp"],
      "env": { "SENDBYTE_API_KEY": "sk_test_your_key_here" }
    }
  }
}

Claude Code

claude mcp add sendbyte --env SENDBYTE_API_KEY=sk_test_your_key_here -- npx -y @sendbyte/mcp

Cursor

Add to ~/.cursor/mcp.json (or a project .cursor/mcp.json):

{
  "mcpServers": {
    "sendbyte": {
      "command": "npx",
      "args": ["-y", "@sendbyte/mcp"],
      "env": { "SENDBYTE_API_KEY": "sk_test_your_key_here" }
    }
  }
}

Continue

In ~/.continue/config.json:

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": ["-y", "@sendbyte/mcp"],
          "env": { "SENDBYTE_API_KEY": "sk_test_your_key_here" }
        }
      }
    ]
  }
}

Related MCP server: Email Alert MCP Server

Configuration

Variable	Required	Description
`SENDBYTE_API_KEY`	yes	An `sk_live_` or `sk_test_` key from the dashboard. A test key sandboxes every send.
`SENDBYTE_BASE_URL`	no	Override the API host for self-hosted, staging, or local development. Defaults to `https://api.sendbyte.africa`.

Tools

Tool	What it does
`send_email`	Send a transactional email (inline html/text, or a saved template with variables).
`get_email`	Fetch one email by id with its delivery status and event timeline.
`list_emails`	List recent emails, newest first, with optional status filter and cursor paging.
`list_domains`	List sending domains with verification and deliverability state.
`get_domain`	Get one domain with the DNS records to publish and their current state.
`verify_domain`	Re-check a domain's DNS and SES status now.
`list_templates`	List saved templates.
`get_template`	Get one template's subject and body.
`preview_template`	Render a saved template with sample variables, without sending.
`get_analytics`	Daily send counts by status and deliverability rates over the last N days.
`scan_content`	Pre-send spam-risk check returning a score, level, and the signals found.

Notes

A sk_test_ key sandboxes sends, so an agent can exercise send_email safely. Switch to sk_live_ only when you want real delivery.
The sender domain on send_email must be a verified sending domain on your account (or the shared test domain when using a test key).
The server writes only to stderr; stdout is reserved for the MCP protocol.

License

MIT

Available Tools

11 tools

get_analyticsA

Get daily send counts by status and deliverability rates (delivered, bounce, complaint) over the last N days.

Inputs: days.

get_domainA

Get one sending domain by id, including the DNS records to publish (DKIM, SPF, DMARC, MAIL FROM) and their current state.

Inputs: id (required).

get_emailA

Fetch one email by id, including its delivery status and event timeline (queued, sent, delivered, bounced, complained).

Inputs: id (required).

get_templateA

Get one saved template by id, including its subject and body (html/text/mjml).

Inputs: id (required).

list_domainsA

List the sending domains on the account with their verification status and whether deliverability (SPF/DMARC/MAIL FROM) is fully configured.

Inputs: no named parameters.

list_emailsA

List recent emails for the project, newest first, with cursor pagination. Optionally filter by delivery status.

Inputs: limit, after, status.

list_templatesA

List saved email templates for the project (id, name, subject, format, version).

Inputs: no named parameters.

preview_templateA

Render a saved template with sample variables and return the resolved subject and body, without sending anything.

Inputs: id (required), variables.

scan_contentA

Pre-send deliverability and spam-risk check for email content. Returns a score, risk level, and the specific signals found, so an agent can fix risky content before sending.

Inputs: subject, html, text, from.

send_emailA

Send a transactional email through SendByte. The sender domain must be a verified sending domain (or use the shared test domain with a test key). Provide html and/or text, or a template_id with variables. A test key (sk_test_) sandboxes the send.

Inputs: from (required), to (required), subject (required), html, +8 more.

verify_domainA

Re-check a domain's DNS records and SES status now, and report which records pass and whether the domain is verified.

Inputs: id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored 2026-06-22 18:36 across 11 tools

Disambiguation5/5

Each tool targets a distinct resource and action: analytics, domains, emails, templates, content scanning, sending, and verification. There is no overlap; for instance, get_domain retrieves a single domain while list_domains enumerates them, and preview_template differs from get_template by rendering with variables without sending.

Naming Consistency5/5

All tool names use a consistent verb_noun pattern in snake_case, with verbs like get, list, preview, scan, send, verify. No mixing of conventions, making the set predictable.

Tool Count5/5

11 tools is well-scoped for an email service, covering domain management, template handling, email retrieval, content scanning, sending, and analytics. Not too few or too many.

Completeness4/5

The tool surface covers the main workflows: sending emails, checking content, managing domains (list, get, verify) and templates (list, get, preview), and viewing analytics. Missing are create/update/delete for domains and templates, but these may be out of scope for the MCP server's intended purpose.

Maintenance

ActivitySlowing

ResponsivenessNo recent community issues

Resources

Related MCP Connectors

Emitd MCP ServerA
com.emitd
Connect AI agents to Emitd email sending, message tracking, templates, and automations. Emitd hosts a Model Context Protocol server for integrating supported email operations into AI-agent workflows. Connect a compatible client to the hosted endpoint (https://mcp.emitd.com/mcp) and authenticate with an Emitd API key. Available tools depend on the key's permissions and enabled features. Emitd's capability areas include sending email, message activity, templates, contacts, audiences, segments, domains, analytics, inbound email, broadcasts, automations, webhooks, and suppressions. Use restricted keys, sending guardrails, and approval settings appropriate to each workflow. For more information check https://emitd.com
Agent Orchestration Email
41
https://mcp.emitd.com/mcp
SendPanda
io.github.TheBugEater
Send email, manage domains, templates, webhooks and broadcasts from your AI agent.
Email Marketing
1
https://api.sendpanda.email/mcp
emailA
dev.primitive
Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.
Email Communication
142
https://www.primitive.dev/mcp
AISend
app.aisend
Email for AI agents: send from your verified domain, track delivery, list mail, validate addresses.
Email Communication
1
https://api.aisend.app/mcp

Related MCP Servers

Gmail MCP Server
Email Communication
TechVest-Global
F
license
Not graded
quality
D
maintenance
Enables AI agents to manage Gmail through natural language, including search, read, send, label, and draft operations via the Model Context Protocol.
Updated a year ago (2025-12-16 12:19 UTC)
-
Email Alert MCP Server
Email Communication
tejaskumbhar288
F
license
Not graded
quality
D
maintenance
Enables AI agents to read, filter, send emails, and check unread counts via the Model Context Protocol using Gmail SMTP/IMAP.
Updated a year ago (2025-11-02 07:28 UTC)
-
Tratto MCP Serverofficial
Email Communication
tratto-email
A
license
A
quality
D
maintenance
Lets AI tools send transactional emails, check status, and manage contacts through the Model Context Protocol.
Updated 5 months ago (2026-06-24 08:43 UTC)
2
MIT
MuntuAI MCP
Email App Automation
design-smith
F
license
Not graded
quality
D
maintenance
Enables AI agents to programmatically manage email outreach campaigns, leads, domains, senders, and webhook events, as well as send emails, through the Model Context Protocol over HTTP.
Updated 5 months ago (2026-06-25 02:17 UTC)
-

@sendbyte/mcp

Quick start

Claude Desktop

Claude Code

Cursor

Continue

Configuration

Tools

Notes

License

Available Tools

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Gmail MCP Server

Email Alert MCP Server

Tratto MCP Serverofficial

MuntuAI MCP