Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

SendGrid MCP Server

by deyikongversion 1.4.0i★ –iRuns on your computer
Registry nameio.github.deyikong/sendgrid-mcp

Install

Overview

Description from the maker (original English)

MCP server for SendGrid's v3 API: email marketing, transactional mail, templates, and analytics.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Marketing & social media
  • You need to fill in: SENDGRID_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: SENDGRID_API_KEY, READ_ONLY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "sendgrid": {
      "command": "npx",
      "args": [
        "-y",
        "sendgrid-mcp"
      ],
      "env": {
        "SENDGRID_API_KEY": "your-value",
        "READ_ONLY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add sendgrid --env SENDGRID_API_KEY=your-value --env READ_ONLY=your-value -- npx -y sendgrid-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "sendgrid": {
      "command": "npx",
      "args": [
        "-y",
        "sendgrid-mcp"
      ],
      "env": {
        "SENDGRID_API_KEY": "your-value",
        "READ_ONLY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "sendgrid": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "sendgrid-mcp"
      ],
      "env": {
        "SENDGRID_API_KEY": "your-value",
        "READ_ONLY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • SENDGRID_API_KEY secret required env
    Your SendGrid API key (must start with 'SG.').
  • READ_ONLY env
    When true (the default), blocks all write/delete operations at runtime while keeping every tool registered and visible.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account deyikong, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Marketing & social mediai

  • More stars than 0% of the other 2987 servers in this category
  • Published to the registry more recently than 31% of the other 2987 servers in this category
  • Basic checks equal to or better than 100% of the other 2987 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is SendGrid MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: SENDGRID_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.4.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

An MCP server retrieving transcripts of YouTube videos

Runs on your computer★ 495MITUpdated 10 days ago
Install

GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.

Runs on your computer★ 244MITUpdated 10 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

SendGrid MCP Server

A Model Context Protocol (MCP) server that provides comprehensive access to SendGrid's API v3 for email marketing, transactional email operations, dynamic template management, and detailed analytics. Features 154 tools covering all aspects of email management and performance analysis.

*Built and maintained by a SendGrid engineer, as an independent project — not an official SendGrid product.*

See RELEASES.md for what's changed in the latest release.

Features

  • Marketing Automations: Create and manage email automation workflows
  • Single Send Campaigns: Manage one-time email campaigns with detailed performance tracking
  • Contact Management: Complete CRUD operations for contacts with advanced search and bulk operations
  • Email Statistics & Analytics: Multi-dimensional performance analysis across browsers, devices, geography, and email providers with 13-month historical data
  • Dynamic Segment Management: Create, update, and delete contact segments with complex filtering criteria that automatically refresh
  • Dynamic Template Management: Create, manage, and version HTML email templates with Handlebars support for personalization
  • Custom Fields Management: Define and manage additional contact data fields for enhanced targeting
  • Mail Sending: Send transactional emails via SendGrid with full personalization support
  • Sender Identity Management: Manage verified sender identities with authentication tracking
  • Suppression Lists: Manage bounces, spam reports, and unsubscribes for deliverability optimization
  • Account Settings: Access account details and configuration management
  • Browser Integration: Quick links to SendGrid web interface for visual operations
  • Read-Only Safety Mode: Secure operation mode prevents accidental data modification while maintaining full analytics access

Supported MCP Clients

✅ Claude Desktop - Official desktop app ✅ Claude Code - Official CLI tool ✅ Claude custom connectors - via Streamable HTTP (see Install the server) ✅ OpenAI Responses API / Apps SDK - via Streamable HTTP ✅ MCP Market - Hosted, one-click deploy, no install required (see Install the server) ✅ Cline - VS Code extension ✅ Zed Editor - Modern code editor ✅ Continue - VS Code autopilot ✅ Codex CLI - via Streamable HTTP ✅ Any MCP-compatible client

Getting Started

Follow these steps in order — by the end you'll have the server installed (or deployed), your SendGrid API key set, and your MCP client connected.

This is the actual request path, whichever client you end up using — some launch the server locally over stdio, others reach it over the network via Streamable HTTP (MCP Market, self-hosted), which adds a choice of client auth on top:

                                ┌──────────┐

│ Client │ └────┬─────┘ ┌──────────────────────┴───────────────────┐ │ │ stdio (local subprocess) HTTP (network) │ auth: none | token | oauth │ │ │ └──────────────────────┬───────────────────┘ ▼ ┌────────────────────┐ │ MCP Server │ │ (this repo) │ └─────────┬──────────┘ │ SENDGRID_API_KEY │ (always required, any transport) ▼ ┌────────────────────┐ │ SendGrid API │ └────────────────────┘

SENDGRID_API_KEY is required no matter which path you take. READ_ONLY=true (the default) is a further gate *inside* the MCP Server box — it blocks create/update/delete/send tools once a request is already in, regardless of which branch it arrived on. See Environment Variables for the full list of what you can configure.

1. Install the server

Install it locally if your client launches it itself, or go remote if it connects over the network instead.

Local (stdio) — for Claude Desktop, Claude Code, Cline, Zed, Continue, or any client that runs the server as a subprocess:

npm install -g sendgrid-mcp

This installs the sendgrid-mcp command globally, which your MCP client will launch as a subprocess. Requires Node.js 20+.

Remote (HTTP) — nothing to install locally; pick one:

MCP Market (hosted, no install required)

MCP Market deploys and hosts this server for you — nothing to install locally and no environment variables to manage on your machine. You still need a SendGrid API key; you'll enter it into MCP Market instead of your own shell/config.

From MCP Market's MCP Servers page, deploy a custom MCP from either source:

  • GitHub — select the GitHub source, choose Public or Private repo, paste the repo URL (https://github.com/deyikong/sendgrid-mcp), and pick a server name.
  • npm — select the npm source, enter the package name (sendgrid-mcp), and pick a server name.

Either way, MCP Market builds and runs it for you; it shows up under MCP Servers with a Running status once ready. Continue to Configure your MCP client to set your credentials and connect.


Self-hosted (Streamable HTTP)

Run the server yourself and expose it over Streamable HTTP instead of letting a client launch it locally — for Claude custom connectors, OpenAI's Responses API mcp tool / Apps SDK, or any other remote client.

The MCP endpoint is POST /mcp; GET /health returns a status document for load balancers. Requests are handled statelessly (no session id required), which is what hosted clients expect.

none/token/oauth below are not alternate ways to *connect* — they're three different locks on the one new door (HTTP), as shown in the request-flow diagram above.

Quick start (local development)
export SENDGRID_API_KEY="SG.your_api_key_here"

export MCP_TRANSPORT=http export MCP_AUTH_MODE=token export MCP_AUTH_TOKEN="$(openssl rand -hex 32)"

sendgrid-mcp

Authentication

Set MCP_AUTH_MODE to one of:

ModeUse forRequires
oauthProduction / remote clientsMCP_OAUTH_ISSUER, MCP_OAUTH_AUDIENCE
tokenLocal dev, simple self-hostingMCP_AUTH_TOKEN (16+ chars)
noneLoopback development only— refuses to start on a public bind

OAuth mode makes this server an OAuth 2.1 resource server. It does not issue or store credentials — it verifies access tokens minted by your existing identity provider (Auth0, Okta, Entra ID, Google, Stytch, …) against that provider's published JWKS.

export MCP_AUTH_MODE=oauth

export MCP_OAUTH_ISSUER="https://your-tenant.auth0.com" export MCP_OAUTH_AUDIENCE="https://mcp.example.com" export MCP_OAUTH_REQUIRED_SCOPES="sendgrid:read" export MCP_PUBLIC_URL="https://mcp.example.com"

SENDGRID_API_KEY (see the diagram in Getting Started) is still required alongside these — OAuth only controls who can reach the server, not what the server uses to talk to SendGrid.

The server publishes RFC 9728 Protected Resource Metadata at /.well-known/oauth-protected-resource, so clients discover your authorization server automatically: an unauthenticated request gets a 401 whose WWW-Authenticate header points at that document, the client reads it, sends the user to your IdP to log in, and retries with the resulting token.

Tokens are rejected (401) if expired, wrongly signed, or issued for a different issuer or audience; a valid token missing a required scope gets 403.

Setting up your identity provider

Whichever provider you use, you're configuring the same three things: an issuer URL, an audience (a stable identifier for this API resource), and a scope clients will request. A few concrete walkthroughs:

Auth0

  1. Sign in to your Auth0 Dashboard and go to Applications → APIs → Create API.
  2. Set an Identifier — this is your audience, e.g. https://mcp.example.com. It doesn't need to resolve to anything; it just needs to be unique.
  3. Under the API's Permissions tab, add the scopes your server should require, e.g. sendgrid:read, sendgrid:write.
  4. Your Issuer URL is your tenant domain, shown on the API's *Settings* tab: https://YOUR_TENANT.auth0.com/.
export MCP_OAUTH_ISSUER="https://YOUR_TENANT.auth0.com/"

export MCP_OAUTH_AUDIENCE="https://mcp.example.com" export MCP_OAUTH_REQUIRED_SCOPES="sendgrid:read"

Okta

  1. Sign in to the Okta Admin Console and go to Security → API → Authorization Servers.
  2. Use the default authorization server, or create a new one. Its Issuer URI, shown at the top of the server's settings page, looks like https://{yourOktaDomain}/oauth2/{authServerId}.
  3. On the same page, the Audience field (default api://default) is what you'll use for the audience — set it to something specific to this server, e.g. api://sendgrid-mcp.
  4. Open the Scopes tab and add a scope, e.g. sendgrid:read.
export MCP_OAUTH_ISSUER="https://YOUR_OKTA_DOMAIN/oauth2/YOUR_AUTH_SERVER_ID"

export MCP_OAUTH_AUDIENCE="api://sendgrid-mcp" export MCP_OAUTH_REQUIRED_SCOPES="sendgrid:read"

Microsoft Entra ID (Azure AD)

  1. In the Azure Portal, go to Microsoft Entra ID → App registrations → New registration to represent this MCP server as a resource.
  2. Open the new app's Expose an API page and set the Application ID URI — this becomes your audience, e.g. api:// .
  3. On the same page, click Add a scope to define one, e.g. sendgrid.read.
  4. Your Issuer URL is https://login.microsoftonline.com/{tenant-id}/v2.0, where {tenant-id} is the directory (tenant) ID from the app's Overview page.
export MCP_OAUTH_ISSUER="https://login.microsoftonline.com/YOUR_TENANT_ID/v2.0"

export MCP_OAUTH_AUDIENCE="api://YOUR_CLIENT_ID" export MCP_OAUTH_REQUIRED_SCOPES="sendgrid.read"

Other providers (Google Identity Platform, Stytch, …) follow the same shape: find the OpenID Connect issuer (usually published at /.well-known/openid-configuration), define an audience/resource identifier for this server, and create a scope for it.

Whichever provider you use, also set MCP_PUBLIC_URL to the externally-reachable URL of your server (e.g. https://mcp.example.com) — clients use it during OAuth discovery.

TLS

Either terminate TLS in-process:

export TLS_KEY_FILE=/etc/ssl/private/mcp.key

export TLS_CERT_FILE=/etc/ssl/certs/mcp.crt export TLS_CA_FILE=/etc/ssl/certs/chain.pem # optional intermediates

…or terminate it at a proxy and tell the server to trust the forwarded headers

Only the beginning is shown; read the rest in the repo

Ask PopNx