01
decision2m
Usar bloqueos consultivos en PostgreSQL
Fuente: Nelson · architecture.md
CURSOR AI MEMORY · AVAILABLE NOW
Cursor Memory for engineering teams
Stop paying the New Chat tax in Cursor. Rules steer one editor; MemHub remembers why — rejected libs, migration constraints, incident lessons — and briefs every new Cursor chat automatically.
N
Nelson · Founder, MemHub at Simplex.lat
Simplex.lat · Quito, Ecuador ·
Written and verified by Nelson at Simplex.lat (Quito, Ecuador) — sources checked August 2026.
Local-first · Offline readySincronización multiagenteSetup en 2 min
Start free — get briefed in 2 min
Free for 1 project · No card · Self-host or we host · No external API
acme/cursor-memory
synchronizedcontext/main
memorias 41
reglas fijadas 6
colaboradores 9
BRIEFING FOR NEW SESSION
What changed since your last pull
02
pattern18m
Los errores de API siguen RFC 9457
Fuente: Maya · PR #184
03
bugfix1h
Los refresh tokens rotan atómicamente
Fuente: Codex CLI · auth/session.ts
Claude Code
Cursor
Codex CLI
THE MECHANISM
Write once. Every session remembers.
Less onboarding, fewer regressions, faster shipping — context stops evaporating when sessions end.
01
You keep coding
Decisions auto-captured where you work — terminal, PR, editor. No extra docs, no context-switching.
02
MemHub does the plumbing
Local SQLite outbox first, then project-scoped sync with provenance (who, when, why). Works offline.
03
Next session starts ahead
Every teammate and agent opens pre-briefed with only what changed since their last pull.
UNIVERSAL COMPATIBILITY
Plugs into any CLI, IDE, or AI coding agent.
If it speaks MCP or reads a JSON config, MemHub plugs in. One command wires your editors and terminals without friction.
- Claude Code
- Cursor
- Windsurf
- Cline
- Codex CLI (GPT)
- GitHub Copilot
- Google Antigravity
- Gemini CLI
- Aider
- OpenCode
- CI bots via REST
WHAT YOU GET
Cursor Memory: specific benefits for your team
01
Stop rewriting rules
Keep tactical .cursor/rules in-repo — move durable why behind them into queryable shared memory.
02
Fresh chat, full context
Yesterday’s decisions brief today’s Cursor New Chat — across chats, worktrees, and machines.
03
No silos between tools
Same memory feeds Claude Code and Codex — mixed-tool teams stay consistent.
04
Relevant, not everything
Ranked retrieval by topic/recency — agents get the few memories that matter, not a dump.
05
See only what you should
Per-project credentials — contractors and new hires see exactly scoped projects.
06
Browse without the terminal
Web portal to pin, edit, and audit the same corpus — no lock-in to one editor.
The honest comparison.
No feature-matrix gymnastics — just what changes the week you adopt MemHub.
| Feature | MemHub | Mem0 | Supermemory | Ideal For |
|---|---|---|---|---|
| Scope | Organization → Project → Member, shared across every agent | Per-user graph, not team-scoped | Per-user vault with sharing on request | Teams that need one truth across tools |
| Storage | PostgreSQL 16 + pgvector, versioned & queryable | Vector graph on managed infra | Hosted cloud store, limited export | Teams that need SQL, backups and audit |
| Tenancy & RLS | Row-level security inside the DB, enforced per project | Application-level isolation | Workspace isolation, no RLS | GDPR / SOC-2 reviews |
| Self-host | Docker/Easypanel recipe included, same MCP + REST | Open-source self-host possible, different ops | Cloud-only | Data-residency and on-prem requirements |
| Offline & sync | Local SQLite outbox, incremental deltas by sequence | Online-first sync | Online-first, no local outbox | Flaky networks, planes and VPN gaps |
| Pricing model | Community free (1 project) · Team $29 · self-host unlimited | Free tier + usage billing | Free tier + pay-per-seat | Trying without procurement |
Keep your stack. Add shared memory.
One command for Claude Code, Cursor, Codex, Windsurf, Cline or any MCP client. No new editor. Setup in 2 minutes, works offline.
memhub-cli · preview
Click tabs to simulateSimulate CLI
$
memhub save --type decision "Usar bloqueos consultivos en Postgres" -m "Evita colisiones concurrentes en el outbox"stdout · [mem_save]12ms
[detect] Contexto resuelto: acme/payments-api
[sqlite] Guardando en outbox local (~/.memhub/outbox.db)...
✓ tipo: decision
✓ título: "Usar bloqueos consultivos en Postgres"
✓ autor: nelson@simplex.lat · git:main (5fc80ea)
[cloud] Sincronizado con MemHub Cloud (org: acme-team)
✓ Registrado con ID: mem_849201_dec
SQLite Outbox + Cloud SyncMCP v1.0
Questions, answered straight.
Does MemHub replace .cursorrules?
No. Rules remain the right place for always-on steering. MemHub holds versioned team knowledge — decisions, constraints, postmortems — that rules files were never shaped to carry. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.
How does Cursor connect to it?
Through the Model Context Protocol: add the memhub entry to your MCP configuration once (the connect command does it for you) and restart Cursor. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.
What happens when our connection drops?
Nothing interrupts the work. Writes commit to the local SQLite outbox and synchronize automatically when the shared service is reachable again. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.
Can we try it without sending data anywhere?
Yes — the local engine works fully offline, and the self-hosted stack keeps even the shared layer on your own PostgreSQL. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.
How much does it cost?
A Community tier is free, and the Team plan adds multi-project contexts, seats, and higher synchronization limits. Self-hosting is unlimited. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.
COUNTRIES · Regional Deployments
Cursor Memory across United StatesCursor Memory across CanadaCursor Memory across United KingdomCursor Memory across IrelandCursor Memory across GermanyCursor Memory across FranceCursor Memory across SpainCursor Memory across PortugalCursor Memory across ItalyCursor Memory across NetherlandsCursor Memory across BelgiumCursor Memory across SwitzerlandCursor Memory across AustriaCursor Memory across SwedenCursor Memory across NorwayCursor Memory across DenmarkCursor Memory across FinlandCursor Memory across EstoniaCursor Memory across PolandCursor Memory across CzechiaCursor Memory across RomaniaCursor Memory across MexicoCursor Memory across BrazilCursor Memory across ArgentinaCursor Memory across ChileCursor Memory across ColombiaCursor Memory across PeruCursor Memory across UruguayCursor Memory across Costa RicaCursor Memory across EcuadorCursor Memory across PanamaCursor Memory across GuatemalaCursor Memory across El SalvadorCursor Memory across Dominican RepublicCursor Memory across ParaguayCursor Memory across AustraliaCursor Memory across New ZealandCursor Memory across JapanCursor Memory across South KoreaCursor Memory across SingaporeCursor Memory across IndiaCursor Memory across United Arab EmiratesCursor Memory across IsraelCursor Memory across South AfricaCursor Memory across NigeriaCursor Memory across KenyaCursor Memory across PhilippinesCursor Memory across VietnamCursor Memory across England
US STATES · Regional Deployments
Cursor Memory in CaliforniaCursor Memory in TexasCursor Memory in New York StateCursor Memory in FloridaCursor Memory in Washington StateCursor Memory in MassachusettsCursor Memory in ColoradoCursor Memory in IllinoisCursor Memory in GeorgiaCursor Memory in ArizonaCursor Memory in North CarolinaCursor Memory in UtahCursor Memory in OregonCursor Memory in VirginiaCursor Memory in New JerseyCursor Memory in PennsylvaniaCursor Memory in MichiganCursor Memory in TennesseeCursor Memory in MinnesotaCursor Memory in OhioCursor Memory in NevadaCursor Memory in Maryland
PROVINCES & REGIONS · Regional Deployments
CITIES & TECH HUBS · Regional Deployments
Cursor Memory in San FranciscoCursor Memory in New York CityCursor Memory in AustinCursor Memory in SeattleCursor Memory in BostonCursor Memory in ChicagoCursor Memory in DenverCursor Memory in Los AngelesCursor Memory in AtlantaCursor Memory in MiamiCursor Memory in DallasCursor Memory in San DiegoCursor Memory in PortlandCursor Memory in PhoenixCursor Memory in PhiladelphiaCursor Memory in NashvilleCursor Memory in MinneapolisCursor Memory in RaleighCursor Memory in Salt Lake CityCursor Memory in DetroitCursor Memory in TorontoCursor Memory in VancouverCursor Memory in MontrealCursor Memory in LondonCursor Memory in ManchesterCursor Memory in EdinburghCursor Memory in DublinCursor Memory in BerlinCursor Memory in MunichCursor Memory in HamburgCursor Memory in ZurichCursor Memory in GenevaCursor Memory in ViennaCursor Memory in ParisCursor Memory in LyonCursor Memory in AmsterdamCursor Memory in RotterdamCursor Memory in BrusselsCursor Memory in MadridCursor Memory in BarcelonaCursor Memory in ValenciaCursor Memory in MálagaCursor Memory in SevilleCursor Memory in BilbaoCursor Memory in ZaragozaCursor Memory in MurciaCursor Memory in Palma de MallorcaCursor Memory in Las Palmas de Gran CanariaCursor Memory in LisbonCursor Memory in PortoCursor Memory in MilanCursor Memory in RomeCursor Memory in StockholmCursor Memory in CopenhagenCursor Memory in OsloCursor Memory in HelsinkiCursor Memory in TallinnCursor Memory in WarsawCursor Memory in KrakówCursor Memory in PragueCursor Memory in BucharestCursor Memory in Mexico CityCursor Memory in GuadalajaraCursor Memory in MonterreyCursor Memory in QuerétaroCursor Memory in PueblaCursor Memory in TijuanaCursor Memory in MéridaCursor Memory in São PauloCursor Memory in Rio de JaneiroCursor Memory in Buenos AiresCursor Memory in CórdobaCursor Memory in RosarioCursor Memory in MendozaCursor Memory in SantiagoCursor Memory in ValparaísoCursor Memory in ConcepciónCursor Memory in BogotáCursor Memory in MedellínCursor Memory in CaliCursor Memory in BarranquillaCursor Memory in QuitoCursor Memory in GuayaquilCursor Memory in LimaCursor Memory in ArequipaCursor Memory in MontevideoCursor Memory in AsunciónCursor Memory in San JoséCursor Memory in Panama CityCursor Memory in Guatemala CityCursor Memory in San SalvadorCursor Memory in Santo DomingoCursor Memory in SydneyCursor Memory in MelbourneCursor Memory in BrisbaneCursor Memory in PerthCursor Memory in AucklandCursor Memory in TokyoCursor Memory in OsakaCursor Memory in SeoulCursor Memory in SingaporeCursor Memory in BengaluruCursor Memory in HyderabadCursor Memory in PuneCursor Memory in MumbaiCursor Memory in Delhi NCRCursor Memory in DubaiCursor Memory in Tel AvivCursor Memory in ManilaCursor Memory in Ho Chi Minh CityCursor Memory in Hong KongCursor Memory in TaipeiCursor Memory in Kuala LumpurCursor Memory in JakartaCursor Memory in BangkokCursor Memory in JohannesburgCursor Memory in Cape TownCursor Memory in LagosCursor Memory in Nairobi
GUIDES, COMPARISONS & PLAYBOOKS
Mem0 Alternative for Teams — MemHub
Best MCP Memory Servers for Teams (2026)
CLAUDE.md vs Shared Team Memory — When You Need Both
How to Share AI Coding Context Across Your Team
Agent Memory Playbook for Agile Teams (2026)
Mem0 vs MemHub: Team AI Memory Compared Guide
Supermemory vs MemHub: Team AI Memory Compared Guide
Letta vs MemHub: Team AI Memory Compared Guide
Cognee vs MemHub: Team AI Memory Compared Guide
Zep vs MemHub: Team AI Memory Compared Guide
Start free — 2 min1 project free · no card requiredGuided demo20 min · see your repo rememberedSelf-host it myselfDocker + pgvector · you own the data
THE NEXT SESSION STARTS HERE — 2 MIN SETUP