PMLL-memory-mcp
A complementary persistent-memory server for Context+ users who need cross-session memory and KV caching.
park
Idea as submitted
PMLL-memory-mcp is a separate MCP server by @drQedwards that adapts Context+’s long-term memory graph and adds short-term KV context memory, Q-promise deduplication, and a solution engine on top. It is positioned as a complementary server to Context+, with full credit and links back to the PMLL repository for details.
Context+ documents pmll-memory-mcp in its README as a complementary server: `npx pmll-memory-mcp` is a separate MCP server by @drQedwards that adapts Context+’s long-term memory graph and adds short-term KV context memory, Q-promise deduplication, and a solution engine on top. The README points readers to drQedwards/PPM for more information.
The commit history also reflects this relationship. Two April commits — “docs: fix Memory & RAG section to correctly describe pmll-memory-mcp as complementary server” and “docs: add pmll-memory-mcp standalone package info” — include `Co-authored-by: drQedwards` trailers, along with agent session logs pointing to `drQedwards/contextplus`. There is also an `agent-instructions.md` entry: “Document PMLL short-term KV memory tools and patterns.”
Both projects are MIT licensed, and the lineage is presented as mutual adaptation with mutual credit rather than infringement. Context+ is framed as codebase intelligence with AST, semantic search, blast radius analysis, and in-memory decay-scored graphs. PMLL is framed as persistent memory across sessions with KV cache and Q-promise deduplication. The products are described as complementary rather than competing.
Context+ has 1.9k stars, 161 forks, and 12 contributors. PMLL has 13 installs on vibehackers. The proposed distribution strategy is to treat the Context+ README as a permanent backlink and to position PMLL as the official complementary memory server recommended in Context+’s README. The strongest validation pitch is: “PMLL is the official complementary memory server to Context+ (1.9k★), recommended in their README, built by a Context+ core contributor.”
I
Scorecard
The headline numbers. Overall viability score, pipeline stage, and whether this idea passed or failed each gate criterion.
Overall Score
54of 100
park
Criteria Breakdown
Problem Severity
9/15
Buyer & Budget Clarity
5/15
Existing Spend (Workaround Gravity)
11/15
Competitive Landscape
3/12
Search Demand
8/12
Distribution Feasibility
4/12
TTFV (Time To First Value)
9/10
Timing & Momentum
5/9
Total
54 / 100
01 — What We're Validating
What We're Validating
“If developers install PMLL alongside Context+, they will experience faster session starts and willingness to pay for premium sync”
Problem
AI coding agents lose all context between sessions, forcing developers to re-explain project architecture and preferences every new session
Target Customer
Individual developers and small dev teams using MCP-compatible AI coding assistants (Claude Code, Cursor) daily
Wedge Use-Case
One-command install (npx pmll-memory-mcp) as complementary server to Context+ (1.9k★), recommended in their README
Pricing
Free OSS core + $9-15/month cloud sync tier
Hypothesis
If developers install PMLL alongside Context+, they will experience faster session starts and willingness to pay for premium sync
II
Understanding the Job
Before looking at competitors or keywords, we decompose the underlying job your customers are trying to get done.
03 — Task Decomposition
Task Decomposition
Primary Goal: Never lose AI coding context — ensure every AI coding session starts with full project awareness, decisions, preferences, and prior work immediately available
1
Capture session context automatically
Record what the AI agent learned, decided, and produced during a coding session without requiring manual effort from the developer. Current workaround: manually update CLAUDE.md files or copy-paste conversation summaries. Competitors serving this: agentmemory (auto-capture with 4-tier consolidation), claude-mem (auto-compress via Haiku), Anthropic Remember plugin (auto-save). PMLL approach: long-term memory graph with decay scoring.
Intercept agent actions and decisions during session → Extract salient facts vs noise (what matters vs ephemeral) → Compress and deduplicate captured information (Q-promise dedup) → Store with decay scoring so stale context fades naturally
2
Inject relevant context into new sessions
When a new coding session starts, automatically provide the AI agent with relevant prior context — project architecture, past decisions, code conventions, user preferences. Current workaround: CLAUDE.md (200-line cap), .cursorrules (static). Competitors: mem0 (semantic search retrieval), Engram (auto git detection), Basic Memory (markdown knowledge graph). PMLL approach: short-term KV cache + memory graph retrieval.
Identify which prior context is relevant to current session → Retrieve from persistent storage with relevance ranking → Format and inject into agent context window efficiently → Manage context window budget (don't overflow with old context)
3
Persist memory across devices and environments
Ensure memory survives beyond a single machine — developers work across laptops, cloud IDEs, and team environments. Current workaround: git-committed context files (manual). Competitors: mem0 cloud ($19-249/mo), MemPalace (€10-15/mo), Basic Memory cloud ($15/mo). PMLL approach: proposed cloud sync tier ($9-15/mo) — not yet built.
Sync memory state to cloud storage → Handle merge conflicts between devices → Support team-shared vs personal memory boundaries → Provide offline-first with eventual sync
4
Manage memory lifecycle (decay, pruning, versioning)
Prevent memory from becoming stale or overwhelming. Old decisions may no longer apply, deprecated code patterns should fade. Current workaround: manual file maintenance. Competitors: agentmemory (95.2% R@5 benchmark), Graphiti (temporal validity windows). PMLL approach: decay-scored memory graph adapted from Context+.
Apply time-based decay to reduce stale context weight → Allow manual pinning of important permanent context → Provide versioned history of what the agent 'knew' at any point → Handle contradictions (new decisions overriding old ones)
5
Install and configure with zero friction
Get from zero to working memory in under 2 minutes. Current workaround: create CLAUDE.md manually (5 min). Competitors: agentmemory (npx, zero deps), Engram (single binary), Graphiti (requires Neo4j — high friction). PMLL approach: npx pmll-memory-mcp (one command).
Single-command install via npx → Auto-detect MCP client (Claude Code, Cursor, etc.) → No external database dependencies → Sensible defaults with optional configuration
04 — Friction Points & Critical Sequence
Friction Points & Critical Sequence
Manual context file maintenance (CLAUDE.md, .cursorrules) — developers must manually write, update, and prune context files every session
Forced by: No built-in cross-session memory in most MCP clients; CLAUDE.md has 200-line cap [Source: competition-analysis.md, Substitutes]
Impact: 10-30 minutes wasted per session re-establishing context; degraded first-response quality [Source: idea.md, Current Solution]
Context staleness — old decisions and deprecated patterns persist in static files without decay
Forced by: CLAUDE.md and .cursorrules are static text with no temporal awareness; no mechanism to age out irrelevant context [Source: competition-analysis.md, Substitutes]
Impact: AI agent acts on outdated information, producing wrong code or contradicting recent decisions; developer must correct and re-explain
No cross-device or cross-tool memory — context locked to one machine and one IDE
Forced by: File-based context is git-committed or local; switching between laptop, desktop, or cloud IDE means starting over [Source: idea.md, Current Solution]
Impact: Developers who work across environments effectively have zero persistent memory; must re-explain on every device
Context window overflow — injecting too much prior context crowds out the current task
Forced by: No intelligent retrieval or ranking of past context; current workarounds are all-or-nothing (dump full CLAUDE.md or nothing)
Impact: Either starved for context (too little) or drowning in irrelevant context (too much); no optimum without smart retrieval
Memory duplication and contradiction — same facts stored multiple times, old decisions conflict with new ones
Forced by: No deduplication or conflict resolution in manual context files; append-only patterns create bloat [Source: idea.md, Differentiation — Q-promise dedup]
Impact: AI agent receives contradictory instructions, leading to confused outputs; developer doesn't know which version of truth agent is using
| Friction Point | Forced By | Impact |
|---|---|---|
| Manual context file maintenance (CLAUDE.md, .cursorrules) — developers must manually write, update, and prune context files every session | No built-in cross-session memory in most MCP clients; CLAUDE.md has 200-line cap [Source: competition-analysis.md, Substitutes] | 10-30 minutes wasted per session re-establishing context; degraded first-response quality [Source: idea.md, Current Solution] |
| Context staleness — old decisions and deprecated patterns persist in static files without decay | CLAUDE.md and .cursorrules are static text with no temporal awareness; no mechanism to age out irrelevant context [Source: competition-analysis.md, Substitutes] | AI agent acts on outdated information, producing wrong code or contradicting recent decisions; developer must correct and re-explain |
| No cross-device or cross-tool memory — context locked to one machine and one IDE | File-based context is git-committed or local; switching between laptop, desktop, or cloud IDE means starting over [Source: idea.md, Current Solution] | Developers who work across environments effectively have zero persistent memory; must re-explain on every device |
| Context window overflow — injecting too much prior context crowds out the current task | No intelligent retrieval or ranking of past context; current workarounds are all-or-nothing (dump full CLAUDE.md or nothing) | Either starved for context (too little) or drowning in irrelevant context (too much); no optimum without smart retrieval |
| Memory duplication and contradiction — same facts stored multiple times, old decisions conflict with new ones | No deduplication or conflict resolution in manual context files; append-only patterns create bloat [Source: idea.md, Differentiation — Q-promise dedup] | AI agent receives contradictory instructions, leading to confused outputs; developer doesn't know which version of truth agent is using |
⚙
Critical Sequence
Session ends → context captured automatically → Captured context stored persistently with metadata → New session starts → relevant context retrieved → Retrieved context injected into agent's context window → Agent uses context to produce informed first response
Most fragile: Captured context stored persistently with metadata — If capture-to-storage fails silently (crash, permission error, MCP disconnect), the entire chain breaks invisibly. User won't know memory was lost until next session, when context is missing. This is the weakest link because it's the only async, background step that can fail without immediate feedback. Competitors mitigate this differently: agentmemory benchmarks R@5 at 95.2%, Graphiti uses temporal graphs for integrity, mem0 uses managed cloud. PMLL's approach (decay-scored graph) needs to prove reliability at this exact handoff.
Most fragile: Captured context stored persistently with metadata — If capture-to-storage fails silently (crash, permission error, MCP disconnect), the entire chain breaks invisibly. User won't know memory was lost until next session, when context is missing. This is the weakest link because it's the only async, background step that can fail without immediate feedback. Competitors mitigate this differently: agentmemory benchmarks R@5 at 95.2%, Graphiti uses temporal graphs for integrity, mem0 uses managed cloud. PMLL's approach (decay-scored graph) needs to prove reliability at this exact handoff.
III
Who's Already Here
Every player in this space: direct competitors, substitutes, and adjacent tools that could pivot into your territory.
05 — Market Intelligence
Market Intelligence
11
Direct competitors
4
Substitutes
5
Adjacencies
Patterns
- Free OSS core is table stakes — every direct competitor ships a free self-hosted tier; paid is always cloud sync or metered API, matching PMLL's proposed freemium split.
- Market is fragmenting rapidly — 592 memory MCP servers listed on PulseMCP; differentiation requires a measurable benchmark claim (agentmemory won with 95.2% R@5).
- Demand is validated — mem0.ai at 388K visits/mo and agentmemory at 22.4k GitHub stars confirm real user pull; traffic concentrates on branded platforms, not individual repos.
- Distribution is the real moat — Context+ README backlink is a unique, embedded acquisition channel none of the above competitors share; most competitors rely on cold GitHub discovery.
- Cloud sync pricing of $9–15/mo is consistent with market — MemPalace €10–15, Basic Memory $15/mo; PMLL's hypothesis is in-range.
Gaps
- No benchmark data for PMLL vs agentmemory (Q-promise dedup and decay scoring need a published R@5 or TTFR metric to compete with agentmemory's 95.2% claim).
- agentmemory cloud/paid tier unknown — if they launch cloud sync, PMLL loses its primary freemium wedge.
- Engram cloud pricing unknown — a low-cost Go binary competitor with 4.3k stars could undercut on price.
- npm download counts not obtainable for any competitor (npmjs.com returned 403) — install velocity unknown.
- PMLL itself does not appear in npm search results yet — discoverability via npm is unproven.
- Supermemory.ai traffic is declining (244K → 174K in 3 months) — worth monitoring whether this segment is consolidating.
- LangMem GitHub URL and MCP compatibility unconfirmed — may be LangChain-only, not a true MCP competitor.
mem0.ai
388,779 /mo
supermemory.ai
174,227 /mo
getzep.com
103,936 /mo
basicmemory.com
17,518 /mo
06 — Competitor Details
Competitor Details
Pricing: Free OSS
Platform: MCP / all agents
Core Task: Auto-capture + inject session context
Demand: 22.4k GitHub stars
Pricing: Free (10K mem); $19/mo; $79/mo; $249/mo
Platform: Web + MCP
Core Task: Managed memory layer for agents
Demand: 388K visits/mo (SimilarWeb)
Pricing: OSS free; Zep cloud: free tier + $125/mo
Platform: MCP + Python
Core Task: Temporal knowledge graph memory
Demand: 26.5k GitHub stars ; 104K visits/mo getzep.com
Pricing: Free OSS (AGPL); $15/mo cloud
Platform: MCP + Claude Desktop
Core Task: Markdown-file knowledge graph
Demand: 3.2k GitHub stars ; 17.5K visits/mo
Pricing: Free OSS (MIT); cloud pricing
Platform: MCP + Go binary
Core Task: Coding-specific session memory
Demand: 4.3k GitHub stars
Pricing: Free consumer app; $19/mo Pro API; $100/mo Max
Platform: Web + MCP
Core Task: Universal memory layer
Demand: 174K visits/mo (SimilarWeb) ; 1.7k GitHub stars
Pricing: Free OSS
Platform: MCP + Python
Core Task: Semantic memory + knowledge graph
Demand: 1.4k GitHub stars
Pricing: Free OSS (MIT)
Platform: MCP / Claude Code
Core Task: Context persistence during sessions
Demand: Demand proxy
Pricing: Free (200 mem); €10/mo Pro; €15/mo Power
Platform: MCP + Web
Core Task: AI memory palace
Demand: Demand proxy
Pricing: Freemium; paid tier pricing
Platform: MCP + Web (contextforge.dev)
Core Task: Long-term memory + Git sync + team
Demand: 0 GitHub stars
Pricing: Free OSS
Platform: MCP
Core Task: Lightweight knowledge graph
Demand: Part of official MCP servers repo
Pricing: Free (built-in)
Platform: Claude Code / Cursor
Core Task: Manual project context files
Demand: Millions of users (inferred)
Pricing: Free–$8/mo
Platform: Web + desktop
Core Task: Manual knowledge management
Demand: Tens of millions of users
Pricing: $10/mo
Platform: VS Code / JetBrains
Core Task: IDE-native AI with some context
Demand: Millions of paid subscribers
Pricing: Included in Cursor Pro $20/mo
Platform: IDE
Core Task: .cursorrules persistent instructions
Demand: 1M+ users (Cursor)
Pricing: Free OSS (MIT)
Platform: MCP / npm
Core Task: Codebase intelligence + RAG
Demand: 1.9k GitHub stars
Pricing: Free app tier
Platform: Web
Core Task: Personal bookmark / knowledge memory
Demand: 174K visits/mo
Pricing: Free OSS; $125/mo
Platform: SDK / Python
Core Task: Production-grade agent memory at scale
Demand: 104K visits/mo
Pricing: Free OSS
Platform: Python / LangChain
Core Task: Long-term memory for LangChain agents
Demand: GitHub stars
Pricing: Free (MIT self-hosted); cloud pricing
Platform: MCP + Docker
Core Task: Semantic code search + memory graphs
Demand: GitHub stars
| Competitor | Pricing | Platform | Core Task | Demand Proxy |
|---|---|---|---|---|
| agentmemory | Free OSS | MCP / all agents | Auto-capture + inject session context | 22.4k GitHub stars |
| Mem0 / OpenMemory | Free (10K mem); $19/mo; $79/mo; $249/mo | Web + MCP | Managed memory layer for agents | 388K visits/mo (SimilarWeb) |
| Graphiti MCP (Zep) | OSS free; Zep cloud: free tier + $125/mo | MCP + Python | Temporal knowledge graph memory | 26.5k GitHub stars ; 104K visits/mo getzep.com |
| Basic Memory | Free OSS (AGPL); $15/mo cloud | MCP + Claude Desktop | Markdown-file knowledge graph | 3.2k GitHub stars ; 17.5K visits/mo |
| Engram | Free OSS (MIT); cloud pricing | MCP + Go binary | Coding-specific session memory | 4.3k GitHub stars |
| Supermemory | Free consumer app; $19/mo Pro API; $100/mo Max | Web + MCP | Universal memory layer | 174K visits/mo (SimilarWeb) ; 1.7k GitHub stars |
| mcp-memory-service | Free OSS | MCP + Python | Semantic memory + knowledge graph | 1.4k GitHub stars |
| mcp-memory-keeper | Free OSS (MIT) | MCP / Claude Code | Context persistence during sessions | Demand proxy |
| MemPalace Cloud | Free (200 mem); €10/mo Pro; €15/mo Power | MCP + Web | AI memory palace | Demand proxy |
| contextforge-mcp | Freemium; paid tier pricing | MCP + Web (contextforge.dev) | Long-term memory + Git sync + team | 0 GitHub stars |
| Official MCP Memory Server | Free OSS | MCP | Lightweight knowledge graph | Part of official MCP servers repo |
| CLAUDE.md / .cursorrules | Free (built-in) | Claude Code / Cursor | Manual project context files | Millions of users (inferred) |
| Notion / Obsidian (manual notes) | Free–$8/mo | Web + desktop | Manual knowledge management | Tens of millions of users |
| GitHub Copilot (built-in context) | $10/mo | VS Code / JetBrains | IDE-native AI with some context | Millions of paid subscribers |
| Cursor / Windsurf rules files | Included in Cursor Pro $20/mo | IDE | .cursorrules persistent instructions | 1M+ users (Cursor) |
| Context+ | Free OSS (MIT) | MCP / npm | Codebase intelligence + RAG | 1.9k GitHub stars |
| Supermemory (app) | Free app tier | Web | Personal bookmark / knowledge memory | 174K visits/mo |
| Zep / Graphiti (agent infra) | Free OSS; $125/mo | SDK / Python | Production-grade agent memory at scale | 104K visits/mo |
| LangMem | Free OSS | Python / LangChain | Long-term memory for LangChain agents | GitHub stars |
| Hindsight | Free (MIT self-hosted); cloud pricing | MCP + Docker | Semantic code search + memory graphs | GitHub stars |
07 — Content Strategy Matrix
Content Strategy Matrix
Competitors dominate through pricing/comparison content (mem0 ranks for 25+ Claude pricing keywords) and brand-driven SEO (Zep/Graphiti own their branded terms with 34K+ vol). The biggest content gap is in MCP memory comparison and selection content — no competitor owns 'best mcp memory server' or 'mcp memory server comparison'. Memory-specific educational content (benchmarks, setup guides, how-to) is also underserved. PMLL's best SEO opportunity is comparison pages targeting 'claude-mem' alternatives (Easy SERP, $43 CPC) and MCP marketplace content.
Pricing/Plans Pages
1/3mem0.ai
getzep.combasicmemory.com
API Documentation & Developer Guides
2/3mem0.aigetzep.com
basicmemory.com
Competitor Comparison Pages
1/3mem0.ai
getzep.combasicmemory.com
Integration Guides (Claude Code, Cursor, etc.)
2/3mem0.aibasicmemory.com
getzep.com
Benchmark & Performance Content
1/3getzep.com
mem0.aibasicmemory.com
Educational Content (Memory Types, Concepts)
1/3mem0.ai
getzep.combasicmemory.com
Open Source / Self-Hosting Guides
2/3mem0.aibasicmemory.com
getzep.com
Use Case / Vertical Pages
1/3mem0.ai
getzep.combasicmemory.com
| Strategy | mem0.ai | getzep.com | basicmemory.com | Coverage |
|---|---|---|---|---|
| Pricing/Plans Pages | ✓ | — | — | 1/3 |
| API Documentation & Developer Guides | ✓ | ✓ | — | 2/3 |
| Competitor Comparison Pages | ✓ | — | — | 1/3 |
| Integration Guides (Claude Code, Cursor, etc.) | ✓ | — | ✓ | 2/3 |
| Benchmark & Performance Content | — | ✓ | — | 1/3 |
| Educational Content (Memory Types, Concepts) | ✓ | — | — | 1/3 |
| Open Source / Self-Hosting Guides | ✓ | — | ✓ | 2/3 |
| Use Case / Vertical Pages | ✓ | — | — | 1/3 |
IV
Demand Signals
Real demand data: what keywords people type, what questions they ask, and whether anyone is paying for ads.
08 — Search Landscape
Search Landscape
⚖
SERP Weakness Analysis
35 keywords analyzed — 3 Easy · 11 Medium · 21 Hard
mcp server
Vol: 60,500
Ads: YES
Medium2 weak
mcp protocol
Vol: 6,600
Ads: YES
Hard1 weak
claude code plugins
Vol: 5,400
Ads: YES
Medium2 weak
claude mem
Vol: 4,400
Ads: YES
Easy4 weak
claude-mem
Vol: 3,600
Ads: YES
Easy3 weak
mcp tools
Vol: 2,900
Ads: YES
Hard0 weak
claude code version
Vol: 2,400
Ads: YES
Hard1 weak
claude code memory
Vol: 1,300
Ads: YES
Medium3 weak
mcp marketplace
Vol: 1,300
Ads: YES
Easy2 weak
claude code latest version
Vol: 1,300
Ads: YES
Hard1 weak
mcp server list
Vol: 1,300
Ads: YES
Hard1 weak
mcp server github
Vol: 1,300
Ads: YES
Hard0 weak
model context protocol server
Vol: 1,000
Ads: YES
Hard1 weak
best mcp servers
Vol: 1,000
Ads: YES
Medium2 weak
claude code extensions
Vol: 1,000
Ads: YES
Hard1 weak
model context protocol servers
Vol: 880
Ads: YES
Hard0 weak
mcp server examples
Vol: 880
Ads: YES
Hard0 weak
mcp server ai
Vol: 590
Ads: YES
Medium3 weak
claude code context
Vol: 320
Ads: YES
Medium2 weak
model context protocol documentation
Vol: 260
Ads: YES
Hard0 weak
free mcp servers
Vol: 260
Ads: YES
Hard1 weak
mcp servers cursor
Vol: 210
Ads: YES
Medium2 weak
openai mcp server
Vol: 210
Ads: YES
Hard1 weak
cursor memory
Vol: 140
Ads: YES
Hard1 weak
model context protocol examples
Vol: 140
Ads: YES
Medium2 weak
github model context protocol
Vol: 140
Ads: NONE
Hard0 weak
claude code auto memory
Vol: 110
Ads: NONE
Medium2 weak
model context protocol openai
Vol: 110
Ads: NONE
Hard0 weak
github mcp server claude code
Vol: 110
Ads: YES
Hard0 weak
mcp server vs api
Vol: 110
Ads: NONE
Hard1 weak
mcp memory server
Vol: 90
Ads: YES
Hard1 weak
mcp server memory
Vol: 70
Ads: YES
Hard1 weak
windsurf memory
Vol: 50
Ads: NONE
Medium2 weak
claude code memory tool
Vol: 50
Ads: NONE
Medium3 weak
claude code persistent memory
Vol: 50
Ads: NONE
Hard1 weak
| Keyword | Volume | Ads | Difficulty | Takeaway |
|---|---|---|---|---|
| mcp server | 60,500 | YES | Medium2 weak | |
| mcp protocol | 6,600 | YES | Hard1 weak | |
| claude code plugins | 5,400 | YES | Medium2 weak | |
| claude mem | 4,400 | YES | Easy4 weak | |
| claude-mem | 3,600 | YES | Easy3 weak | |
| mcp tools | 2,900 | YES | Hard0 weak | |
| claude code version | 2,400 | YES | Hard1 weak | |
| claude code memory | 1,300 | YES | Medium3 weak | |
| mcp marketplace | 1,300 | YES | Easy2 weak | |
| claude code latest version | 1,300 | YES | Hard1 weak | |
| mcp server list | 1,300 | YES | Hard1 weak | |
| mcp server github | 1,300 | YES | Hard0 weak | |
| model context protocol server | 1,000 | YES | Hard1 weak | |
| best mcp servers | 1,000 | YES | Medium2 weak | |
| claude code extensions | 1,000 | YES | Hard1 weak | |
| model context protocol servers | 880 | YES | Hard0 weak | |
| mcp server examples | 880 | YES | Hard0 weak | |
| mcp server ai | 590 | YES | Medium3 weak | |
| claude code context | 320 | YES | Medium2 weak | |
| model context protocol documentation | 260 | YES | Hard0 weak | |
| free mcp servers | 260 | YES | Hard1 weak | |
| mcp servers cursor | 210 | YES | Medium2 weak | |
| openai mcp server | 210 | YES | Hard1 weak | |
| cursor memory | 140 | YES | Hard1 weak | |
| model context protocol examples | 140 | YES | Medium2 weak | |
| github model context protocol | 140 | NONE | Hard0 weak | |
| claude code auto memory | 110 | NONE | Medium2 weak | |
| model context protocol openai | 110 | NONE | Hard0 weak | |
| github mcp server claude code | 110 | YES | Hard0 weak | |
| mcp server vs api | 110 | NONE | Hard1 weak | |
| mcp memory server | 90 | YES | Hard1 weak | |
| mcp server memory | 70 | YES | Hard1 weak | |
| windsurf memory | 50 | NONE | Medium2 weak | |
| claude code memory tool | 50 | NONE | Medium3 weak | |
| claude code persistent memory | 50 | NONE | Hard1 weak |
Top Easy Wins
claude mem
4,400 vol4 weak
claude-mem
3,600 vol3 weak
mcp marketplace
1,300 vol2 weak
| Keyword | Volume | Weak Spots |
|---|---|---|
| claude mem | 4,400 | 4 |
| claude-mem | 3,600 | 3 |
| mcp marketplace | 1,300 | 2 |
09 — Keyword Clusters
Keyword Clusters
102 keywords across 8 clusters. Purchase intent: 18%. Problem intent: 4%.
MCP Server Ecosystem
64,420 vol · 14 kw
Claude Code Features
10,100 vol · 5 kw
Claude Code Memory
9,720 vol · 16 kw
MCP Protocol & Documentation
7,620 vol · 5 kw
MCP Server Discovery
5,430 vol · 14 kw
AI Coding Tool Extensions
2,760 vol · 12 kw
Competitor Tools (Cursor/Windsurf)
420 vol · 7 kw
AI Agent Memory
130 vol · 29 kw
10 — High-Value Keywords
High-Value Keywords
claude-mem
Vol: 3,600
CPC: $43.57
Comp: 0.00
uncleargithub mcp server claude code
Vol: 110
CPC: $29.29
Comp: 0.00
unclearopenai mcp server
Vol: 210
CPC: $28.62
Comp: 0.00
unclearclaude mem
Vol: 4,400
CPC: $24.82
Comp: 2.00
unclearmcp server
Vol: 60,500
CPC: $17.88
Comp: 33.00
unclearmodel context protocol server
Vol: 1,000
CPC: $16.85
Comp: 3.00
unclearcursor memory
Vol: 140
CPC: $15.50
Comp: 6.00
unclearclaude code latest version
Vol: 1,300
CPC: $15.07
Comp: 0.00
unclearclaude code extensions
Vol: 1,000
CPC: $13.97
Comp: 20.00
purchase intentmodel context protocol servers
Vol: 880
CPC: $12.58
Comp: 0.00
unclearmcp memory server
Vol: 90
CPC: $12.48
Comp: 13.00
unclearclaude code version
Vol: 2,400
CPC: $12.36
Comp: 0.00
unclearfree mcp servers
Vol: 260
CPC: $11.70
Comp: 0.00
purchase intentmcp protocol
Vol: 6,600
CPC: $10.94
Comp: 21.00
unclearmodel context protocol examples
Vol: 140
CPC: $10.81
Comp: 0.00
unclearbest mcp servers
Vol: 1,000
CPC: $10.59
Comp: 31.00
purchase intentmcp server ai
Vol: 590
CPC: $10.47
Comp: 0.00
unclearclaude code memory
Vol: 1,300
CPC: $10.06
Comp: 6.00
unclearmcp server market
Vol: 40
CPC: $10.03
Comp: 0.00
purchase intentmodel context protocol documentation
Vol: 260
CPC: $9.68
Comp: 0.00
unclear| Keyword | Volume | CPC | Competition | Intent |
|---|---|---|---|---|
| claude-mem | 3,600 | $43.57 | 0.00 | unclear |
| github mcp server claude code | 110 | $29.29 | 0.00 | unclear |
| openai mcp server | 210 | $28.62 | 0.00 | unclear |
| claude mem | 4,400 | $24.82 | 2.00 | unclear |
| mcp server | 60,500 | $17.88 | 33.00 | unclear |
| model context protocol server | 1,000 | $16.85 | 3.00 | unclear |
| cursor memory | 140 | $15.50 | 6.00 | unclear |
| claude code latest version | 1,300 | $15.07 | 0.00 | unclear |
| claude code extensions | 1,000 | $13.97 | 20.00 | purchase intent |
| model context protocol servers | 880 | $12.58 | 0.00 | unclear |
| mcp memory server | 90 | $12.48 | 13.00 | unclear |
| claude code version | 2,400 | $12.36 | 0.00 | unclear |
| free mcp servers | 260 | $11.70 | 0.00 | purchase intent |
| mcp protocol | 6,600 | $10.94 | 21.00 | unclear |
| model context protocol examples | 140 | $10.81 | 0.00 | unclear |
| best mcp servers | 1,000 | $10.59 | 31.00 | purchase intent |
| mcp server ai | 590 | $10.47 | 0.00 | unclear |
| claude code memory | 1,300 | $10.06 | 6.00 | unclear |
| mcp server market | 40 | $10.03 | 0.00 | purchase intent |
| model context protocol documentation | 260 | $9.68 | 0.00 | unclear |
V
What It All Means
Synthesis: which segments to target, what positioning angles work, how to price, and exactly what to do next.
11 — Strategic Verdict
Strategic Verdict
60,500
Monthly searches for 'mcp server'
$43.57
CPC for 'claude-mem' — highest in category
666K
Combined monthly visits to top 3 competitors
592
Memory MCP servers on PulseMCP
13
PMLL installs (vs 22.4K stars for agentmemory)
<$0.01
Anthropic Remember plugin per-session cost
The job-to-be-done — persistent AI coding agent memory — is thoroughly validated. 'claude code memory' generates 1,000 monthly searches at $20.61 CPC, 'claude-mem' commands $43.57 CPC, and the broader 'mcp server' ecosystem drives 60,500 searches/month [Source: keyword-report.md]. Competitors mem0 (388K visits/mo), Supermemory (174K visits/mo), and Zep/Graphiti (104K visits/mo) collectively attract 666K monthly visits, confirming massive market demand [Source: traffic-analysis.md]. However, PMLL faces a brutal competitive reality. The market has already consolidated around 4-5 well-resourced players: agentmemory (22.4K GitHub stars), Graphiti (26.5K stars), and mem0 (388K visits + VC funding) [Source: competition-analysis.md]. More critically, Anthropic has shipped its own 'Remember' plugin at <$0.01/session, creating a platform-native substitute that eliminates the core pain for Claude Code users [Source: web search]. With 592 memory MCP servers already listed on PulseMCP and only 13 installs on vibehackers, PMLL is attempting to enter a market that is rapidly moving from fragmented experimentation to winner-take-most consolidation.
The Context+ README backlink (1.9K stars) is PMLL's strongest and most unique asset. No other memory server has an embedded recommendation inside a complementary tool's documentation. However, this distribution channel converts at the referral-link level — a small percentage of Context+ users will click through, and a smaller percentage of those will install. At Context+'s scale (1.9K stars ≈ ~500-1,000 active users), this yields perhaps 5-15 installs/month at best [INFERRED]. This is consistent with the observed 13 total installs.
The strategic tension is clear: validated demand + excellent TTFV + unique distribution angle vs. late entry into a consolidating market with overwhelming competition. The idea is not fundamentally flawed — the job is real, the wedge is creative, and the pricing is market-consistent. But the window for a new entrant to build meaningful share has likely closed without a differentiated technical or distribution advantage that goes beyond 'complementary to Context+'.
12 — Customer Segments
Customer Segments
Context+ Power Users
Developers already using Context+ for codebase intelligence who discover PMLL via the README recommendation. They want to add session memory on top of their existing AST/semantic search setup. This is the only segment with a built-in acquisition channel.
WTP
$0 (free tier) to $9-12/mo (cloud sync)
Channel
Context+ README backlink → GitHub → npm install
Unit Econ
healthy
Grounding
GROUNDED
Evidence
- Context+ README documents PMLL as 'complementary server' [Source: idea.md, Distribution Strategy]
- Context+ has 1.9K GitHub stars, 161 forks, 12 contributors [Source: idea.md, Key Metrics]
- 13 existing PMLL installs likely originated from this channel [Source: idea.md, Key Metrics]
- 'context plus mcp' has 10 vol — minimal direct search [Source: keyword-metrics.csv]
Unit economics
CAC: $0
Zero CAC — organic referral from README placement. No paid acquisition needed. [Source: idea.md, Distribution]
AMPU: $9
PMLL proposed cloud tier $9-15/mo, midpoint $12, assume 2% conversion = $0.24 effective AMPPU across all users. For paying users only: $9/mo [Source: idea.md, Pricing]
Payback: 0 months
Point A → Point B
Point A: I already have Context+ for code intelligence, but my AI agent still forgets everything between sessions. I re-explain my project every morning.
Point B: My AI agent remembers my project architecture, past decisions, and coding preferences — it picks up exactly where we left off, with Context+ handling code search and PMLL handling memory.
Claude Code Memory Seekers
Developers actively searching for ways to give Claude Code persistent memory. They search for 'claude code memory', 'claude mem', 'claude code persistent memory' — the highest-CPC segment indicating strong purchase intent.
WTP
$0-19/mo based on competitor pricing (claude-mem free/cloud, mem0 $19/mo)
Channel
SEO for 'claude code memory' cluster + GitHub discovery + npm search
Unit Econ
risky
Grounding
GROUNDED
Evidence
- 'claude code memory': 1,000 vol, $20.61 CPC [Source: keyword-metrics.csv]
- 'claude-mem': 3,600 vol, $43.57 CPC [Source: keyword-metrics.csv]
- 'claude mem': 4,400 vol, $24.82 CPC [Source: keyword-metrics.csv]
- 'claude code persistent memory': 50 vol [Source: keyword-metrics.csv]
- SERP difficulty: 'claude mem' is Easy (4 weak spots), 'claude code memory' is Medium (3 weak spots) [Source: serp-weakness-report.md]
Unit economics
CAC: $687
CPC $20.61 / 3% conversion rate = $687 CAC. Organic SEO is the viable path — paid acquisition is uneconomical at this CPC. [Source: keyword-metrics.csv, 'claude code memory' CPC]
AMPU: $12
Midpoint of $9-15/mo paid tier [Source: idea.md, Pricing]. Comparable: Basic Memory $15/mo, MemPalace €10-15/mo [Source: competition-analysis.md]
Payback: 57 months
Point A → Point B
Point A: I use Claude Code daily but it has amnesia. Every new session starts blank. I've tried CLAUDE.md but it's limited to 200 lines and I have to maintain it manually.
Point B: I type 'npx pmll-memory-mcp' once and my Claude Code sessions automatically remember everything — project context, past decisions, my preferences. No manual maintenance.
MCP Server Explorers
Developers actively building their MCP server stack — searching for the best servers to add to Claude Code or Cursor. They discover memory servers as part of a broader MCP shopping experience.
WTP
$0 (most MCP servers are free) — discovery segment, not a buying segment
Channel
SEO for 'best mcp servers' + MCP marketplace directories (PulseMCP, mcpservers.org) + listicle placements
Unit Econ
risky
Grounding
GROUNDED
Evidence
- 'mcp server': 60,500 vol, $17.88 CPC [Source: keyword-metrics.csv]
- 'best mcp servers': 1,000 vol, $10.59 CPC [Source: keyword-metrics.csv]
- 'mcp marketplace': 1,300 vol, $6.93 CPC, Easy SERP difficulty [Source: keyword-metrics.csv, serp-weakness-report.md]
- 'mcp server list': 1,300 vol [Source: keyword-metrics.csv]
- 'free mcp servers': 260 vol, $11.70 CPC [Source: keyword-metrics.csv]
Unit economics
CAC: $353
CPC $10.59 / 3% conversion rate = $353 CAC for 'best mcp servers'. Organic listing in directories is zero-cost. [Source: keyword-metrics.csv]
AMPU: $0
This is a discovery/awareness segment — most will install free tier only. Monetization requires upsell to cloud sync. [INFERRED]
Payback: -1 months
Point A → Point B
Point A: I'm setting up my MCP stack and need a memory server. There are hundreds of options and I don't know which one to pick.
Point B: I found PMLL recommended by Context+ — a trusted source — and installed it in one command. It works alongside my other MCP servers seamlessly.
Multi-Tool AI Developers
Developers who use multiple AI coding tools (Claude Code + Cursor + Windsurf) and need cross-tool memory persistence. Their context is fragmented across tools.
WTP
$12-20/mo — willing to pay more for cross-tool capability
Channel
SEO for tool-specific keywords + tool comparison content + Reddit/community
Unit Econ
risky
Grounding
INFERRED
Evidence
- 'cursor memory': 140 vol, $15.50 CPC [Source: keyword-metrics.csv]
- 'windsurf memory': 50 vol [Source: keyword-metrics.csv]
- 'mcp servers cursor': 210 vol [Source: keyword-metrics.csv]
- claude-mem supports Claude Code, Codex, Gemini, Hermes, Copilot, OpenCode [Source: web search, claude-mem GitHub]
Unit economics
CAC: $517
CPC $15.50 / 3% conversion rate = $517 CAC for 'cursor memory'. [Source: keyword-metrics.csv]
AMPU: $15
Premium tier price point for cross-tool feature. Comparable: mem0 $19/mo [Source: competition-analysis.md]
Payback: 34 months
Point A → Point B
Point A: I switch between Claude Code and Cursor depending on the task. Each tool has its own memory silo — my AI agents don't share what they've learned across tools.
Point B: One unified memory layer that works across all my MCP-compatible tools. What Claude Code learned about my project, Cursor can use too.
Team-Scale Memory Users
Small teams (2-8 developers) who want shared AI memory across team members — so one developer's AI agent benefits from what another's learned about the codebase.
WTP
$20-79/mo per team based on mem0 pricing tiers
Channel
Content marketing targeting 'mcp memory server for teams' + comparison pages
Unit Econ
marginal
Grounding
HYPOTHESIS
Evidence
- Competitor pricing: mem0 Team $79/mo, Enterprise $249/mo [Source: competition-analysis.md]
- ContextForge MCP includes team features [Source: competition-analysis.md]
- 'Best MCP Memory Servers for Teams' article exists [Source: web search, contextcloud.pro]
- Web search revealed team memory as differentiator in 2026 comparisons [Source: web search]
Unit economics
CAC: $500
Estimated from general MCP server CPC range ($10-15) / 3% conversion. [INFERRED]
AMPU: $40
Midpoint between mem0 Team $79/mo and Basic Memory $15/mo for team tier [Source: competition-analysis.md]
Payback: 12 months
Point A → Point B
Point A: Each developer on our team has their own AI context silo. When someone learns something about the codebase with their AI agent, that knowledge dies with their session.
Point B: Our team's AI agents share a collective memory — code patterns, architecture decisions, and project context are available to everyone's AI assistant.
13 — Pivot Directions
Pivot Directions
Move to Higher-Level Job: Full 'AI Coding Context' Stack
product_expansion
Instead of competing as one of 592 memory servers, combine Context+ codebase intelligence + PMLL session memory + task planning into a single 'AI coding context' stack. The mutual credit relationship with Context+ is the foundation for a merged product.
Supporting data
- 'claude code plugins': 5,400 vol, $8.82 CPC — developers want complete plugin packages [Source: keyword-metrics.csv]
- 'mcp tools': 2,900 vol, $8.12 CPC — searching for tool bundles [Source: keyword-metrics.csv]
- Context+ already documents PMLL as complementary — the merger narrative is pre-established [Source: idea.md]
- No competitor currently bundles codebase intelligence + session memory as one product [Source: competition-analysis.md]
Own the 'MCP Marketplace' Discovery Opportunity
content_seo
Create a curated comparison site / directory for MCP memory servers. 'mcp marketplace' is Easy difficulty with 1,300 vol. Becoming the trusted guide to the fragmented memory server market builds distribution for PMLL.
Supporting data
- 'mcp marketplace': 1,300 vol, $6.93 CPC, Easy SERP difficulty (2 weak spots in top 5) [Source: keyword-metrics.csv, serp-weakness-report.md]
- 'best mcp servers': 1,000 vol, $10.59 CPC, Medium difficulty [Source: keyword-metrics.csv, serp-weakness-report.md]
- 'top 10 mcp servers': 30 vol [Source: keyword-metrics.csv]
- mcpmarket.com (PR 3.36) and mcpservers.org (PR 4.19) are current weak incumbents [Source: serp-weakness-report.md]
Target Cursor/Windsurf Users Underserved by Claude-Centric Solutions
market_segment
Most memory servers (claude-mem, Remember plugin) are Claude-centric. Cursor and Windsurf users are underserved. Position PMLL as the cross-tool memory server.
Supporting data
- 'cursor memory': 140 vol, $15.50 CPC — high CPC signals unmet need [Source: keyword-metrics.csv]
- 'mcp servers cursor': 210 vol, Medium SERP difficulty [Source: keyword-metrics.csv, serp-weakness-report.md]
- 'windsurf memory': 50 vol, Medium SERP difficulty [Source: keyword-metrics.csv, serp-weakness-report.md]
- Cursor has 1M+ users [Source: competition-analysis.md, Substitutes]
Benchmark-Led Differentiation
technical_moat
agentmemory won stars by publishing benchmarks (95.2% R@5 on LongMemEval). The market responds to measurable quality claims. PMLL should benchmark its Q-promise deduplication and decay scoring against established metrics.
Supporting data
- agentmemory achieved 22.4K stars partly through benchmark marketing [Source: competition-analysis.md]
- Evermind claims 93.05% LoCoMo and 83.00% LongMemEval-S scores [Source: web search]
- mem0 scores 49.0% on similar benchmarks — beatable [Source: web search]
- No PMLL benchmarks exist yet [Source: idea.md — no benchmark claims]
Exploit the 'claude mem' Easy SERP Win
seo_opportunity
The 'claude mem' and 'claude-mem' keywords (4,400 + 3,600 vol, $24-43 CPC) are Easy SERPs with massive opportunity scores. A well-optimized comparison page or alternative page could capture significant traffic.
Supporting data
- 'claude mem': 4,400 vol, $24.82 CPC, Easy (4 weak spots) — opportunity score 109.5 [Source: serp-weakness-report.md]
- 'claude-mem': 3,600 vol, $43.57 CPC, Easy (3 weak spots) — opportunity score 14,400 [Source: serp-weakness-report.md]
- claude-mem.ai has PR 3.17 — beatable [Source: serp-weakness-report.md]
- docs.claude-mem.ai has PR 2.69 [Source: serp-weakness-report.md]
B2B Team Memory Platform
B2B switch (Mechanic #8)
Pivot from individual developer tool to team-scale AI memory platform. Charge per-seat ($15-25/developer/mo) for shared team memory where one developer's AI learnings benefit the whole team. mem0 charges $79-249/mo for team tiers.
Validation test
Post a 'Team Memory for AI Coding Agents' concept page. Target small agencies (5-10 devs) via LinkedIn. 3+ demo requests in 30 days = proceed.
Enterprise 'AI Knowledge Continuity' Compliance Product
Upmarket shift (Mechanic #9)
Position AI agent memory as a compliance/governance requirement — companies need to know what their AI agents 'remember' and ensure sensitive code knowledge doesn't leak across projects. SOC2-compliant, audit-logged memory.
Validation test
Interview 5 engineering managers at regulated companies (fintech, healthcare) about AI agent memory governance concerns. 3+ express budget → proceed.
Memory-as-Infrastructure for MCP Server Builders
Low-level job across many graphs (Mechanic #12)
Instead of being a consumer-facing memory server, become the memory library that other MCP server developers embed. The 'SQLite of AI memory' — a library, not a product.
Validation test
Publish PMLL's memory graph as a standalone npm package. Track npm installs from non-PMLL packages over 60 days. 50+ dependent packages = viable.
14 — Messaging & Taglines
Messaging & Taglines
Your AI Agent Remembers Everything — Across Every Session
PMLL adds persistent memory to Claude Code, Cursor, and any MCP client. One command, zero config. Recommended by Context+ (1.9K★).
Target: Claude Code Memory Seekers
Channel: GitHub README, npm landing page
claude code memory (1,000 vol), claude code persistent memory (50 vol), session memory ai agent (seed)
The Memory Server Context+ Recommends
Context+ handles codebase intelligence. PMLL handles session memory. Together, your AI agent is fully context-aware — code search + persistent memory in two commands.
Target: Context+ Power Users
Channel: Context+ README, GitHub cross-referral
context plus mcp (10 vol), mcp complementary server (seed), mcp context server (10 vol)
Stop Re-Explaining Your Project to Claude Code
CLAUDE.md caps at 200 lines. PMLL has no limit. Automatic capture, intelligent decay, and smart retrieval — your agent starts every session fully informed.
Target: Claude Code Memory Seekers
Channel: SEO content targeting 'claude code memory', Reddit r/ClaudeAI
claude code memory (1,000 vol, $20.61 CPC), claude code auto memory (110 vol), claude code memory files (40 vol)
One Memory Layer. Every MCP Tool.
Works with Claude Code, Cursor, Windsurf, and any MCP-compatible client. Your AI agent's memory travels with you — not locked to one IDE.
Target: Multi-Tool AI Developers
Channel: SEO for 'cursor memory', 'mcp servers cursor'
cursor memory (140 vol, $15.50 CPC), mcp servers cursor (210 vol), windsurf memory (50 vol)
592 Memory Servers. Here's How to Choose.
The definitive comparison of MCP memory servers — benchmarks, pricing, setup complexity, and what actually works. By the team behind PMLL.
Target: MCP Server Explorers
Channel: SEO for 'best mcp servers', 'mcp marketplace'
best mcp servers (1,000 vol, $10.59 CPC), mcp marketplace (1,300 vol, $6.93 CPC), mcp server list (1,300 vol)
Taglines
“Never re-explain your project again.”
Friction point: developers waste 10-30 min/session re-establishing context [Source: idea.md]
For: Claude Code Memory Seekers
“Context+ for intelligence. PMLL for memory.”
Distribution positioning: complementary to Context+ [Source: idea.md, Distribution]
For: Context+ Power Users
“Your agent's memory, across every tool.”
Cross-tool gap: most memory servers are Claude-centric [Source: competition-analysis.md]
For: Multi-Tool AI Developers
“One command. Permanent memory.”
TTFV strength: npx pmll-memory-mcp [Source: idea.md, Wedge]
For: All segments
“Smart decay. No memory bloat.”
Friction point: context staleness and overflow [Source: section-friction_points.json]
For: Claude Code Memory Seekers
“The memory half of your MCP stack.”
Positioning: complementary infrastructure [Source: idea.md, Differentiation]
For: MCP Server Explorers
Communication Gaps
No comparison content for 'PMLL vs claude-mem' or 'PMLL vs agentmemory'
Create head-to-head comparison pages targeting the highest-CPC, easiest-to-rank keywords in the entire dataset. The 'claude-mem' SERP is beatable (PR 3.17).
'claude-mem' (3,600 vol, Easy SERP) and 'claude mem' (4,400 vol, Easy SERP) have no PMLL presence [Source: serp-weakness-report.md]
No benchmark data to support PMLL's technical claims
Run LongMemEval benchmarks and publish results. Even modest scores create a concrete talking point in a market where most servers have no benchmarks.
agentmemory publishes 95.2% R@5, Evermind publishes 93.05% LoCoMo — PMLL has zero published benchmarks [Source: competition-analysis.md, web search]
No content targeting 'how to' or tutorial keywords for MCP memory setup
Create a 'Getting Started with AI Memory for Coding' guide. Lower-volume but builds trust and captures problem-aware searchers.
'how to find mcp servers' (10 vol), 'mcp server examples' (880 vol, Hard) — tutorial content is dominated by high-authority sites [Source: keyword-metrics.csv, serp-weakness-report.md]
No presence on MCP marketplace directories (PulseMCP, mcpservers.org, mcpmarket.com)
Ensure PMLL is listed and well-described on all major MCP directories. This is free distribution in a discoverable channel.
These directories rank for 'mcp marketplace' (Easy SERP), 'mcp server list', 'best mcp servers' [Source: serp-weakness-report.md]
15 — Pricing Strategy
Pricing Strategy
Free (Open Source Core)
$0
MIT-licensed npm package, self-hosted
Free OSS is table stakes — every direct competitor offers it. Without a free tier, PMLL cannot compete for installs. The value of the free tier is distribution (npm installs, GitHub stars) that feeds the paid funnel.
Comparables
- agentmemory: free, MIT, 22.4K stars [Source: competition-analysis.md]
- Engram: free, MIT, 4.3K stars [Source: competition-analysis.md]
- Official MCP memory server: free [Source: competition-analysis.md]
- Anthropic Remember plugin: <$0.01/session [Source: web search]
Risk of remaining permanently free with no conversion. agentmemory has 22.4K stars and zero revenue. The free tier may be 'good enough' for 97-99% of users.
PMLL Cloud (Individual)
$12/month
Monthly subscription for cloud memory sync, cross-device persistence, and backup
Positioned at the low end of competitor pricing ($10-19/mo range). The $12 price point undercuts mem0 ($19) and Basic Memory ($15) while remaining above MemPalace (€10). Cloud sync is the standard monetization lever in this category.
Comparables
- Basic Memory Cloud: $15/mo (AGPL core) [Source: competition-analysis.md]
- MemPalace Pro: €10/mo [Source: competition-analysis.md]
- mem0 Starter: $19/mo [Source: competition-analysis.md]
- MemoryPlugin Pro: $120/year ($10/mo) [Source: web search]
High risk: conversion from free to paid is 1-3% in OSS dev tools. At 13 installs, even 3% conversion = 0.39 paying users. Need >500 free installs to sustain one developer's time.
PMLL Team
$25/month (up to 5 seats)
Monthly subscription for shared team memory, access controls, and admin dashboard
Priced significantly below mem0 Team ($79) to attract small teams (2-5 devs) who can't justify enterprise pricing. The team tier is a HYPOTHESIS — it requires significant product development and there's no validation that small teams want shared AI memory yet.
Comparables
- mem0 Team: $79/mo [Source: competition-analysis.md]
- MemPalace Power: €15/mo [Source: competition-analysis.md]
- Zep Cloud: starts at $125/mo [Source: competition-analysis.md]
Very high risk: team features don't exist yet, market demand is unvalidated, and the team sale requires a different go-to-market motion (decision-maker is tech lead, not individual dev).
16 — Prioritized Next Steps
Prioritized Next Steps
1
Test Anthropic's Remember plugin hands-on and document exactly what it does and doesn't do. Identify specific gaps PMLL fills that Remember doesn't. This is the #1 existential risk — if Remember covers the core job adequately, PMLL's value proposition collapses.
Remember plugin was found via web search but its capabilities are unverified. Before investing any more effort, confirm there's a gap to fill. [RAT #4]
Clear list of Remember gaps (or a KILL signal if no meaningful gaps exist). Required for all subsequent decisions.
claude code memory (1,000 vol, $20.61 CPC)2
Add UTM tracking to the Context+ README backlink and measure actual click-through rate over 4 weeks. This is the only validated distribution channel — need to know if it can scale.
13 installs after months of README presence could mean the channel is at steady state. Without data, all growth projections are fantasy. [RAT #1]
Weekly click count. If <20 clicks/week, Context+ README is insufficient as primary channel and a new distribution strategy is needed.
context plus mcp (10 vol)3
Create a 'PMLL vs claude-mem' comparison page optimized for 'claude mem' (4,400 vol, Easy SERP) and 'claude-mem' (3,600 vol, Easy SERP). These are the highest-opportunity keywords with the weakest competition.
claude-mem.ai has PR 3.17 — a well-optimized comparison page can rank. Combined 8,000 vol at $24-43 CPC represents the most accessible organic traffic in the entire keyword set. [Source: serp-weakness-report.md]
Page ranking in top 10 for 'claude mem' within 60 days. Target: 500+ organic visits/month driving 10-15 PMLL installs/month.
claude-mem (3,600 vol, $43.57 CPC, Easy difficulty)4
Run PMLL against LongMemEval benchmark and publish results. Benchmark marketing drove agentmemory to 22.4K stars. Without benchmarks, PMLL's Q-promise dedup and decay scoring claims are unverifiable.
agentmemory published 95.2% R@5. Evermind published 93.05% LoCoMo. mem0 scored 49%. Even a modest PMLL score (>60%) creates a concrete talking point. [RAT #3]
Published benchmark results. If >80% R@5: strong differentiation claim. If 50-80%: moderate. If <50%: need to improve core engine before marketing.
mcp memory server (90 vol, $12.48 CPC)5
List PMLL on all major MCP directories (PulseMCP, mcpservers.org, mcpmarket.com, Awesome Claude, claudemarketplaces.com). These are free distribution channels that rank for discovery keywords.
Zero-cost, zero-effort distribution. PulseMCP lists 592 memory servers — PMLL should be among them. Directory listings compound over time. [Source: serp-weakness-report.md]
Presence on 5+ directories within 1 week. Incremental discovery traffic. Baseline for measuring directory-driven installs.
mcp marketplace (1,300 vol, $6.93 CPC, Easy difficulty)6
Evaluate the 'Context+ / PMLL merged stack' pivot. If Context+ partnership is strong enough, propose combining into a single 'AI Coding Context Stack' that owns the higher-level job. This escapes the 592-server commoditization trap.
The standalone memory server market is consolidating around 3-4 winners. PMLL's best strategic asset is the Context+ relationship. A merged product competes at a different level entirely. [Pivot Direction #1]
Decision: merge with Context+ (higher-level job pivot) or remain standalone (niche memory server). Requires conversation with @drQedwards and Context+ maintainers.
claude code plugins (5,400 vol, $8.82 CPC)Disclaimer. This report is a directional validation tool, not a definitive assessment of success or failure. It combines publicly available data (SEO signals, competitor analysis, and observable market behavior) with structured reasoning to highlight potential risks, opportunities, and strategic paths. However, it does not capture all forms of demand — particularly behavior-driven, community-led, or discovery-based growth, which are common in developer tools and consumer products. Scores and conclusions should be interpreted as relative signals, not absolute judgments. Early-stage products often succeed despite weak measurable demand signals, especially when distribution, timing, or product experience create new behavior. This analysis is most useful for identifying assumptions to test — not for making final build-or-kill decisions. The only reliable validation comes from real user behavior (retention, engagement, and willingness to use the product repeatedly).
Ready to build this?
Deploy your app on Railway — the fastest way to go from idea to production.
Deploy on Railway →Comments
No comments yet. Be the first!