@senderkit
基本情報
Build and send email, SMS, push, and web-push from your AI coding agent
https://mcp.senderkit.comclaude mcp add senderkit --transport http https://mcp.senderkit.comReturns 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.
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.
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.
List all message templates in the workspace across email, SMS, push, and web-push, with slugs and channels.
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.
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.
Fetch full details and delivery status for a single message by ID — check whether a specific email or SMS was delivered, bounced, or failed.
Cancel a still-pending message (scheduled or queued) by its public id.
List the workspace's programmatic inbound email addresses — the addresses that receive mail and forward it or fire a webhook into the workspace.
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.
Delete one of the workspace's inbound email addresses by id. The address immediately stops receiving new mail; already-received messages are unaffected.
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.
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.
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.
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.
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.
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.
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.
SenderKit adds transactional email, SMS, push, and web-push notifications to any app directly from an AI coding agent. It is packaged as a plugin for Claude Code, OpenAI Codex, Cursor, opencode, and other Agent Skills–compatible assistants, and can send messages directly or route through providers like Resend, SendGrid, Postmark, Mailgun, SES, Twilio, FCM, APNs, and Expo.
Install the skills using npx skills add senderkit/senderkit-skills or follow per-platform instructions (Claude Code, Codex, Cursor, opencode). Then connect the SenderKit MCP server via OAuth (built-in for each client) or optionally with an API key. Three skills are available: senderkit-integration, senderkit-mcp-messaging-operations, and senderkit-email-deliverability.
Integration writes SenderKit into your code and migrates existing notification logic; messaging operations sends and inspects messages at runtime via MCP tool calls.
SenderKit can route email, SMS, push, and web-push through Resend, SendGrid, Postmark, Mailgun, SES, Twilio, FCM, APNs, Expo, and others – so your app is not locked into one vendor.
Each client setup uses OAuth – no API key is stored in the repository. Claude Code users run `/mcp` and sign in; Codex users run `codex mcp login senderkit`; Cursor users toggle the server in Settings → MCP; opencode users run `opencode mcp auth senderkit`. Optionally, an API key (`SENDERKIT_API_KEY`) can be used with a custom MCP config.
ChatGPT support means OpenAI Codex, the coding agent (CLI/IDE extension/app). The ChatGPT chat app does not load skills.
The skills run within the coding assistant’s environment; the MCP server connects to `https://mcp.senderkit.com` via OAuth or API key. No local server or database is needed.
Senderkit のリモート MCP サーバーは、https://mcp.senderkit.com にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。
エンドポイント https://mcp.senderkit.com を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。
はい。Senderkit は OAuth を使用します。初回接続時に MCP クライアントがブラウザを開いてサインイン・認可を行い、以降はその認証情報を再利用します。
Senderkit は stdio エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。
Discover, evaluate, and buy solutions for the cloud
Pharmaceutical drug & clinical trial intelligence
Convert web pages to clean Markdown and retrieval-ready chunks with browser rendering support.
CVE prioritization using exploitation signals, plus agent heartbeat monitoring and state capsules. Some tools use API-key or x402 access.
Pay-per-use data and tools for AI agents: crypto token safety and rug checks, web search with cited answers, page-to-Markdown, up-to-date library docs, package safety, company research and UK/EU open data. 160 tools, 20
コメント