SendGrid

SendGrid

Send email and inspect deliverability via SendGrid from an AI agent.

Score 56(?)CommunityMITVerified Top MCPs for Email

Quick answer

What it does

Wraps the SendGrid v3 REST API: send mail, query Activity Feed, list suppressions, inspect authenticated senders and IPs.

Best for

  • Transactional send
  • Activity Feed investigation
  • Suppression list audits
  • Sender auth verification

Not for

  • High-volume marketing campaigns from chat
  • Workflows that need granular IP pool selection from the model

Setup recipe

Pick your client, then follow the three steps.

  1. 1

    Install

    claude_desktop_config.json
    {
      "mcpServers": {
        "sendgrid": {
          "command": "npx",
          "args": [
            "-y",
            "sendgrid-mcp"
          ],
          "env": {
            "SENDGRID_API_KEY": "${SENDGRID_API_KEY}",
            "SENDGRID_FROM": "${SENDGRID_FROM}"
          }
        }
      }
    }

    Paste under mcpServers. Fully quit and reopen Claude after editing.

    CLI or .mcp.json
    # export SENDGRID_API_KEY=SG.changeme
    # export SENDGRID_FROM=agent@example.com
    claude mcp add sendgrid -- npx -y sendgrid-mcp

    Run from your repo. Commit .mcp.json to share with your team.

    .cursor/mcp.json
    {
      "mcpServers": {
        "sendgrid": {
          "command": "npx",
          "args": [
            "-y",
            "sendgrid-mcp"
          ],
          "env": {
            "SENDGRID_API_KEY": "${SENDGRID_API_KEY}",
            "SENDGRID_FROM": "${SENDGRID_FROM}"
          }
        }
      }
    }

    Global path: ~/.cursor/mcp.json. Reload window after editing.

    .vscode/mcp.json
    {
      "servers": {
        "sendgrid": {
          "command": "npx",
          "args": [
            "-y",
            "sendgrid-mcp"
          ],
          "env": {
            "SENDGRID_API_KEY": "${SENDGRID_API_KEY}",
            "SENDGRID_FROM": "${SENDGRID_FROM}"
          }
        }
      }
    }

    VS Code uses the "servers" key (not "mcpServers").

    ~/.codeium/windsurf/mcp_config.json
    {
      "mcpServers": {
        "sendgrid": {
          "command": "npx",
          "args": [
            "-y",
            "sendgrid-mcp"
          ],
          "env": {
            "SENDGRID_API_KEY": "${SENDGRID_API_KEY}",
            "SENDGRID_FROM": "${SENDGRID_FROM}"
          }
        }
      }
    }

    Open via Cascade → hammer icon → Configure.

    cline_mcp_settings.json
    {
      "mcpServers": {
        "sendgrid": {
          "command": "npx",
          "args": [
            "-y",
            "sendgrid-mcp"
          ],
          "env": {
            "SENDGRID_API_KEY": "${SENDGRID_API_KEY}",
            "SENDGRID_FROM": "${SENDGRID_FROM}"
          }
        }
      }
    }

    Open via the Cline sidebar → MCP Servers → Edit.

    ~/.continue/config.json
    {
      "experimental": {
        "modelContextProtocolServers": [
          {
            "transport": {
              "type": "stdio",
              "command": "npx",
              "args": [
                "-y",
                "sendgrid-mcp"
              ],
              "env": {
                "SENDGRID_API_KEY": "${SENDGRID_API_KEY}",
                "SENDGRID_FROM": "${SENDGRID_FROM}"
              }
            }
          }
        ]
      }
    }

    Continue uses modelContextProtocolServers with a transport block.

    ~/.codex/config.toml
    # ~/.codex/config.toml
    [mcp_servers.sendgrid]
    command = "npx"
    args = [
      "-y",
      "sendgrid-mcp",
    ]
    env = { SENDGRID_API_KEY = "${SENDGRID_API_KEY}", SENDGRID_FROM = "${SENDGRID_FROM}" }

    Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

    ~/.config/zed/settings.json
    {
      "context_servers": {
        "sendgrid": {
          "command": {
            "path": "npx",
            "args": [
              "-y",
              "sendgrid-mcp"
            ]
          },
          "env": {
            "SENDGRID_API_KEY": "${SENDGRID_API_KEY}",
            "SENDGRID_FROM": "${SENDGRID_FROM}"
          }
        }
      }
    }

    Zed calls them "context_servers". Settings live-reload on save.

    ChatGPT → Apps directory

    SendGrid doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

  2. 2

    Set required secrets

    Set SENDGRID_API_KEY, SENDGRID_FROM in your shell environment before launching your MCP client.

  3. 3

    Try a minimum working prompt

    Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

ToolDescriptionArgsSide effects
send_mailSend a transactional email via the v3 Mail Send API.to: string, subject: string, html: stringWrite
query_activitySearch the Activity Feed by recipient, status, or time window.query: objectRead
list_suppressionsList bounces, blocks, and spam reports.type: stringRead
verify_senderCheck the verification status of a sender or domain.sender: stringRead

Security & scope

Access scope
Read + write
Sandbox
Authenticates with a SendGrid API key scoped to the smallest necessary permissions. Send + read-stats by default; suppressions only when explicitly granted.
Gotchas
  • Never use a Full Access key — agents only need Mail Send + Stats Read.
  • SENDGRID_FROM must be a verified sender or domain; unverified senders fail with 403.
  • Activity Feed has a 30-day retention window — older events return empty without warning.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.
Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.
Recommend the best MCP servers for [task: e.g. email work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-email
Compare SendGrid against a real alternative. Swap the second MCP in [brackets] if you want a different match.
Compare SendGrid MCP vs [Resend MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/sendgrid
- top-mcps.com listing for Resend
Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.
Install the SendGrid MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/sendgrid (fetch https://top-mcps.com/mcp/sendgrid.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (SENDGRID_API_KEY, SENDGRID_FROM) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

2 updates tracked.
  1. Refreshed install snippets and fact sheet; verified for 2026.

  2. Initial directory listing.

More Email MCPs

Other tools in the same category worth evaluating.

Gmail

Send, read, search, and label Gmail from an AI agent — community MCP with auto-OAuth.

gmail, email, community, google
15 minMedium
Resend
Official

Send transactional and broadcast emails via the official Resend MCP.

resend, email, transactional, broadcast
2 minLow
Mailgun
Official

Manage Mailgun messaging, domains, webhooks, and analytics from an AI agent.

mailgun, email, transactional, analytics
5 minLow

Compared with SendGrid

Side-by-side breakdowns for the choices people most often weigh against this MCP.

Exploring Top MCPs for Email? See all Email MCPs →