cachly← All posts
Growth · May 2026

30,000+ npm downloads: MCP distribution and the memory pivot

An honest look at the numbers, the distribution channel, and the one repositioning that changed everything.

The numbers

@cachly-dev/mcp-server launched on npm on April 16, 2026, and growth has been steady ever since — purely organic, with no paid acquisition. The package has since crossed 30,000+ npm downloads.

That curve didn't come from a launch post — we didn't write one. No Product Hunt, no Reddit, no Show HN. Purely organic.

30,000+
npm downloads
$0
Paid acquisition spend
23
Days since launch

What we thought would work

We built cachly as a semantic cache for AI applications. The pitch: save LLM API costs by caching similar requests. Fast, EU-hosted, GDPR-compliant. The cache pricing angle was technically correct. It was also easy to defer. Nobody's LLM bill was a problem yet — and even if it was, setting up cache middleware requires a code change. High friction.

What actually drove installs: the pivot to memory

The developers who became power users weren't using cachly as a cache. They were using it as AI memory — storing lessons from debugging sessions, recalling past fixes, persisting context across editor restarts. We'd built memory infrastructure while trying to sell a cache.

The repositioning was blunt: Your AI coding assistant forgets everything at the end of every session. cachly gives it a brain that persists. Installs accelerated from that week onward.

The MCP distribution effect

MCP (Model Context Protocol) is the most efficient developer tool distribution channel we've seen. When you publish an MCP server on npm, you get discovered by:

The search intent is already qualified. Someone who finds @cachly-dev/mcp-server while searching for “mcp server memory” has near-zero additional friction to install. One npx command, one config block, done.

What the Brain has learned (meta-lesson)

Here's a sample of what our own Brain instance has stored from running cachly in production:

TopicWhat worked
infra:clickhouse-ipv6listen_host = 0.0.0.0 + 127.0.0.1 in healthcheck
bash:macos-lowercasetr '[:upper:]' '[:lower:]' not ${var,,}
fix:stripe-webhookexpress.raw() must come before json() middleware
deploy:docker--force-recreate prevents stale container issues
fix:nextauth-sessionMiddleware must export config with matcher
fix:playwright-portE2E uses port 4000, prod uses 3000 — use env var

Every new session — on any machine, by any engineer — benefits from these. That's the value proposition in practice.

What's next

Steady, purely organic growth is a strong start. The users who benefit most — the ones who've recalled a critical fix that saved an hour of debugging — are the ones who stay and upgrade. The product bet: if the Brain is useful enough, developers will never want to work without it.

MCPnpmAI MemoryGrowthDeveloper Toolscachly Brain

cachly.dev

For solo developers, teams and whole companies

Explain it once. Every AI knows it.

cachly keeps what you explain to your AI in every session. Claude Code, Cursor, Copilot and Windsurf read your rules, decisions and solved bugs: for you alone, for your whole team and for every team in your company. Servers in Germany, with SSO and a DPA for companies.

Servers in the EU · one command, restart your editor, done · 1 project free

Four ways to install

Claude Code
/plugin marketplace add cachly-dev/cachly-mcp
/plugin install cachly-brain@cachly

Then turn on auto-update once: /plugin → Marketplaces → cachly → Enable auto-update

Any MCP editor
npx @cachly-dev/mcp-server@latest autopilot