Ext Ops Panel
Open dashboard
Comparison

SuperMailOS vs HQBase

SuperMailOS is an MCP server published by supermailos.com. Marketplaces we read that list it: 1 (Official MCP Registry). HQBase is an MCP server published by HQBase. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplaceSuperMailOSHQBase
Official MCP Registry Listed
Version: 1.2.0
No figure published
Not marked · First seen
Listed
Version: 1.0.0
Forks (GitHub): 37
Stars (GitHub): 346
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

SuperMailOS vs HQBase
FactSuperMailOSHQBase
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub346
Forks (GitHub) (differs)No figure on GitHub37
Last releaseNot publishedNot published
Where it runs (differs)Remote server (supermailos.com/mcp)Not stated
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/hqbase/hqbase
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

SuperMailOS

In its own words, on Official MCP Registry:

Read, search, organize, draft and send business email from your SuperMailOS mailboxes.

HQBase

In its own words, on Official MCP Registry:

Connect AI agents to your self-hosted HQBase shared email workspace.

How to run each

SuperMailOS As a remote MCP server

Claude Code
claude mcp add --transport http mail https://supermailos.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

HQBase

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Only SuperMailOS 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: SuperMailOS · What it can do: HQBase · 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