Cursor Memory across Singapore · shared project memory — local-first · offline-ready

Cursor Memory across Singapore

Teams on Cursor stay aligned without extra docs. One searchable memory per project, identical from Cursor, Claude Code, or the web portal. Free to start, offline-ready.

Keep .cursor/rules for steering, move durable reasoning to shared memory. Ranked retrieval, scoped access, one-command MCP setup — ship faster without re-explaining.

Start free — get briefed in 2 min

Free for 1 project · No card · Self-host or we host · No external API

acme/cursor-memory

synchronized

context/main

memories 41

pinned 6

contributors 9

BRIEFING FOR NEW SESSION

What changed since your last pull

3 new

decision

Standardize on idempotent write endpoints

Source: architecture.md

pattern

Repository layer owns every database transaction

Source: pull request #214

bugfix

Refresh tokens rotate atomically under load

Source: auth/session.ts

Claude Code

Cursor

Windsurf

WHY IT MATTERS HERE

Why Singapore engineering teams choose MemHub

Across Singapore, software teams ship faster when their tools share one memory instead of three silos. New engineers ramp in days because precedent is searchable, not oral history.

Teams operating under PDPA can point at a concrete architecture instead of promises.

Built for Singapore: Southeast Asia’s regional engineering headquarters.
Data residency you control — run MemHub on infrastructure inside Singapore or let us host it.
One command onboards the whole team: memhub login, then connect for Claude Code, Cursor, Windsurf, Cline, Codex CLI, or any JSON client.

Start free — 2 min1 project free · no card required Guided demo20 min · see your repo remembered Self-host it myselfDocker + pgvector · you own the data

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 across Singapore, without the trade-offs.

See only what you should

Per-project credentials — contractors and new hires see exactly scoped projects.

Browse without the terminal

Web portal to pin, edit, and audit the same corpus — no lock-in to one editor.

Stop rewriting rules

Keep tactical .cursor/rules in-repo — move durable why behind them into queryable shared memory.

Fresh chat, full context

Yesterday’s decisions brief today’s Cursor New Chat — across chats, worktrees, and machines.

No silos between tools

Same memory feeds Claude Code and Codex — mixed-tool teams stay consistent.

Relevant, not everything

Ranked retrieval by topic/recency — agents get the few memories that matter, not a dump.

The honest comparison.

No feature-matrix gymnastics — just what changes the week you adopt MemHub.

Start free — 2 min Talk to the team

Without MemHub	With MemHub
Context lives in heads and DMs → onboarding takes days	Structured, searchable memory → new dev/agent productive in minutes
Every agent re-learns the repo from scratch	Sessions open pre-briefed with only what changed — zero re-explaining
Rules files cap out at ~2k tokens	Unbounded versioned history stays one query away — never cap again
Decisions re-litigated, bugs re-introduced	Pinned invariants prevent regressions — agents respect past calls

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.

Start free — 2 min Talk to the team

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 across the United States Cursor Memory across Canada Cursor Memory across the United Kingdom Cursor Memory across Ireland Cursor Memory across Germany Cursor Memory across France Cursor Memory across Spain Cursor Memory across Portugal Cursor Memory across Italy Cursor Memory across the Netherlands Cursor Memory across Belgium Cursor Memory across Switzerland

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 — 2 MIN SETUP

Stop rebuilding context.
Start shipping faster.

Create workspace — free