SenderKit
Server Details
Build and send email, SMS, and push straight from your AI agent.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- senderkit/senderkit-skills
- GitHub Stars
- 1
- ChatGPT
- SenderKit
- Claude
- SenderKit
TDQS
Scored across 18 tools
The inbound_* namespace cleanly separates received-mail tools from general outbound messaging, and send vs send_raw are explicitly distinguished by template vs inline content. Minor potential confusion between messages_list (sent/scheduled) and inbound_messages_list (received), but prefixes keep them distinct.
Nearly all tools use snake_case with a resource_action pattern (templates_create, messages_get, inbound_domains_list) under a consistent senderkit_ prefix. A few outliers (send, send_raw, cancel_message, context) use verb-first or noun-only forms, a minor deviation.
At 18 tools the set is on the heavy side but each tool maps to a real operation across inboxes, domains, messages, and templates. It sits in the borderline 16-25 range rather than being clearly over-scoped.
Templates, messages, addresses, and domains each have list/create/get or cancel, but coverage is uneven: no template delete or update, no address/domain get or update, and no explicit publish/verify tool (publish is editor-only). Notable gaps an agent may hit.
Publisher details
- Operator
- SenderKit · Publisher source
- Operator website
- https://senderkit.com/
- Vendor relationship
- Not applicable
- Documentation
- https://docs.senderkit.com/
- Privacy policy
- Not provided
- Trust center
- https://www.senderkit.com/legal
- Restrictions
- Unknown
Available Tools
18 toolssenderkit_cancel_messageCancel Scheduled MessageADestructiveInspect
Cancel a still-pending message (scheduled or queued) by its public id.
Inputs: id (required), context (required). Returns: id, status
senderkit_contextGet Workspace ContextARead-onlyInspect
Returns the connected workspace (id, name, slug) and the send mode (live or test) for this connection. The mode is fixed for the whole connection: in live mode messages are really delivered; in test mode they are only recorded, without delivery.
Inputs: context (required). Returns: mode, workspace
senderkit_inbound_addresses_createCreate Inbound AddressAInspect
Create a new inbound email address that receives mail for the workspace and, optionally, forwards it and/or fires a webhook on receipt. Enforces the workspace's plan limit and validates forwardTo/webhookEndpointId.
Inputs: context (required), domainId, livemode, forwardTo, +3 more. Returns: id, active, address, livemode, +3 more
senderkit_inbound_addresses_deleteDelete Inbound AddressADestructiveInspect
Delete one of the workspace's inbound email addresses by id. The address immediately stops receiving new mail; already-received messages are unaffected.
Inputs: id (required), context (required). Returns: deleted
senderkit_inbound_addresses_listList Inbound AddressesARead-onlyInspect
List the workspace's programmatic inbound email addresses — the addresses that receive mail and forward it or fire a webhook into the workspace.
Inputs: context (required). Returns: data
senderkit_inbound_domains_createClaim Inbound DomainADestructiveInspect
Claim a custom domain for receiving mail (e.g. "inbound.acme.com"). Returns the DNS records (MX, DKIM) to publish at the domain's DNS host. If the domain already has live MX records pointing elsewhere, the call fails with an existing_mx error naming the current host(s); with acknowledgeExistingMx: true it claims the domain anyway, which redirects all of that domain's mail to SenderKit. Nothing is received until the records are live and verification completes.
Inputs: domain (required), context (required), acknowledgeExistingMx. Returns: id, kind, domain, status, +3 more
senderkit_inbound_domains_deleteDelete Inbound DomainADestructiveInspect
Delete a custom inbound domain by id. Its addresses stop receiving mail immediately. The workspace's shared {slug}.in.senderkit.email domain cannot be deleted.
Inputs: id (required), context (required). Returns: deleted
senderkit_inbound_domains_listList Inbound DomainsARead-onlyInspect
List the workspace's custom inbound domains — including the shared {slug}.in.senderkit.email domain, if used — with their verification status and (for pending custom domains) the DNS records still needed.
Inputs: context (required). Returns: domains
senderkit_inbound_messages_getGet Inbound MessageARead-onlyInspect
Fetch a single received inbound email message by id — envelope, headers, subject, body, attachments (as authenticated v1 API links — Bearer key with the inbound scope, not signed/presigned), and spam/auth verdicts.
Inputs: id (required), context (required). Returns: cc, id, to, from, +18 more
senderkit_inbound_messages_listList Inbound MessagesARead-onlyInspect
List received inbound email messages for the workspace's programmatic addresses, newest first. Filter by address or a receivedAt cursor — use this to check whether mail has arrived, or to page through recent receipts.
Inputs: context (required), limit, before, address. Returns: data
senderkit_messages_getGet MessageARead-onlyInspect
Fetch full details and delivery status for a single message by ID — check whether a specific email or SMS was delivered, bounced, or failed.
Inputs: id (required), context (required). Returns: vars, error, status, channel, +18 more
senderkit_messages_listList MessagesARead-onlyInspect
List sent and scheduled messages across email, SMS, push, and web-push. Filter by channel, template, delivery status, or metadata — use this to monitor deliverability, debug failed sends, or audit transactional message history.
Inputs: context (required), limit, cursor, search, +4 more. Returns: data, nextCursor
senderkit_sendSend Templated MessageADestructiveInspect
Send a transactional email, SMS, push, or web-push notification to a recipient using a saved template. This connection is bound to one mode: in test mode messages are recorded but not delivered; in live mode they are really sent. The result's mode field reports which one was used, and senderkit_context reports it before sending. Test mode can send draft (unpublished) templates for trial runs; live mode only sends templates with a published version.
Inputs: to (required), context (required), template (required), cc, +11 more. Returns: id, mode, status, livemode
senderkit_send_rawSend Raw MessageADestructiveInspect
Send a transactional email, SMS, push, or web-push notification with inline content, without a registered template. This connection is bound to one mode: in test mode messages are recorded but not delivered; in live mode they are really sent. The result's mode field reports which one was used, and senderkit_context reports it before sending.
Inputs: to (required), channel (required), context (required), cc, +21 more. Returns: id, mode, status, livemode
senderkit_templates_createCreate TemplateAInspect
Generate a new email, SMS, push, or web-push template from a plain-language brief and save it as a DRAFT. Returns a link to review it in the editor. Nothing is sent until the user reviews and publishes the draft.
Inputs: brief (required), channel (required), context (required), slug, +1 more. Returns: slug, status, message, editorUrl
senderkit_templates_getGet TemplateARead-onlyInspect
Look up a template by slug: its channel, status, and current version's number, publish time, and declared variables (fill these in vars when sending). Rendered content is not included.
Inputs: slug (required), context (required). Returns: slug, status, channel, updatedAt, +2 more
senderkit_templates_listList TemplatesARead-onlyInspect
List all message templates in the workspace across email, SMS, push, and web-push, with slugs and channels.
Inputs: context (required). Returns: data
senderkit_templates_regenerateRegenerate Template DraftADestructiveInspect
Regenerate an existing DRAFT template from a new brief. This replaces the draft's content and discards any manual edits made in the editor. Only drafts can be regenerated; published templates are left untouched.
Inputs: slug (required), brief (required), context (required). Returns: slug, status, message, editorUrl
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Email, WhatsApp and Telegram for AI agents: send, campaigns, automations, contacts, agent inboxes.
Send email, run broadcasts and automations, and answer your inbox from any AI agent.
Design on-brand emails with your AI, preview them in chat, and send through server-side guardrails.
Email and SMS inboxes for AI agents, plus email rendering, inbox placement and sender warmup.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to send prioritized notifications through SMS, Telegram, email, Slack, Discord, phone push, and webhooks, with routing rules, quiet hours, and per-agent limits.1MIT
- AlicenseAqualityCmaintenanceLets AI agents send notifications, manage templates and read delivery status.129 npmMIT

SendKuy MCP serverofficial
AlicenseAqualityBmaintenanceEnables AI assistants and agents to send WhatsApp, SMS, and email messages, verify OTP codes, and run campaigns through an account-based messaging platform.81759 npm1MIT- AlicenseNot gradedqualityDmaintenanceLet your AI agent notify you via email, Slack, Discord, or webhook using a single tool.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.