Ext Ops Panel
Open dashboard
Comparison

PO6 Mailbox vs io.github.orieg/gws-connector

PO6 Mailbox is an MCP server published by po6.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.orieg/gws-connector is an MCP server published by orieg. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-11-07. 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
MarketplacePO6 Mailboxio.github.orieg/gws-connector
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.4.3
Forks (GitHub): 2
Stars (GitHub): 4
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.3.1
Forks (GitHub): 2
Stars (GitHub): 4
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

PO6 Mailbox vs io.github.orieg/gws-connector
FactPO6 Mailboxio.github.orieg/gws-connector
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub4
Forks (GitHub) (differs)No figure on GitHub2
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.po6.com)On your machine (https://github.com/orieg/gws-connector/releases/download/v0.4.3/gws-mcp.mcpb)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle9
Licence (differs)Not statedMIT
Repository (differs)github.com/po6-com/po6_mailgithub.com/orieg/gws-connector
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: last check 2 days ago returned HTTP 401no 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

PO6 Mailbox

In its own words, on Official MCP Registry:

Give AI agents secure access to your email via private aliases with dedicated mailbox storage.

io.github.orieg/gws-connector

In its own words, on Official MCP Registry:

Multi-account Google Workspace MCP — Gmail, Calendar, Drive, Sheets, Docs with smart routing.

How to run each

PO6 Mailbox As a remote MCP server

Claude Code
claude mcp add --transport http mailbox https://mcp.po6.com

io.github.orieg/gws-connector As a Claude Code plugin

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

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

Only PO6 Mailbox 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

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

What it can do: PO6 Mailbox · What it can do: io.github.orieg/gws-connector · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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