MCP MEMORY SERVER · AVAILABLE NOW

MCP Memory Server in Berlin

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.

N

Nelson · Founder, MemHub at Simplex.lat

Simplex.lat · Quito, Ecuador ·

Published by MemHub at Simplex.lat. Product limits come from the current plans; validate capabilities in your own pilot.

Local-first · OfflineSin pérdida de contextoSetup 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/mcp-memory-server
synchronized

context/main

memorias 41

fijadas 6

autores 9

BRIEFING FOR NEW SESSION

What changed since your last pull

3 new
01
decision2m

Usar bloqueos consultivos en PostgreSQL

Fuente: Nelson · architecture.md

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

Definition

What is MCP Memory Server in Berlin?

MCP Memory Server is the durable project memory that survives restarts, device switches and session closes so agents inherit what humans already decided. Teams in Berlin run MemHub on PostgreSQL 16 with pgvector and row-level security, giving every agent the same cited context without vendor lock-in or re-explaining.

Team plan at a glance

$29

Team per workspace per month (USD)

Team plan price; review current terms before subscribing. This is not a savings estimate.

According to MemHub pricing →

5

Seats included in Team

Share decisions with authorized teammates. Shared memory is not a replacement for live collaborative chat.

According to MemHub pricing →

20

Projects included in Team

Configure project scope and test what each user can retrieve before connecting sensitive repositories.

According to MemHub pricing →

How MemHub delivers MCP Memory Server without trade-offs

MemHub delivers MCP Memory Server in Berlin by writing first to a local SQLite outbox and then syncing incremental deltas by monotonic sequence, so flaky VPNs never block work. According to the Princeton GEO study, citing sources lifts AI-answer visibility by up to 40%, which structured, provenance-rich memories are built to earn.

Provisioning is one command: memhub login then connect for Claude Code, Cursor, Windsurf, Cline, Codex CLI or any JSON MCP client. Row-level security, hashed credentials and an audit trail keep the store team-safe whether you self-host on PostgreSQL 16 or let us host it.

What changes the first week

In the first week with MCP Memory Server in Berlin, sessions stop re-proposing settled decisions because pinned invariants outrank noise during ranked retrieval. According to Authoritas, AI Overviews cut traditional clicks by 58%, so being the cited, extractable source inside the briefing matters more than dumping more tokens.

Standups shrink to real blockers, reviews surface the original rationale in one query, and agents respect hard constraints automatically. Because briefings are deltas, the archive stays a query away rather than a stowaway in every prompt.

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

MCP Memory Server: core benefits and capabilities

01

Prove who did what

Actor, action, and target on every admin change — ready for security review and audits.

02

No pasted secrets

mh login via browser with scoped, revocable credentials — a lost laptop loses access instantly.

03

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.

04

Run on PostgreSQL you trust

pgvector-ready schema, versioned migrations, Docker/Easypanel. Backups with pg_dump — no exotic stack.

05

One proxy, every client

memhub serve bridges any MCP client over stdio. Zero daemons on the laptop, zero workflow change.

06

Queue when offline

Local SQLite outbox keeps memory writable during outages — syncs automatically when you’re back.

The honest comparison.

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

FeatureMemHubMem0SupermemoryIdeal For
ScopeOrganization → Project → Member, shared across every agentPer-user graph, not team-scopedPer-user vault with sharing on requestTeams that need one truth across tools
StoragePostgreSQL 16 + pgvector, versioned & queryableVector graph on managed infraHosted cloud store, limited exportTeams that need SQL, backups and audit
Tenancy & RLSRow-level security inside the DB, enforced per projectApplication-level isolationWorkspace isolation, no RLSGDPR / SOC-2 reviews
Self-hostDocker/Easypanel recipe included, same MCP + RESTOpen-source self-host possible, different opsCloud-onlyData-residency and on-prem requirements
Offline & syncLocal SQLite outbox, incremental deltas by sequenceOnline-first syncOnline-first, no local outboxFlaky networks, planes and VPN gaps
Pricing modelCommunity free (1 project) · Team $29 · self-host unlimitedFree tier + usage billingFree tier + pay-per-seatTrying 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
Simulate 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.

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. Because writes land locally first and sync as incremental deltas, teams stay productive offline and distributed squads remain aligned without re-explaining decisions every session.

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. Because writes land locally first and sync as incremental deltas, teams stay productive offline and distributed squads remain aligned without re-explaining decisions every session.

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. Because writes land locally first and sync as incremental deltas, teams stay productive offline and distributed squads remain aligned without re-explaining decisions every session.

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. Because writes land locally first and sync as incremental deltas, teams stay productive offline and distributed squads remain aligned without re-explaining decisions every session.

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. Because writes land locally first and sync as incremental deltas, teams stay productive offline and distributed squads remain aligned without re-explaining decisions every session.

MORE LOCATIONS

EXPLORE OTHER USE CASES

THE NEXT SESSION STARTS HERE — 2 MIN SETUP

Stop rebuilding context.
Start shipping faster.

Create workspace — free