Two decisions separate this from a thin API wrapper. The first is that validation is a distinct step you can run alone, and the recommended send path runs it automatically — which matters because the failure mode of email tooling is a real message to a real recipient. The second is the confirmation token on mutating console operations: an assistant cannot quietly reconfigure your domain authentication or alerts by misreading an instruction. Sending still enqueues real email, so sandbox mode is where experiments belong.
A community-maintained MCP server for Twilio SendGrid, shipped as a single compiled binary. It covers sending with validation, dynamic template management, delivery diagnostics, and account and console settings, plus an optional local receiver that captures Event Webhook traffic so you can inspect it from the same session. Contact and list marketing CRUD is deliberately out of scope.
- A send request validated before anything is queued, and a send that runs the preflight first — `sendgrid_validate_send_request`, `sendgrid_send_with_preflight`, plus sandbox mode
- Dynamic templates listed, created, updated and activated
- Delivery diagnostics: Email Activity, suppressions, statistics, error classification and delivery triage
- Event Webhook configuration inside SendGrid, plus an optional local receiver that captures events for inspection — `get_received_webhook_events`, `get_webhook_receiver_status`
- Account and console settings: verified senders, domain authentication, mail and tracking settings, alerts and inbound parse
- A confirmation gate on the destructive parts: mutating console tools require `confirmToken: "CONFIRM"` before they act
- List and read tools that take an optional `response_format` of `markdown` or `json` and return pagination metadata
A SendGrid API key with scopes covering the tools you use, and a verified sender address matching the from address you configure — `SENDGRID_API_KEY` and `SENDGRID_FROM_EMAIL` are the two required values. Optional settings cover the display name, the EU region base URL, a full base-URL override and log level. Nothing else to install: download the binary for your platform from the releases page and make it executable — it is built with `bun build --compile` and embeds its runtime, so end users do not install Bun. The local webhook receiver turns on only when `SENDGRID_EVENT_WEBHOOK_PORT` is set; for a public tunnel, require signature verification and supply the SendGrid public key. Each user runs it locally with their own key rather than sharing one hosted instance. Package `sendgrid-mcp` (2.0.0), MIT licensed. Email Activity may need the paid add-on on your SendGrid account.
One command plus a key — npx -y sendgrid-mcp, then supply credentials