io.github.Inefavel/sfmc-mcp-server vs HubSpot MCP
io.github.Inefavel/sfmc-mcp-server is an MCP server published by Inefavel. Marketplaces we read that list it: 1 (Official MCP Registry). HubSpot MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-11-13. 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 |  io.github.Inefavel/sfmc-mcp-server |   HubSpot MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 Downloads/month (npm): 113 Downloads/week (npm): 44 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.3.0 Forks (GitHub): 18 Stars (GitHub): 76 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 | io.github.Inefavel/sfmc-mcp-server | HubSpot MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 76 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 18 (better) |
| Last release (differs) | Not published | 2026-11-12 |
| Where it runs (differs) | On your machine (sfmc-mcp-server) | On your machine (https://github.com/Servosity/msp-skills/releases/download/hubspot-v0.3.0/hubspot-mcp.mcpb) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 1 | 8, secrets among them: 2 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/inefavel/sfmc-mcp-server | github.com/servosity/msp-skills |
| Changes in the last 7 days (differs) | 0 | 15 |
| First seen | 2026-10-11 | 2026-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
io.github.Inefavel/sfmc-mcp-server
MCP Server para Salesforce Marketing Cloud: valida queries do Automation Studio antes de rodar.
HubSpot MCP
Every HubSpot Sales Hub feature, plus offline cross-object queries, property-change-history
How to run each
io.github.Inefavel/sfmc-mcp-server As a local MCP server: npm package
claude mcp add --env "SFMC_CLIENT_ID=<YOUR_SFMC_CLIENT_ID>" --env "SFMC_CLIENT_SECRET=<YOUR_SFMC_CLIENT_SECRET>" --env "SFMC_SUBDOMAIN=<YOUR_SFMC_SUBDOMAIN>" --transport stdio sfmc-mcp-server -- npx -y sfmc-mcp-serverRequires: SFMC_CLIENT_ID, SFMC_CLIENT_SECRET (secret), SFMC_SUBDOMAIN
HubSpot MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install hubspot@msp-skillsRequires: HUBSPOT_ACCESS_TOKEN (secret), HUBSPOT_MCP_HTTP_TOKEN (secret)
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 io.github.Inefavel/sfmc-mcp-server asks for
SFMC_ACCOUNT_IDSFMC_CLIENT_IDSFMC_CLIENT_SECRET (secret)SFMC_MODESFMC_SUBDOMAIN
Only HubSpot MCP asks for
HUBSPOT_ACCESS_TOKEN (secret)HUBSPOT_BASE_URLHUBSPOT_MCP_HTTP_TOKEN (secret)HUBSPOT_MCP_READ_ONLYHUBSPOT_NO_LOCAL_DATAHUBSPOT_OWNER_EMAILHUBSPOT_USER_AGENTPRINTING_PRESS_CLIENT_PROFILE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.Inefavel/sfmc-mcp-server · What it can do: HubSpot MCP · Compare two other plugins
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.