Ext Ops Panel
Open dashboard
Comparison

Outlook vs io.github.qmmughal/titan-email-mcp

Outlook is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). io.github.qmmughal/titan-email-mcp is an MCP server published by qmmughal. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-23. 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
MarketplaceOutlookio.github.qmmughal/titan-email-mcp
Cursor: cursor/plugins Listed
Version: 1.0.0
Forks (GitHub): 1 353
Stars (GitHub): 13 601
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.5
Downloads/month (npm): 1 123
Downloads/week (npm): 114
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.0.5
Downloads/month (npm): 1 123
Downloads/week (npm): 114
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

Outlook vs io.github.qmmughal/titan-email-mcp
FactOutlookio.github.qmmughal/titan-email-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)13 601 (better)0 (worse)
Forks (GitHub) (differs)1 353 (better)0 (worse)
Last release (differs)Not published2026-10-12
Where it runs (differs)Remote server (api.cursor.com/rest-mcp/outlook/mcp)On your machine (titan-email-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published7, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
LicenceMITMIT
Repository (differs)github.com/cursor/pluginsgithub.com/qmmughal/titan-email-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 6 days agono 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

Outlook

In its own words, on Cursor: cursor/plugins:

Search, read, and send Microsoft Outlook email, and look up contacts.

io.github.qmmughal/titan-email-mcp

In its own words, on Official MCP Registry:

MCP server for Titan Email (IMAP/SMTP), tested and confirmed with GoDaddy mailboxes.

How to run each

Outlook

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

io.github.qmmughal/titan-email-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "TITAN_EMAIL=<YOUR_TITAN_EMAIL>" --env "TITAN_PASSWORD=<YOUR_TITAN_PASSWORD>" --transport stdio titan-email-mcp -- npx -y titan-email-mcp

Requires: TITAN_EMAIL, TITAN_PASSWORD (secret)

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

Only Outlook 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 Outlook publish no settings it asks for, so we do not compare settings.

What it can do: Outlook · What it can do: io.github.qmmughal/titan-email-mcp · Compare two other plugins

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