Ext Ops Panel
Open dashboard
Comparison

ActiveCampaign vs dev.wraps/email

ActiveCampaign is a plugin bundle for AI coding tools published by ActiveCampaign. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins). 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

Where each is published
MarketplaceActiveCampaigndev.wraps/email
Claude Code: claude-plugins-official Listed
Version: 0.3.1
Forks (GitHub): 2
Stars (GitHub): 3
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 0.3.1
Forks (GitHub): 2
Stars (GitHub): 3
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

ActiveCampaign vs dev.wraps/email
FactActiveCampaigndev.wraps/email
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)3 (better)1 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@wraps.dev/mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published7, secrets among them: 0
Parts of the bundle (differs)14Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/activecampaign/activecampaign-plugingithub.com/wraps-team/wraps-js
Changes in the last 7 days00
First seen2026-10-112026-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

ActiveCampaign

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

Marketing automation, CRM, and email marketing powered by ActiveCampaign. Manage contacts, campaigns, automations, deals, and get AI-powered marketing insights — all from Claude.

dev.wraps/email

In its own words, on Official MCP Registry:

Send email through your own Amazon SES account, and check domains, suppressions and sandbox status.

How to run each

ActiveCampaign As a Claude Code plugin

Claude Code
/plugin install activecampaign@claude-plugins-official

dev.wraps/email As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio email -- npx -y @wraps.dev/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

The marketplaces of ActiveCampaign publish no settings it asks for, so we do not compare settings.

What it can do: ActiveCampaign · What it can do: dev.wraps/email · Compare two other plugins

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

Where the data comes from: how the catalog is built