Synaptic Core 1.0 — MCP Native

AI with a
perfect memory.

Memobase is the persistent synaptic layer for your AI agents. Claude and ChatGPT remember every detail across every session.

The Challenge

Break the Amnesia Loop.

Context windows are expanding, but they remain ephemeral. Every new session is a reset—your agent forgets your architecture, your style, and your progress.

Context Erosion

As conversations grow, older facts are silently evicted from the context window to make room for new ones.

Session Isolation

Great ideas from yesterday's chat are inaccessible today. You're stuck in a loop of re-explaining your setup.

Fragmented Identity

Claude knows one thing, ChatGPT knows another. There is no shared "source of truth" for your AI toolchain.

Static Intelligence

Without long-term memory, agents can't evolve with you. They remain generic assistants rather than specialized partners.

Core Architecture

Built for production

🔍

Semantic vector search

Memories are stored as 1536-dimension embeddings. Retrieval is by meaning, not keyword.

🔐

Per-user isolation

PostgreSQL Row-Level Security enforces strict data isolation at the database level.

Sub-second retrieval

IVFFlat cosine index delivers results in milliseconds, even across millions of memories.

🔌

MCP-native protocol

Built on the Model Context Protocol. Works natively with Claude and ChatGPT.

📋

Audit-ready

Every memory is timestamped with structured metadata for full traceability.

📊

Usage transparency

Real-time usage tracking through standard MCP tools and dashboard.

Implementation

Up and running in minutes

⚙️
01

Initialize Core

Add the Memobase MCP server to your AI configuration with a single JSON entry.

🔒
02

Neural Handshake

Authenticate once via secure OAuth. Your memories are isolated using Postgres RLS.

🧠
03

Active Recurrence

Your agent automatically retrieves context and stores new insights in real-time.

Neural Allocation

Simple, transparent pricing

Start free and upgrade when you need more. Monthly limits reset on the first of each month.

Free

$0 /forever

500 credits / month

Perfect for trying Memobase out.

  • store_memory = 10 credits, search = 1 credit
  • forget_memory (always free)
  • Semantic vector search
  • Per-user memory isolation
  • Community support
Start for free
Recommended

Pro

$9 /per month

5,000 credits / month

For power users and small teams who rely on memory daily.

  • Everything in Free
  • 5,000 credits per month
  • Monthly usage dashboard
  • Email support
  • Priority response
Upgrade to Pro

Unlimited

$29 /per month

Unlimited credits

No limits. For teams and high-volume agent workflows.

  • Everything in Pro
  • Unlimited credits
  • Dedicated support
  • SLA available
  • Custom onboarding
Go Unlimited

Quick Setup

Connect in minutes

Add Memobase to your favorite AI assistant — no code required.

Claude

  1. 1

    Open Integrations

    In Claude.ai, click your name → Settings → Connectors → Add custom connector.

  2. 2

    Paste the server URL

    https://mcp.memobase.ai
  3. 3

    Sign in & start chatting

    Click Connect and authorize Memobase.

Pro Tip: Enable automatic memory

Once connected, follow the Recommended System Prompt instructions on the right to make Claude use its new memory automatically.

Recommended System Prompt

Paste this into Settings → Personalization → Instructions (or Project Instructions) to enable automatic recall.

Memobase MCP = persistent shared memory.

Start chat: search_memory(mode="hybrid", query=user+task keywords). Before answering anything that depends on past chats/decisions, search_memory first; use knowledge_graph_query/explore_relationships for entity links.

Store only durable, reusable info (short + data-minimised): prefs, stable facts, goals, reusable procedures/solutions, decisions+rationale. type=semantic|episodic(dated)|procedural|decision. Skip routine/ephemeral.

Keep it clean: update_memory when superseded; merge_memories when duplicate/overlapping; namespace per project/topic. If user says "continue"/"pick up", reconstruct_context first. Keep memory ops invisible unless asked. Never store secrets/sensitive personal data unless user explicitly requests.