senderkit-mcp-messaging-operationslisted

Send and operate transactional messages — email, SMS, push, or web-push — at runtime through the connected SenderKit MCP server. Use whenever the SenderKit MCP tools (senderkit_*) are available and a user wants to actually send a message (a test or live send, a welcome/OTP/notification message), check delivery or message status, debug a failed or stuck send, look up/draft/regenerate templates, filter recent messages, check scheduled sends, or cancel a scheduled or queued message — rather than editing application code (that is the senderkit-integration skill).
senderkit/senderkit-skills · ★ 1 · AI & Automation · score 67

Install: claude install-skill senderkit/senderkit-skills

# SenderKit MCP messaging operations Use this skill when SenderKit is connected as an MCP server and the user wants you to operate SenderKit through tool calls. The documented MCP surface is small and tool-only: ten tools, all prefixed with `senderkit_`. This skill **operates SenderKit at runtime via MCP** and does not change application code. To add or wire SenderKit into a codebase (SDK/REST integration, migrating a provider), use the `senderkit-integration` skill instead. ## Source of truth and drift The connected MCP server's advertised tool list is the runtime source of truth, not this document. - The tool map below mirrors the published surface at `https://docs.senderkit.com/mcp/tools` (ten tools). Treat that page as canonical when the two disagree, and prefer the live tool list over both. - If the connected server advertises an additional `senderkit_*` tool that is not listed here, you may use it after reading its tool schema. Do not assume a tool exists because it appears here; if a listed tool is absent at runtime, skip it and tell the user. - Older or restricted servers may expose fewer tools (for example without the template-authoring tools). Confirm a tool is present before relying on it. ## Required workflow 1. Check context before acting. - Call `senderkit_context` before any send or cancellation. - Tell the user whether the active connection is `test` or `live`. - In `live` mode, do not send or cancel unless the user's request clearly authorizes