Ext Ops Panel
Open dashboard
Comparison

agenticmail vs io.github.Bitfloo/mailoo

agenticmail is a plugin bundle for AI coding tools published by agenticmail. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.Bitfloo/mailoo is an MCP server published by Bitfloo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplaceagenticmailio.github.Bitfloo/mailoo
Claude Code: claude-plugins-community Listed
Version: 0.9.20
Forks (GitHub): 40
Stars (GitHub): 236
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 1 370
Downloads/week (npm): 502
Forks (GitHub): 0
Stars (GitHub): 0
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

agenticmail vs io.github.Bitfloo/mailoo
Factagenticmailio.github.Bitfloo/mailoo
Marketplaces that list it11
Stars (GitHub) (differs)236 (better)0 (worse)
Forks (GitHub) (differs)40 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@agenticmail/mcp)On your machine (@bitfloo/mailoo)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 050, secrets among them: 5
Hooks it runs (differs)30Not published
Parts of the bundle (differs)34Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/agenticmail/agenticmailgithub.com/bitfloo/mailoo
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

agenticmail

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

Give every Claude Code subagent its own real email address and phone number, all self hosted on the user's machine. AgenticMail runs a local mail server (Stalwart in a Colima or Docker container) so each agent has a working `<name>@localhost` inbox, an identity, an API key, and a persona. When a teammate is CC'd on an email they wake up as a Claude Code subagent under your existing Claude OAuth, read the full thread, decide if it is their turn, and either reply to all or stay silent. The thread is the workspace and the audit trail. There is no central orchestrator, no separate Anthropic key per agent, no data leaving your machine, and no polling because everything is push based over SSE. The plugin exposes three skills (`install`, `create-agent`, `coordinate`) that handle the one time bootstrap and let the host session kick off multi agent work with a single email. Behind the plugin sit five npm packages doing the real work: an Express API, an MCP server with 62 tools across email, SMS, contacts, drafts, temp

io.github.Bitfloo/mailoo

In its own words, on Official MCP Registry:

Mailoo — email MCP server for IMAP, SMTP, and ManageSieve. Multi-account, per-folder profiles.

How to run each

agenticmail As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install agenticmail@claude-community

io.github.Bitfloo/mailoo As a local MCP server: npm package

Claude Code
claude mcp add --env "MCP_EMAIL_ADDRESS=<YOUR_MCP_EMAIL_ADDRESS>" --env "MCP_EMAIL_ALERT_WEBHOOK_URL=<YOUR_MCP_EMAIL_ALERT_WEBHOOK_URL>" --env "MCP_EMAIL_HTTP_TOKEN=<YOUR_MCP_EMAIL_HTTP_TOKEN>" --env "MCP_EMAIL_IMAP_HOST=<YOUR_MCP_EMAIL_IMAP_HOST>" --env "MCP_EMAIL_OAUTH2_CLIENT_SECRET=<YOUR_MCP_EMAIL_OAUTH2_CLIENT_SECRET>" --env "MCP_EMAIL_OAUTH2_REFRESH_TOKEN=<YOUR_MCP_EMAIL_OAUTH2_REFRESH_TOKEN>" --env "MCP_EMAIL_PASSWORD=<YOUR_MCP_EMAIL_PASSWORD>" --env "MCP_EMAIL_SMTP_HOST=<YOUR_MCP_EMAIL_SMTP_HOST>" --transport stdio mailoo -- npx -y @bitfloo/mailoo

Requires: MCP_EMAIL_ADDRESS, MCP_EMAIL_ALERT_WEBHOOK_URL (secret), MCP_EMAIL_HTTP_TOKEN (secret), MCP_EMAIL_IMAP_HOST, MCP_EMAIL_OAUTH2_CLIENT_SECRET (secret), MCP_EMAIL_OAUTH2_REFRESH_TOKEN (secret), MCP_EMAIL_PASSWORD (secret), MCP_EMAIL_SMTP_HOST

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

Only agenticmail asks for

  • AGENTICMAIL_API_URL

Only io.github.Bitfloo/mailoo asks for

  • MCP_EMAIL_ACCOUNT_NAME
  • MCP_EMAIL_ADDRESS
  • MCP_EMAIL_ALERT_DESKTOP
  • MCP_EMAIL_ALERT_SOUND
  • MCP_EMAIL_ALERT_URGENCY_THRESHOLD
  • MCP_EMAIL_ALERT_WEBHOOK_ALLOW_PRIVATE
  • MCP_EMAIL_ALERT_WEBHOOK_URL (secret)
  • MCP_EMAIL_FULL_NAME
  • MCP_EMAIL_HOOK_AUTO_CALENDAR
  • MCP_EMAIL_HOOK_AUTO_FLAG
  • MCP_EMAIL_HOOK_AUTO_LABEL
  • MCP_EMAIL_HOOK_BATCH_DELAY
Show the remaining 38
  • MCP_EMAIL_HOOK_CALENDAR_ALARM_MINUTES
  • MCP_EMAIL_HOOK_CALENDAR_CONFIRM
  • MCP_EMAIL_HOOK_CALENDAR_NAME
  • MCP_EMAIL_HOOK_CUSTOM_INSTRUCTIONS
  • MCP_EMAIL_HOOK_ON_NEW_EMAIL
  • MCP_EMAIL_HOOK_PRESET
  • MCP_EMAIL_HTTP_ALLOWED_HOSTS
  • MCP_EMAIL_HTTP_HOST
  • MCP_EMAIL_HTTP_TOKEN (secret)
  • MCP_EMAIL_IMAP_DISABLE_IMAP4REV2
  • MCP_EMAIL_IMAP_HOST
  • MCP_EMAIL_IMAP_PORT
  • MCP_EMAIL_IMAP_STARTTLS
  • MCP_EMAIL_IMAP_TLS
  • MCP_EMAIL_IMAP_VERIFY_SSL
  • MCP_EMAIL_OAUTH2_CLIENT_ID
  • MCP_EMAIL_OAUTH2_CLIENT_SECRET (secret)
  • MCP_EMAIL_OAUTH2_PROVIDER
  • MCP_EMAIL_OAUTH2_REFRESH_TOKEN (secret)
  • MCP_EMAIL_PASSWORD (secret)
  • MCP_EMAIL_RATE_LIMIT
  • MCP_EMAIL_READ_ONLY
  • MCP_EMAIL_SAVE_TO_SENT
  • MCP_EMAIL_SIEVE_HOST
  • MCP_EMAIL_SIEVE_PORT
  • MCP_EMAIL_SMTP_HOST
  • MCP_EMAIL_SMTP_POOL_ENABLED
  • MCP_EMAIL_SMTP_POOL_MAX_CONNECTIONS
  • MCP_EMAIL_SMTP_POOL_MAX_MESSAGES
  • MCP_EMAIL_SMTP_PORT
  • MCP_EMAIL_SMTP_STARTTLS
  • MCP_EMAIL_SMTP_TLS
  • MCP_EMAIL_SMTP_VERIFY_SSL
  • MCP_EMAIL_SYSTEM_ONE_ENABLED
  • MCP_EMAIL_USERNAME
  • MCP_EMAIL_WATCHER_ENABLED
  • MCP_EMAIL_WATCHER_FOLDERS
  • MCP_EMAIL_WATCHER_IDLE_TIMEOUT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: agenticmail · What it can do: io.github.Bitfloo/mailoo · 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. 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