Ext Ops Panel
Open dashboard
Comparison

ai.bobwork/emailwarmup vs SendGrid MCP Server

ai.bobwork/emailwarmup is an MCP server published by bobwork.ai. Marketplaces we read that list it: 1 (Official MCP Registry). SendGrid MCP Server is an MCP server published by deyikong. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceai.bobwork/emailwarmupSendGrid MCP Server
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.4.0
Downloads/month (npm): 1 078
Downloads/week (npm): 304
Forks (GitHub): 3
Stars (GitHub): 4
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.4.0
Downloads/month (npm): 1 078
Downloads/week (npm): 304
Forks (GitHub): 3
Stars (GitHub): 4
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

ai.bobwork/emailwarmup vs SendGrid MCP Server
Factai.bobwork/emailwarmupSendGrid MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)4 (better)
Forks (GitHub) (differs)0 (worse)3 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (app-emailwarmup.bobwork.ai/mcp)On your machine (sendgrid-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)Not statedISC
Repository (differs)github.com/agent-operating-system/emailwarmup-mcpgithub.com/deyikong/sendgrid-mcp
Changes in the last 7 days00
First seen (differs)2026-11-022026-10-11
Endpoint at the last check (differs)Status out of date: last check 2 days ago returned HTTP 405no remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

ai.bobwork/emailwarmup

In its own words, on Official MCP Registry:

Warm up mailboxes, check the ready-for-outbound gate, run cold email and get checkout links.

SendGrid MCP Server

In its own words, on Official MCP Registry:

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

How to run each

ai.bobwork/emailwarmup As a remote MCP server

Claude Code
claude mcp add --transport http emailwarmup https://app-emailwarmup.bobwork.ai/mcp --header "Authorization: Bearer <YOUR_API_KEY>"

Requires: Authorization header

SendGrid MCP Server As a local MCP server: npm package

Claude Code
claude mcp add --env "SENDGRID_API_KEY=<YOUR_SENDGRID_API_KEY>" --transport stdio sendgrid-mcp -- npx -y sendgrid-mcp

Requires: SENDGRID_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only ai.bobwork/emailwarmup has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of ai.bobwork/emailwarmup publish no settings it asks for, so we do not compare settings.

What it can do: ai.bobwork/emailwarmup · What it can do: SendGrid MCP Server · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built