Log inSubmit server
SendGrid MCP Server logo

SendGrid MCP Server

Manage SendGrid contacts, campaigns, automations, templates, and analytics through MCP tools.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install SendGrid MCP Server

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "sendgrid-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "sendgrid-mcp"
      ],
      "env": {
        "SENDGRID_API_KEY": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

SendGrid MCP Server MCP server connects MCP-compatible clients to SendGrid’s v3 API for contact management, marketing campaigns, automations, transactional email, templates, and analytics. It runs locally over stdio or remotely over Streamable HTTP, using a SendGrid API key for API access. Reach for it when an agent needs to inspect or manage SendGrid data, with read-only mode available to block write and send operations. The project is independent and is not an official SendGrid product.

Use cases

  • Manage SendGrid contacts and custom fields
  • Review Single Send campaign performance
  • Update marketing automation settings
  • Search contacts with filtering conditions
  • Inspect email analytics through an agent

Key features

  • SendGrid v3 API access over MCP
  • Contact, list, segment, and custom field management
  • Marketing automation and Single Send tools
  • Transactional email and dynamic template support
  • Campaign analytics and browser links
  • Read-only safety mode

Tools80

What SendGrid MCP Server lets your agent do. Expand a tool for its parameters.

Self-reported~1.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 44d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 5d ago via OSV.dev · sendgrid-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars4Stargazers on the source repository.
npm downloads1.6kPackage downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Tools exposed80Callable tools this server registers over MCP.

How SendGrid MCP Server works

What SendGrid MCP Server MCP server does

SendGrid MCP Server MCP server exposes SendGrid email operations as MCP tools. The repository describes coverage for marketing automations, one-time Single Send campaigns, contacts, lists, segments, custom fields, dynamic templates, transactional mail, sender identities, suppressions, account settings, and performance reporting.

The listed tools support common contact and campaign workflows. Agents can list, inspect, create, update, search, and delete contacts; manage email lists and custom fields; inspect and modify automation settings and steps; and review Single Send campaign details. Browser-opening tools provide links into SendGrid’s visual automation, campaign, and segment interfaces rather than replacing those interfaces.

The project is maintained independently by a SendGrid engineer and is not presented as an official SendGrid product.

How it works

An MCP client invokes the server’s tools, and the server calls SendGrid’s v3 API with the configured SENDGRID_API_KEY. Local clients can start the package as a subprocess using stdio. Remote deployments can expose the server through Streamable HTTP; the documented endpoint is POST /mcp, while GET /health provides a health response for load balancers. HTTP requests are stateless and do not require a session ID.

The server supports HTTP authentication modes of none, token, and oauth. OAuth mode verifies tokens issued by an existing identity provider; it does not issue or store those credentials. A read-only safety setting is enabled by default and blocks create, update, delete, and send operations while leaving read and analytics access available.

Setup and configuration

For local use, install the sendgrid-mcp package globally with npm and run it with Node.js 20 or newer. Configure SENDGRID_API_KEY in the environment used by the MCP client. The key is required for both stdio and HTTP deployments.

For a self-hosted HTTP deployment, set MCP_TRANSPORT=http. Token authentication additionally uses MCP_AUTH_MODE=token and an MCP_AUTH_TOKEN of at least 16 characters. OAuth authentication uses MCP_AUTH_MODE=oauth, along with an issuer and audience; the documented configuration can also define required scopes and the public URL. The none mode is intended for loopback development and refuses to start on a public bind.

The hosted MCP Market option runs the server remotely, so local installation is not required. Its deployment flow accepts the repository or npm package and lets you provide the SendGrid key in the hosted configuration.

Tools and capabilities

SendGrid MCP Server MCP server includes tools for:

  • Listing and inspecting automations, Single Send campaigns, contacts, lists, segments, and custom fields.
  • Creating, updating, searching, and deleting contacts, including custom data and list assignments.
  • Creating and maintaining email lists and custom field definitions.
  • Updating automation names, statuses, steps, wait times, and segment criteria.
  • Opening SendGrid’s browser-based creators, editors, and campaign statistics pages.
  • Supporting broader SendGrid features documented by the project, including dynamic templates, transactional sending, sender identities, suppression data, account settings, and multidimensional analytics.

Limitations and notes

Write operations can be prevented by the default read-only mode, so deployments intended to modify SendGrid data must account for that guard. Deletion tools permanently remove automations, contacts, lists, or segments according to the operation; the segment description specifically notes that deleting a segment does not delete its contacts.

The server requires a valid SendGrid API key even when HTTP authentication is enabled. HTTP OAuth controls access to the MCP endpoint; it does not replace the SendGrid credential used for API calls. Browser integration opens SendGrid web workflows for visual operations, so those tools depend on access to the SendGrid interface in the user’s browser.

The README names Claude Desktop, Claude Code, Cline, Zed, Continue, Codex CLI, Claude custom connectors, OpenAI’s Responses API and Apps SDK, MCP Market, and other MCP-compatible clients as supported connection options.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about SendGrid MCP Server

SendGrid MCP Server is an MCP server that connects AI clients to SendGrid’s v3 API. Its main tools manage contacts, email lists, segments, automations, Single Send campaigns, custom fields, templates, transactional email, and analytics. It can run locally over stdio or remotely over Streamable HTTP.

Install it locally with npm using `npm install -g sendgrid-mcp`, then run it with Node.js 20 or newer. Set `SENDGRID_API_KEY` in the client’s environment. Alternatively, deploy the package through MCP Market or run it remotely over Streamable HTTP.

The server requires `SENDGRID_API_KEY` for both local stdio and remote HTTP operation. HTTP deployments may also require authentication variables depending on whether token or OAuth mode is selected.

It does state that the server supports any MCP-compatible client, so Cursor may work if its MCP implementation supports the selected stdio or Streamable HTTP connection, but Cursor-specific configuration is not documented here.

Related MCP servers

All in Communication All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSendGrid MCP Server AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/sendgrid-mcp-server?style=directory)](https://allmcps.com/mcp/sendgrid-mcp-server)
HTML Embed
<a href="https://allmcps.com/mcp/sendgrid-mcp-server"><img src="https://allmcps.com/api/badge/sendgrid-mcp-server?style=directory" alt="SendGrid MCP Server on AllMCPs" /></a>