get_conversation_idLABSCO SUMMARY
Four tools, one job: conversation history that survives a restart.
It is deliberately small — write a message, read the recent ones back, and move between threads. What separates it from a local memory file is where the data goes: onto shared storage with a browsable hub, so the same history can follow an agent across machines.
What it is
A small server over the Membase memory layer. Messages you save go to the Unibase network, and the conversation they belong to preloads its history when the server starts.
What you get
- The current conversation identifier, so the agent knows which thread it is writing to (get_conversation_id)
- A switch to a different conversation without restarting (switch_conversation)
- A message or memory written into the current conversation (save_message)
- The last few messages read back out (get_messages)
- Stored messages viewable on the Membase hub in a browser
Requirements
An account on the network to upload under, an instance identifier, and a conversation identifier unique to you — that last one decides which history preloads. All three are supplied as environment settings when the client launches the server. Python with uv.
Setup effort
Build from source — git clone https://github.com/unibaseio/membase-mcp.git
USE CASES
01
Carrying context between sessions
Save the messages that matter as they happen; the history preloads next time the server starts.
02
Keeping separate threads separate
Switch to another conversation identifier so a new project does not inherit the old one's memory.
03
Checking what the agent actually remembers
Read the recent stored messages back before you rely on them.
4 tools
Listed in project docs. Your client may show a different list.
switch_conversationsave_messageget_messagesBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Requires
- uv on PATH
- MEMBASE_ACCOUNT in your environment
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
You clone this one yourself.
Server setup
TERMINAL
git clone https://github.com/unibaseio/membase-mcp.git
cd membase-mcp
uv run src/membase_mcp/server.pyMCP Clients
Claude Desktop, Windsurf, Other MCP clients
JSON
{
"mcpServers": {
"membase": {
"command": "uv",
"args": [
"--directory",
"<YOUR_PATH_TO_MEMBASE_MCP>",
"run",
"src/membase_mcp/server.py"
],
"env": {
"MEMBASE_ACCOUNT": "<YOUR_MEMBASE_ACCOUNT>",
"MEMBASE_CONVERSATION_ID": "<YOUR_MEMBASE_CONVERSATION_ID>",
"MEMBASE_ID": "<YOUR_MEMBASE_ID>"
}
}
}
}
