HubSpot vs Outlook Assistant
HubSpot is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Outlook Assistant is an MCP server published by littlebearapps. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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
| Marketplace |   Outlook Assistant | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 3.14.1 Downloads/month (npm): 3 259 Downloads/week (npm): 500 Forks (GitHub): 18 Stars (GitHub): 39 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
| Fact | HubSpot | Outlook Assistant |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 39 |
| Forks (GitHub) (differs) | No figure on GitHub | 18 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (app.hubspot.com/mcp/v1/http) | On your machine (@littlebearapps/outlook-assistant) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 5, secrets among them: 1 |
| Hooks it runs (differs) | Not published | 2 |
| Parts of the bundle (differs) | Not a bundle | 4 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/littlebearapps/outlook-assistant |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 days ago | no 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
HubSpot
Unite marketing, sales, and customer service with AI-powered automation, lead management, and comprehensive analytics.
Outlook Assistant
Microsoft Outlook MCP server — 22 tools for email, calendar, contacts, and mailbox management.
How to run each
HubSpot As a remote MCP server
claude mcp add --transport http hubspot https://app.hubspot.com/mcp/v1/httpRequires: HUBSPOT_API_KEY (secret)
Outlook Assistant As a local MCP server: npm package
claude mcp add --env "OUTLOOK_CLIENT_SECRET=<YOUR_OUTLOOK_CLIENT_SECRET>" --transport stdio outlook-assistant -- npx -y @littlebearapps/outlook-assistantRequires: OUTLOOK_CLIENT_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only HubSpot 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
Only HubSpot asks for
HUBSPOT_API_KEY (secret)
Only Outlook Assistant asks for
OUTLOOK_ALLOWED_RECIPIENTSOUTLOOK_AUTH_AUDIENCE (secret)OUTLOOK_CLIENT_IDOUTLOOK_CLIENT_SECRET (secret)OUTLOOK_MAX_EMAILS_PER_SESSIONOUTLOOK_READ_ONLY
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: HubSpot · What it can do: Outlook Assistant · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.