Membase

ai.membasePublished by membase.aiv1.0.1Updated Oct 24, 2026

Long-term memory for you and your AIs: search memories, read the profile, add facts and documents.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Membase is a hosted long-term memory layer that lets an assistant search, read, add and manage shared memories, documents and a profile across AI tools.

What you can do
  • Search and ask questions over stored memories
  • Read the user profile and memory containers
  • Add facts, documents, web pages and imported chat exports
  • Organize memories into containers and forget entries that should go
  • Share one memory across Claude Code, Cursor, Codex, ChatGPT and SDK clients
When to use it
Use it when you want an assistant to remember facts, decisions and documents across sessions and across different AI tools, instead of re-explaining context each time you switch models or clients.
Requirements
Remote endpoint at api.app.membase.com over streamable HTTP with OAuth sign-in. A Membase account is needed; a MEMBASE_API_KEY bearer header is used for full access. No environment variables or headers are declared in the manifest.
Before you install
Memories are stored in a Membase account and shared with every connected AI, so anything added may be readable by other clients. Hosted connections without the bearer header are read-only. Adding, importing and forgetting change stored data. Chat exports from Claude or ChatGPT may contain sensitive content.

Installation

In SourceWeft

  1. Open Membase in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.membase%2Fmembase/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "membase": {
      "type": "http",
      "url": "https://api.app.membase.com/mcp-http"
    }
  }
}

README

[Membase]

Membase

One memory. Every AI. Only yours.
Teach it once. Every AI remembers.

[PyPI] [npm] [MIT]

Website · Docs · Web app · Discord · X

[Add sources, manage one memory, use it from every AI and app]

Membase is the memory layer for AI agents. It keeps one memory for everything you and your agents know, and every AI you use reads it. You stop re-explaining yourself each time you switch models or tools.

  • Add. Facts, documents, web pages and chat exports from Claude or ChatGPT go into one memory.
  • Manage. Containers keep projects apart; search it, ask it questions, forget what should go.
  • Use. Your code, Claude Code, Cursor, Codex and ChatGPT read the same memory through the SDK or MCP.

This repository is the developer side: Python and TypeScript clients, the membase command line and an MCP server. The memory lives in your Membase account, which the web app and browser extension also fill, or on your machine with unibaseio-membase[local].

Write once, read from any AI

[Your app writes a memory; any AI reads it, here Claude Code]

Recordings: Python SDK (57 s) · Claude Code (1 min 33 s). The answer above is illustrative.

Accuracy

[LoCoMo 93.1%, LongMemEval_S 92.6%, DMR 92.2%]

93.1% on LoCoMo, 92.6% on LongMemEval_S and 92.2% on DMR, using about 3× fewer tokens than the full history on LoCoMo and 11× fewer on LongMemEval_S. Method and results: membase.com/research

Quickstart

[Hosted, local in process, or local over HTTP]

bash
pip install unibaseio-membase              # hosted · Python 3.10+ · needs MEMBASE_API_KEYpip install 'unibaseio-membase[local]'     # local  · Python 3.12 or 3.13 · needs OPENAI_API_KEYpip install 'unibaseio-membase[media]'     # local + photos, videos and audionpm install @unibaseio/membase              # TypeScript · Node 18+npm install -g @unibaseio/membase-cli       # the `membase` command (hosted) without Python
python
from membase import Membase
m = Membase()                    # hosted# m = Membase(local=True)        # local, in ~/.membase
m.memories.add("We picked Postgres for the ledger service.", container="Engineering")m.search("what database is the ledger on?")m.add("Design notes …", container="Engineering", custom_id="design-1")   # a documentm.ask("Which database did we choose for the ledger?")

Every method, its REST route and MCP tool, and the access it needs: SDK reference. The Python package is unibaseio-membase (import membase); membase on PyPI is unrelated.

Command line

bash
membase --local add "We picked Postgres for the ledger" --container Engineeringmembase --local search "what did we pick for the ledger?"membase --local ask "Which database is the ledger on?"membase --local import ~/Downloads/claude-export.json     # Claude, ChatGPT, markdown or JSON chatsmembase --local agent ingest trace.json --agent codermembase --local agent search "fix flaky deploy" --agent codermembase --local media add ~/Movies/trip.mp4                # shots, speech and speakersmembase --local media search "someone skiing"   # any language

Without --local (or --store DIR, both before the command) commands use the hosted API; agent, import and serve need unibaseio-membase[local], and media (local only, with its own search and ask) needs unibaseio-membase[media]: see Media memory.

MCP

[MCP clients, hosted or local server, same tools]

bash
claude mcp add membase -- membase --local mcp                                   # localclaude mcp add --transport http membase https://api.app.membase.com/mcp-http \  --header "Authorization: Bearer $MEMBASE_API_KEY"                             # hosted

Hosted without the header, the connection signs you in and is read-only. Setup for Claude, ChatGPT, Cursor, Codex and other clients: Connect your AI.

Docs

License

MIT; see LICENSE. unibaseio-membase[local] also installs unibaseio-membase-core, the compiled engine, under its own Unibase license.

Source: README.md at commit 94b2d3e

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestOct 20, 2026
  2. v1.0.0Oct 14, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts