@sendbyte/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| 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. | https://api.sendbyte.africa |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| get_emailA | Fetch one email by id, including its delivery status and event timeline (queued, sent, delivered, bounced, complained). |
| list_emailsA | List recent emails for the project, newest first, with cursor pagination. Optionally filter by delivery status. |
| list_domainsA | List the sending domains on the account with their verification status and whether deliverability (SPF/DMARC/MAIL FROM) is fully configured. |
| get_domainA | Get one sending domain by id, including the DNS records to publish (DKIM, SPF, DMARC, MAIL FROM) and their current state. |
| verify_domainA | Re-check a domain's DNS records and SES status now, and report which records pass and whether the domain is verified. |
| list_templatesA | List saved email templates for the project (id, name, subject, format, version). |
| get_templateA | Get one saved template by id, including its subject and body (html/text/mjml). |
| preview_templateA | Render a saved template with sample variables and return the resolved subject and body, without sending anything. |
| get_analyticsA | Get daily send counts by status and deliverability rates (delivered, bounce, complaint) over the last N days. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
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.
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.
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.
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.