01
decision
Standardize on idempotent write endpoints
Source: architecture.md
MCP Memory Server across · shared project memory
MCP Memory Server across Ireland
The Model Context Protocol made tools portable; MemHub makes memory portable between them. One server, one credential per project, and every agent reads the same versioned knowledge graph of your codebase.
MemHub ships a production-grade MCP memory server backed by PostgreSQL and pgvector: multi-tenant, access-controlled, auditable, and reachable by every Model Context Protocol client your team runs.
Create your shared memory
Free Community tier. Self-hosted or hosted. No external embedding API required.
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
LOCAL FIT
Why Ireland engineering teams choose MemHub
Across Ireland, software teams ship faster when their tools share one memory instead of three silos. Distributed squads stay aligned because every session opens with the same briefing.
Teams operating under GDPR can point at a concrete architecture instead of promises.
- Built for Ireland: an EU headquarters for many global engineering organizations.
- Data residency you control — run MemHub on infrastructure inside Ireland 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.
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 across Ireland, without the trade-offs.
01
Offline outbox
A local SQLite write-ahead queue keeps memory available and consistent during outages.
02
Audit trail
Actor, action, and target recorded for every administrative change — enterprise-review friendly.
03
Browser login
`mh login` authorizes a machine through the browser with scoped, revocable credentials — no pasted secrets.
04
Multi-tenant by design
Row-level security separates organizations and projects; credentials are scoped, hashed, and revocable.
05
PostgreSQL durability
pgvector-ready schema, migration tooling, and Docker/Easypanel deployment recipes included.
06
Stdio proxy simplicity
`memhub serve` bridges any MCP client to the cloud memory with zero infrastructure on the laptop.
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.
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.
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.
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 across the United StatesMCP Memory Server across CanadaMCP Memory Server across the United KingdomMCP Memory Server across GermanyMCP Memory Server across FranceMCP Memory Server across SpainMCP Memory Server across PortugalMCP Memory Server across ItalyMCP Memory Server across the NetherlandsMCP Memory Server across BelgiumMCP Memory Server across SwitzerlandMCP Memory Server across Austria
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