What changed
FACT: A team founder publicly described (Ask HN) that two cofounders each run local Claude Code agents whose accumulated context (strategy, customer notes, decisions) is trapped per-machine and drifting, with only hacky workarounds like a shared Google Drive folder (https://news.ycombinator.com/item?id=48848840). FACT: The Claude Code ecosystem is expanding beyond Anthropic's API — Ollama now exposes Anthropic-API-compatible endpoints so Claude Code works with local models (https://ollama.com/blog/claude). FACT: Google is moving agent plumbing (background tasks, remote MCP) into the managed Gemini API (https://blog.google/innovation-and-ai/technology/developers-tools/expanding-managed-agents-gemini-api/), signaling providers absorbing agent infrastructure.
Why now
Claude Code adoption is growing fast and multi-person teams are hitting the memory-silo wall now; MCP is a stable, documented integration surface, so a remote memory MCP server is a small, well-scoped build today. HYPOTHESIS: the window is short — provider-hosted agent infra (as Gemini's managed-agents move shows) suggests Anthropic may ship native team memory, which would crush a thin third-party layer.
Converging signals
(1) PAIN: concrete team-agent-memory complaint with sync conflicts, no history, no shared/private boundary (HN 48848840). (2) Ecosystem breadth: Claude Code now runs against local models via Anthropic-compatible APIs, widening the user base a backend-agnostic memory layer could serve (ollama.com/blog/claude). (3) Platform direction: providers are hosting agent orchestration and remote MCP natively (Google blog), which both validates remote-MCP architecture and threatens third-party middleware.
Customer pain
FACT (single source): cofounders each accumulate agent context locally; it drifts, conflicts, has no history, and there is no way to share a subset while keeping private notes separate; current workaround is a Google Drive folder (HN 48848840). HYPOTHESIS: this pain generalizes to many 2-10 person Claude Code teams — plausible but NOT proven by the supplied evidence; there is exactly one complaint and zero hiring/spend signals in demand_evidence.
Who pays
HYPOTHESIS: technical founders and small dev teams (2-10 seats) already paying $100-200/mo/person for Claude Max — they have budget and card-on-file behavior. No FORCED BUYER exists; no hiring/spend evidence was provided, so willingness to pay is unproven. Developers in this segment habitually expect memory MCP servers to be free/open-source, which is the core monetization risk.
Solved today
FACT: shared Google Drive folder of markdown context files (cited in HN thread). Also (general knowledge, not from supplied sources): checked-in CLAUDE.md files, git repos of notes, and open-source memory MCP servers (Anthropic's reference memory server, mem0/OpenMemory, Letta, Zep) that are single-user-oriented.
Why current solutions are bad
FACT (from HN post): sync conflicts, no version history, no shared-vs-private partition, silent drift between machines. Git-based sharing forces all-or-nothing sharing and manual merges; existing memory MCP servers are mostly single-user local stores without team ACLs or conflict resolution.
Proposed product
A remote MCP memory server: Postgres-backed store with (a) team namespace + per-user private namespace, (b) versioned entries with history/rollback, (c) last-write-wins + human-readable diff review for conflicts, (d) selective share command ('promote this memory to team'), (e) works with any Anthropic-API-compatible client including local-model setups. Ship an open-source self-host core + hosted sync as the paid tier.
MVP version
1-2 weeks solo: FastAPI + Postgres remote MCP server exposing memory_read/memory_write/memory_promote/memory_history tools, API-key auth per user, team/private partitions, simple web viewer. Charles already runs FastAPI+Postgres+MCP-adjacent infrastructure (the Convergence stack), so this is squarely in-stack. Dogfood on his own multi-agent setup immediately.
30-day build
Week 1-2 build MVP; week 2 answer the HN thread with a working demo and post 'Show HN'; list on MCP directories (mcp.so, Smithery, PulseMCP); recruit 10-20 free design partners from HN/r/ClaudeAI/Discord; instrument which features (history, private partition, promote) get used.
60-day build
Add hosted tier with Stripe ($15/seat/mo, team plan $49/mo up to 5 seats); add conflict-diff UI and encrypted-at-rest option (teams will worry about strategy/customer notes in a third-party store); convert 3-5 design-partner teams to paid; publish 'how we share Claude Code memory across a team' content targeting the exact search/complaint language.
90-day revenue plan
Target: 10-20 paying teams ≈ $500-1,500 MRR. HYPOTHESIS — that is a modest ceiling and it is NOT cash-in-30-days; realistic first revenue is day 45-60. If <5 teams pay by day 75, kill and open-source fully for reputation.
Distribution path
Direct answer in the originating HN thread, Show HN, MCP server directories, r/ClaudeAI and Claude Discord, SEO on 'share Claude Code context across team'. No enterprise sales needed; self-serve. Weakness: discovery depends on Anthropic-ecosystem channels he doesn't control.
Pricing hypothesis
Free self-host/single-user; $15/seat/mo hosted sync or $49/mo team-of-5; annual discount. Per-seat because value scales with team size. HYPOTHESIS: dev willingness to pay for memory infra is unproven; open-source alternatives cap pricing power.
Technical difficulty
Low-moderate for MVP (CRUD + auth + MCP protocol + versioning). Real difficulty is in trust (holding other companies' strategy notes) and in conflict-resolution UX — merge semantics for free-text memory are genuinely hard to do better than 'last write wins + history'.
Legal / regulatory risk
Low regulatory risk, but the product stores customers' confidential business context — a breach is existential for trust. Needs clear DPA-lite terms and encryption; no licenses/permits involved.
Platform dependency
HIGH and this is the main kill risk: the product exists only inside the Claude Code/MCP ecosystem, and Anthropic shipping native team/shared memory (plausible given the provider trend shown by Gemini's managed agents) would erase the standalone value overnight. Mitigation: backend-agnostic MCP works with any client (including Ollama-backed setups), but the buyer pool is still Anthropic-centric.
Founder fit
Moderate. Fits Charles's stack (Python/FastAPI/Postgres, MCP, AI workflows, fast prototyping, demonstrated-value selling, no enterprise sales) and he is a heavy Claude Code user who can dogfood. BUT it is NOT his proven regulatory-filing shape: there is no mandate, no forced filer, no per-transaction toll booth — so his strongest, demonstrated edge (FMCSA ELDT-style government-portal monetization) is unused here.
Breakout potential
If MCP memory becomes standard team infra, this could grow into the 'shared brain' layer for all agent tooling (cursor/Gemini CLI/local models) — real but speculative upside; more likely outcome is a niche $1-3k MRR tool or acqui-absorption by platform features.
Final recommendation
CONDITIONAL PASS — do not commit the 90-day cash plan to this. The pain is real but proven at n=1, spend is unproven, and platform risk is severe. Worth a strictly time-boxed 2-week experiment ONLY because the MVP is nearly free for Charles to build on his existing stack: build, answer the HN thread, and demand 5 teams that will pay within 30 days of the demo. If that bar isn't met, open-source it for reputation and redirect to a forced-buyer (government-mandate) opportunity, which is his proven, higher-fit shape.
Next action
Reply to HN thread 48848840 (and DM the poster) with a concrete offer: 'I'll build the shared/private MCP memory sync — will you pay $49/mo for it?' Pre-sell 5 teams before writing more than the 2-week MVP.