01
decision
Standardize on idempotent write endpoints
Source: architecture.md
Cursor Memory in Montevideo · shared project memory
Cursor Memory in Montevideo
Rules files tell Cursor what to do; MemHub remembers why. Rejected libraries, migration constraints, incident lessons — the reasoning that makes suggestions correct — persist beyond any single editor session.
For teams standardized on Cursor, MemHub adds the missing organizational layer: memory scoped per project, searchable by everyone, and identical whether the question comes from Cursor, a terminal agent, or the web portal.
Create your shared memory
Free Community tier. Self-hosted or hosted. No external embedding API required.
acme/cursor-memory
synchronizedcontext/main
memories 41
pinned 6
contributors 9
BRIEFING FOR NEW SESSION
What changed since your last pull
02
pattern
Repository layer owns every database transaction
Source: pull request #214
03
bugfix
Refresh tokens rotate atomically under load
Source: auth/session.ts
Claude Code
Cursor
Windsurf
LOCAL FIT
Why Montevideo engineering teams choose MemHub
In Montevideo, software teams ship faster when their tools share one memory instead of three silos. Mixed toolchains stop fragmenting knowledge across vendor-specific stores.
Every entry carries authorship and version history, which keeps both humans and auditors comfortable.
- Montevideo: connect Claude Code, Cursor, Windsurf, Cline, Codex CLI, or Antigravity to one shared memory. It also plugs into any CLI that speaks MCP or reads a JSON config.
- Local-first writes keep sessions productive through outages and travel.
- One command onboards the whole team: memhub login, then connect for Claude Code, Cursor, Windsurf, Cline, Codex CLI, or any JSON client.
UNIVERSAL COMPATIBILITY
Plugs into any CLI or development tool you use.
If it speaks MCP or reads a JSON config, MemHub plugs in. One command wires the majors; everything else joins as a generic client.
- 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 in Montevideo, without the trade-offs.
01
Cross-tool parity
The same memory feeds Claude Code and Codex CLI, keeping mixed-tool teams consistent.
02
Ranked retrieval
Agents pull relevant memories by topic and recency instead of swallowing the full history.
03
Access control
Per-project credentials ensure contractors and new hires see exactly the projects they should.
04
Web portal
Browse, pin, edit, and audit the same memories from a clean dashboard — no lock-in to one editor.
05
Complements .cursor/rules
Keep tactical rules in-repo; move durable decisions and rationale into shared memory both humans and agents query.
06
Cross-session continuity
Context written yesterday is briefed today — across chats, worktrees, and machines.
The honest comparison.
No feature-matrix gymnastics — just what changes the week you adopt MemHub.
| Status quo | With MemHub |
|---|---|
| Context lives in heads and DMs | Memory is structured, shared, and searchable |
| Every agent re-learns the repo | Sessions open pre-briefed with only what changed |
| Rules files cap out at ~2k tokens | Unbounded versioned history stays one query away |
Connect the tools already in your repository.
One command injects configuration for Claude Code, Cursor, Codex CLI, Google Antigravity, Windsurf, Cline, or any JSON MCP client.
repository terminal
$ npm install --global @simplexlat/memhub
$ memhub login
✓ project resolved · context ready · memory synchronized
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.
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.
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.
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.
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.
MORE LOCATIONS
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 Diego
EXPLORE OTHER USE CASES
AI Agent Memory
Give every AI coding agent a persistent, team-wide memory.
MCP Memory Server
A hosted MCP memory server your whole team connects to in one command.
Claude Code Memory
Claude Code memory that survives sessions and reaches the whole team.
Codex CLI Memory
Persistent context for Codex CLI — personal today, shared tomorrow.
Cross-Agent Memory
One memory behind Claude Code, Cursor, Codex CLI, and Antigravity.
Developer Knowledge Base
A living knowledge base that writes itself while your team codes.
Self-Hosted AI Memory
Run the entire memory stack on your own PostgreSQL — nothing leaves.
Coding Agent Context
Context engineering for coding agents — brief, don’t dump.
Engineering Decision Log
An ADR habit your team will actually keep — logged by the agents doing the work.
Agent Memory Database
A real database behind agent memory — PostgreSQL, pgvector, row-level security.
Windsurf Memory
Persistent Windsurf context shared with every other agent on the team.
Cline Memory
Give Cline a memory that survives tasks, machines, and teammates.
Copilot Team Memory
What Copilot’s custom instructions can’t hold, MemHub remembers.
Antigravity & Gemini Memory
Persistent context for Google Antigravity, Gemini CLI, and the agents around them.
THE NEXT SESSION STARTS HERE