Model Context Protocol

Email tools your agent can safely call.

The MCP server wraps tinysend’s scoped API. Give an agent only the domain and operations it needs. Every write still uses the same validation, suppression, idempotency, and audit boundaries as the dashboard.

Install

{
  "mcpServers": {
    "tinysend": {
      "command": "npx",
      "args": ["-y", "tinysend-mcp"],
      "env": {
        "TINYSEND_API_KEY": "ts_your_scoped_key",
        "TINYSEND_API_URL": "https://your-tinysend.example"
      }
    }
  }
}

For self-hosting, set TINYSEND_API_URL to your deployment. Keep the API key in the agent host’s secret store.

Available tools

send_email

Queue one transactional email with a template or inline content.

Scope: emails:send

send_batch

Queue up to 100 independent transactional messages.

Scope: emails:send

sync_contacts

Create or update users and their product attributes.

Scope: contacts:write

list_templates

Read the current version of every template.

Scope: templates:read

create_template

Create a reusable, versioned email template.

Scope: templates:write

list_broadcasts

Inspect broadcast status and recipient progress.

Scope: broadcasts:read

create_broadcast

Create a draft, immediate, or scheduled broadcast.

Scope: broadcasts:write

send_broadcast

Explicitly release an existing draft to subscribed contacts.

Scope: broadcasts:write

list_domains

List sending identities available to this key.

Scope: domains:read

check_domain_status

Inspect SES verification and DNS requirements.

Scope: domains:read

get_stats

Read 30-day delivery and engagement health.

Scope: emails:read

Narrow keys

Restrict a key to one sending domain and explicit capabilities.

Idempotent sends

Agents can retry a stable business action without sending twice.

Same guardrails

Suppression, domain verification, and recipient rules cannot be bypassed by MCP.