connector-namespaces vs dev.wraps/email
connector-namespaces is a plugin bundle for AI coding tools published by Azure. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). dev.wraps/email is an MCP server published by wraps.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
| Marketplace | ||
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 1.2.0 Forks (GitHub): 7 Stars (GitHub): 20 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.8.2 Downloads/month (npm): 888 Downloads/week (npm): 59 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | connector-namespaces | dev.wraps/email |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 20 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 7 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@wraps.dev/mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 7, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/azure/connectors | github.com/wraps-team/wraps-js |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
connector-namespaces
Interactive GitHub Copilot canvas for discovering, connecting, and managing hosted MCP servers from an Azure Connector Namespace.
dev.wraps/email
Send email through your own Amazon SES account, and check domains, suppressions and sandbox status.
How to run each
connector-namespaces
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
dev.wraps/email As a local MCP server: npm package
claude mcp add --transport stdio email -- npx -y @wraps.dev/mcpCommands 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
The marketplaces of connector-namespaces publish no settings it asks for, so we do not compare settings.
What it can do: connector-namespaces · What it can do: dev.wraps/email · Compare two other plugins
Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/plugin/marketplace.json. 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.