@mcpfusion/core vs Marrow AI: Control Layer for AI Agents
@mcpfusion/core is an MCP server published by @mcpfusion. Marketplaces we read that list it: 1 (npm registry (MCP servers)). Marrow AI: Control Layer for AI Agents is an MCP server published by getmarrow.ai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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 |   Marrow AI: Control Layer for AI Agents | |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 5.1.0 Downloads/month (npm): 4 777 Downloads/week (npm): 854 Forks (GitHub): 24 Stars (GitHub): 255 Not marked · First seen |
Listed Version: 3.9.112 Downloads/month (npm): 12 819 Downloads/week (npm): 2 475 Forks (GitHub): 0 Stars (GitHub): 7 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 3.9.112 Downloads/month (npm): 12 819 Downloads/week (npm): 2 475 Forks (GitHub): 0 Stars (GitHub): 7 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 | @mcpfusion/core | Marrow AI: Control Layer for AI Agents |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 255 (better) | 7 (worse) |
| Forks (GitHub) (differs) | 24 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-08 |
| Where it runs (differs) | On your machine (@mcpfusion/core) | On your machine (@getmarrow/mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/vinkius-labs/mcpfusion | github.com/getmarrow/marrow-mcp |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-12 | 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
@mcpfusion/core
MVA (Model-View-Agent) framework for the Model Context Protocol. Structured perception packages with Presenters, cognitive guardrails, self-healing errors, action consolidation, and tRPC-style type safety — so AI agents perceive and act on your data det
Marrow AI: Control Layer for AI Agents
Approval gate and audit trail for AI agent actions: policy check first, proof after. Any MCP client.
How to run each
@mcpfusion/core
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Marrow AI: Control Layer for AI Agents As a local MCP server: npm package
claude mcp add --env "MARROW_API_KEY=<YOUR_MARROW_API_KEY>" --transport stdio marrow -- npx -y @getmarrow/mcpRequires: MARROW_API_KEY (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
The marketplaces of @mcpfusion/core publish no settings it asks for, so we do not compare settings.
What it can do: @mcpfusion/core · What it can do: Marrow AI: Control Layer for AI Agents · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.org). 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.