MCP YouTube Transcript
An MCP server retrieving transcripts of YouTube videos
Description from the maker (original English)
MCP server for SendGrid's v3 API: email marketing, transactional mail, templates, and analytics.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
SENDGRID_API_KEY, READ_ONLYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
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-mcpFill in the empty values before running it.
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.
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.
READ_ONLY envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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
The registry name was verified with the GitHub account deyikong, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
You need to fill in: SENDGRID_API_KEY
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).
The GitHub repo last changed –, and the latest version (1.4.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: MCP YouTube Transcript, Google Analytics MCP, BibiGPT YouTube Video Summarizer
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
GA4 MCP server for AI agents: schema discovery, server-side aggregation, analysis-ready defaults.
AI video summarizer: summarize and transcribe YouTube, Bilibili, TikTok and podcast videos.
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.
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.
✅ 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
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.
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:
https://github.com/deyikong/sendgrid-mcp), and pick a server 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.
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
Set MCP_AUTH_MODE to one of:
| Mode | Use for | Requires |
|---|---|---|
oauth | Production / remote clients | MCP_OAUTH_ISSUER, MCP_OAUTH_AUDIENCE |
token | Local dev, simple self-hosting | MCP_AUTH_TOKEN (16+ chars) |
none | Loopback 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.
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
https://mcp.example.com. It doesn't need to resolve to anything; it just needs to be unique.sendgrid:read, sendgrid:write.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
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}.api://default) is what you'll use for the audience — set it to something specific to this server, e.g. api://sendgrid-mcp.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)
api:// .sendgrid.read.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.
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