Which API key permissions does it need?

Mail Send + Stats Read for the default tool set. Add Suppressions Read/Write to manage the bounce list. Never give the agent the Full Access key.

Does it support subusers?

Yes via the on-behalf-of header. Pass SENDGRID_SUBUSER to scope all calls to one subuser without rotating keys.

Activity Feed search granularity?

Per-recipient, per-status, per-time-window. The Activity Feed v3 endpoint is what the SendGrid UI itself uses — same fidelity for the agent.

SendGrid

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

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

Score 66(?)CommunityMIT 3Verified Aug 19, 2026Top MCPs for Email →

Install View on GitHub

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

Source: top-mcps.com/mcp/sendgrid — verified Aug 2026

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "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.jsonshell

# 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.jsonjson

{
  "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.jsonjsonc

{
  "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.jsonjson

{
  "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.jsonjson

{
  "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.jsonjson

{
  "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.tomlshell

# ~/.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.jsonjsonc

{
  "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 directorynone

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
Set required secrets
Set SENDGRID_API_KEY, SENDGRID_FROM in your shell environment before launching your MCP client.
3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tool	Description	Args	Side effects
`send_mail`	Send a transactional email via the v3 Mail Send API.	to: string, subject: string, html: string	Write
`query_activity`	Search the Activity Feed by recipient, status, or time window.	query: object	Read
`list_suppressions`	List bounces, blocks, and spam reports.	type: string	Read
`verify_sender`	Check the verification status of a sender or domain.	sender: string	Read

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.

Aug 19, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Feb 22, 2025
Initial directory listing.

At a glance

Maintainer: Community
Transport: stdio
Auth model: API key
Required secrets: SENDGRID_API_KEYSENDGRID_FROM
Supported clients: ChatGPT
Claude Desktop
Claude Code
Cursor
VS Code
Windsurf
Cline
Continue
Zed
Codex CLI
License: MIT
Language: TypeScript
Latest version: latest
Last verified: Aug 19, 2026

GitHub repo

Rank badge

Maintainer of SendGrid? Embed the live badge — it re-renders with the current rank and score on every catalog refresh.

[![Ranked #6 in Email on Top-MCPs](https://top-mcps.com/badge/sendgrid.svg)](https://top-mcps.com/mcp/sendgrid)

Alternatives

Resend →
Send transactional and broadcast emails via the official Resend MCP.
Postmark →
Send transactional email from an AI agent — verified deliverability, audit-friendly.
Mailgun →
Manage Mailgun messaging, domains, webhooks, and analytics from an AI agent.

Related guides

Best MCP Servers for Email in 2026 (Ranked + Setup) →
Setup Guide
Best MCPs for Marketers in 2026 (SEO, Email, Analytics) →
Role Guide

More Email MCPs

Other tools in the same category worth evaluating.

Microsoft Work IQ

Official

Ask natural-language questions across Microsoft 365 Copilot data.

microsoftcopilotsearchemail

10 minMedium

Microsoft 365

Outlook mail and calendar, Teams, OneDrive and Excel through one Graph API server.

microsoftoutlookcalendaremail

10 minMedium

Gmail

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

gmailemailcommunitygoogle

15 minMedium

Compared with SendGrid

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

SendGridvsResend SendGridvsPostmark SendGridvsMailgun

Exploring Top MCPs for Email? See all Email MCPs →