MCP MEMORY SERVER · AVAILABLE NOW

MCP Memory Server across Switzerland

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.

Connect Claude Code, Cursor, Codex, Windsurf, Cline or any JSON MCP client to one memory. Writes hit the local outbox first, then sync — flaky VPN never costs context. Try free, self-host anytime.

Nelson · Founder, MemHub at Simplex.lat

Simplex.lat · Quito, Ecuador · Last updated: September 4, 2026

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

decision2m

Usar bloqueos consultivos en PostgreSQL

Fuente: Nelson · architecture.md

pattern18m

Los errores de API siguen RFC 9457

Fuente: Maya · PR #184

bugfix1h

Los refresh tokens rotan atómicamente

Fuente: Codex CLI · auth/session.ts

Claude Code

Cursor

Codex CLI

Definition

What is MCP Memory Server across Switzerland?

MCP Memory Server is a persistent, versioned memory layer that captures team decisions, constraints, bug fixes and preferences so AI coding agents start each session informed instead of re-learning them. In Switzerland, engineering teams use MemHub to keep that memory shared across Claude Code, Cursor, Windsurf and Codex CLI with local-first sync and full provenance.

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 →

Seats included in Team

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

According to MemHub pricing →

Projects included in Team

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

According to MemHub pricing →

Why Switzerland teams need MCP Memory Server

MCP Memory Server in Switzerland helps engineering teams ship faster because every AI coding session opens pre-briefed with only what changed since the last pull, not a full dump. According to Search Engine Journal, 45% of searches now show an AI Overview, so concise, cited memory answers also travel beyond the IDE into generative results.

Distributed squads stay aligned across time zones, new hires ramp in days from searchable precedent, and mixed toolchains stop fragmenting knowledge. MemHub keeps that context project-scoped with provenance and local-first sync, so the revised FADP requirements requirements are met without re-explaining.

How MemHub delivers MCP Memory Server without trade-offs

MemHub delivers MCP Memory Server in Switzerland 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.

THE MECHANISM

Write once. Every session remembers.

Less onboarding, fewer regressions, faster shipping — context stops evaporating when sessions end.

You keep coding

Decisions auto-captured where you work — terminal, PR, editor. No extra docs, no context-switching.

MemHub does the plumbing

Local SQLite outbox first, then project-scoped sync with provenance (who, when, why). Works offline.

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

Queue when offline

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

Prove who did what

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

No pasted secrets

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

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.

Run on PostgreSQL you trust

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

One proxy, every client

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

The honest comparison.

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

Start free — 2 min Talk to the team

Feature	MemHub	Mem0	Supermemory	Ideal For
Scope	Organization → Project → Member, shared across every agent	Per-user graph, not team-scoped	Per-user vault with sharing on request	Teams that need one truth across tools
Storage	PostgreSQL 16 + pgvector, versioned & queryable	Vector graph on managed infra	Hosted cloud store, limited export	Teams that need SQL, backups and audit
Tenancy & RLS	Row-level security inside the DB, enforced per project	Application-level isolation	Workspace isolation, no RLS	GDPR / SOC-2 reviews
Self-host	Docker/Easypanel recipe included, same MCP + REST	Open-source self-host possible, different ops	Cloud-only	Data-residency and on-prem requirements
Offline & sync	Local SQLite outbox, incremental deltas by sequence	Online-first sync	Online-first, no local outbox	Flaky networks, planes and VPN gaps
Pricing model	Community free (1 project) · Team $29 · self-host unlimited	Free tier + usage billing	Free tier + pay-per-seat	Trying 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.

Start free — 2 min Talk to the team

memhub-cli · preview

Click tabs to simulateSimulate 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.

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. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.

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. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.

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. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.

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. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.

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. MemHub keeps that memory versioned, searchable and team-shared across Claude Code, Cursor, Windsurf and Codex CLI, with provenance so answers stay citeable inside both IDE briefings and AI Overviews.

MORE LOCATIONS

MCP Memory Server across the United States MCP Memory Server across Canada MCP Memory Server across the United Kingdom MCP Memory Server across Ireland MCP Memory Server across Germany MCP Memory Server across France MCP Memory Server across Spain MCP Memory Server across Portugal MCP Memory Server across Italy MCP Memory Server across the Netherlands MCP Memory Server across Belgium MCP 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 — 2 MIN SETUP

Stop rebuilding context.
Start shipping faster.

Create workspace — free

MCP Memory Server across Switzerland

What changed since your last pull

Usar bloqueos consultivos en PostgreSQL

Los errores de API siguen RFC 9457

Los refresh tokens rotan atómicamente

What is MCP Memory Server across Switzerland?

Team plan at a glance

Why Switzerland teams need MCP Memory Server

How MemHub delivers MCP Memory Server without trade-offs

Write once. Every session remembers.

You keep coding

MemHub does the plumbing

Next session starts ahead

Plugs into any CLI, IDE, or AI coding agent.

MCP Memory Server: core benefits and capabilities

Queue when offline

Prove who did what

No pasted secrets

Isolated by default

Run on PostgreSQL you trust

One proxy, every client

The honest comparison.

Keep your stack. Add shared memory.

Questions, answered straight.

Stop rebuilding context.Start shipping faster.

Stop rebuilding context.
Start shipping faster.