01
decision
Standardize on idempotent write endpoints
Source: architecture.md
MCP Memory Server in · shared project memory — local-first · offline-ready
MCP Memory Server in Tokyo
Stop running a toy JSON memory server. MemHub is a production MCP memory server on PostgreSQL + pgvector — isolated per org/project, audited, and ready for your whole team in one command.
Most MCP servers die on one laptop. MemHub runs the same MCP protocol on a real database with row-level security — one endpoint, one credential per project, every agent in sync.
Start free — get briefed in 2 min
Free for 1 project · No card · Self-host or we host · No external API
acme/mcp-memory-server
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
WHY IT MATTERS HERE
Why Tokyo engineering teams choose MemHub
In Tokyo, 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.
- Built for Tokyo: enterprise modernization programs at national scale.
- 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
MCP Memory Server in Tokyo, without the trade-offs.
01
One proxy, every client
memhub serve bridges any MCP client over stdio. Zero daemons on the laptop, zero workflow change.
02
Queue when offline
Local SQLite outbox keeps memory writable during outages — syncs automatically when you’re back.
03
Prove who did what
Actor, action, and target on every admin change — ready for security review and audits.
04
No pasted secrets
mh login via browser with scoped, revocable credentials — a lost laptop loses access instantly.
05
Isolated by default
Row-level security per org/project — a bug in one repo can’t read another’s memory. Safe for the whole team.
06
Run on PostgreSQL you trust
pgvector-ready schema, versioned migrations, Docker/Easypanel. Backups with pg_dump — no exotic stack.
The honest comparison.
No feature-matrix gymnastics — just what changes the week you adopt MemHub.
| 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.
repository terminal
$ npm install --global @simplexlat/memhub
$ memhub login
✓ project resolved · context ready · memory synchronized
Questions, answered straight.
Can I self-host the MCP memory server?
Yes. The repository includes Docker Compose and Easypanel templates for PostgreSQL 16 with pgvector, plus migration and seed commands.
Which clients can connect?
Any MCP-compatible client: Claude Code, Cursor, Codex CLI, Gemini-based IDEs such as Antigravity, Windsurf, Cline, or a generic JSON config.
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
MCP Memory Server in OsakaMCP Memory Server in San FranciscoMCP Memory Server in New York CityMCP Memory Server in AustinMCP Memory Server in SeattleMCP Memory Server in BostonMCP Memory Server in ChicagoMCP Memory Server in DenverMCP Memory Server in Los AngelesMCP Memory Server in AtlantaMCP Memory Server in MiamiMCP Memory Server in Dallas
EXPLORE OTHER USE CASES
AI Agent Memory
Give every AI coding agent a persistent, team-wide memory.
Claude Code Memory
Claude Code memory that survives sessions and reaches the whole team.
Cursor Memory
Carry Cursor context across sessions, machines, and teammates.
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