Ext Ops Panel
Open dashboard
Comparison

windows-desktop-com-plugin-for-mail vs Agent Email

windows-desktop-com-plugin-for-mail is a plugin bundle for AI coding tools published by gabrieldenny-del. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Agent Email is an MCP server published by UseJunior. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-03. 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
Marketplacewindows-desktop-com-plugin-for-mailAgent Email
Claude Code: claude-plugins-community Listed
Version: 56113b9
Forks (GitHub): 3
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.0
Downloads/month (npm): 1 479
Downloads/week (npm): 520
Forks (GitHub): 2
Stars (GitHub): 7
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.4.0
Downloads/month (npm): 1 479
Downloads/week (npm): 520
Forks (GitHub): 2
Stars (GitHub): 7
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

windows-desktop-com-plugin-for-mail vs Agent Email
Factwindows-desktop-com-plugin-for-mailAgent Email
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)3 (worse)7 (better)
Forks (GitHub) (differs)3 (better)2 (worse)
Last release (differs)Not published2026-10-27
Where it runs (differs)Installs as a plugin bundleOn your machine (email-agent-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/gabrieldenny-del/outlook-extensiongithub.com/usejunior/email-agent-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-10-11

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

windows-desktop-com-plugin-for-mail

In its own words, on Claude Code: claude-plugins-community:

Claude Cowork connector for Microsoft Outlook desktop. Read, triage, draft, send, and schedule — all via local COM. No Azure AD, no IT approvals, no cloud credentials.

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

windows-desktop-com-plugin-for-mail As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install windows-desktop-com-plugin-for-mail@claude-community

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.

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: windows-desktop-com-plugin-for-mail · What it can do: Agent Email · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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