Ext Ops Panel
Open dashboard
Comparison

dev.primitive/email vs Agent Email

dev.primitive/email is an MCP server published by primitive.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Agent Email is an MCP server published by UseJunior. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplacedev.primitive/emailAgent Email
Official MCP Registry Listed
Version: 0.2.0
No figure published
Not marked · First seen
Listed
Version: 0.3.2
Downloads/month (npm): 744
Downloads/week (npm): 338
Forks (GitHub): 2
Stars (GitHub): 6
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

dev.primitive/email vs Agent Email
Factdev.primitive/emailAgent Email
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub6
Forks (GitHub) (differs)No figure on GitHub2
Last releaseNot publishedNot published
Where it runs (differs)Remote server (www.primitive.dev/mcp)On your machine (email-agent-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/primitivedotdev/primitive-mono-repogithub.com/usejunior/email-agent-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days ago, requires a keyno 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

dev.primitive/email

In its own words, on Official MCP Registry:

Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.

Agent Email

In its own words, on Official MCP Registry:

Local email connectivity for AI agents — read, draft, send, and organize Outlook mail via MCP

How to run each

dev.primitive/email As a remote MCP server

Claude Code
claude mcp add --transport http email https://www.primitive.dev/mcp

Agent Email As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio email-agent-mcp -- npx -y email-agent-mcp

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

Only dev.primitive/email 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

Neither one's marketplaces publish the settings it asks for.

What it can do: dev.primitive/email · What it can do: Agent Email · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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