Ext Ops Panel
Open dashboard
Comparison

mcp-apps vs MemoFS MCP Server

mcp-apps is a plugin bundle for AI coding tools published by modelcontextprotocol. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). MemoFS MCP Server is an MCP server published by memofs.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-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

Where each is published
Marketplacemcp-appsMemoFS MCP Server
Claude Code: claude-plugins-official Listed
Version: 0.1.0
Forks (GitHub): 401
Stars (GitHub): 2 947
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 401
Stars (GitHub): 2 947
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.0-beta.3
Downloads/month (npm): 290
Downloads/week (npm): 66
Forks (GitHub): 2
Stars (GitHub): 6
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

mcp-apps vs MemoFS MCP Server
Factmcp-appsMemoFS MCP Server
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)2 947 (better)6 (worse)
Forks (GitHub) (differs)401 (better)2 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (memofs.dev/api/v1/projects/%7BprojectId%7D/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/modelcontextprotocol/ext-appsgithub.com/memo-fs/memofs
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 31 h ago

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

mcp-apps

In its own words, on Claude Code: claude-plugins-official:

Skills for creating MCP Apps with the MCP Apps SDK

MemoFS MCP Server

In its own words, on Official MCP Registry:

Persistent memory and virtual filesystem MCP server for AI agents.

How to run each

mcp-apps As a Claude Code plugin

Claude Code
/plugin install mcp-apps@claude-plugins-official

MemoFS MCP Server

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

Requires: MEMOFS_API_KEY (secret), Authorization header

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

Only MemoFS MCP Server 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 mcp-apps publish no settings it asks for, so we do not compare settings.

What it can do: mcp-apps · What it can do: MemoFS MCP Server · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built