MCP Connector

Integrate Decentralized Memory for AI Agents

Save and retrieve AI agent conversation memory on Membase, a decentralized, verifiable storage layer built on Unibase.

Works with github

Maintainer of this project? Claim this page to edit the listing.


77
Spark score
out of 100
Updated May 2025
Version 1.0.0
Models
universal

Add to Favorites

Why it matters

Connect your AI agents to a decentralized memory layer for secure, persistent storage of conversation history and knowledge. Enable agent continuity, personalization, and auditability.

Outcomes

What it gets done

01

Store and retrieve AI agent conversation history.

02

Manage and switch between different conversation contexts.

03

Securely persist agent knowledge and interaction records.

04

Integrate with the Unibase DA network for verifiable storage.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-membase | bash

Capabilities

Tools your agent gets

get_conversation_id

Get the current conversation ID

switch_conversation

Switch to a different conversation

save_message

Save a message/memory to the current conversation

get_messages

Get the last n messages from the current conversation

Overview

Membase MCP Server

Membase MCP Server gives AI agents persistent, decentralized conversation memory by uploading and retrieving messages from the Unibase DA network via Membase. It supports switching between multiple tracked conversations. Use it when an agent's memory needs to persist on a decentralized, verifiable storage layer across sessions. Not applicable if purely local, network-independent memory is required.

What it does

Membase MCP Server connects an AI agent to Membase, described as the first decentralized memory layer for AI agents, powered by Unibase. It uploads and retrieves conversation history, interaction records, and knowledge to the Unibase DA network, giving agents persistent, verifiable, and traceable memory across sessions instead of storage that disappears when a session ends.

When to use - and when NOT to

Use it when you want an agent's conversation memory to persist on a decentralized, verifiable storage layer - useful for continuity across sessions, personalization, or auditability of what an agent said and stored. Each conversation is tracked by a unique MEMBASE_CONVERSATION_ID, and stored messages/memories can be inspected directly at testnet.hub.membase.io. Do not use it if you need purely local, private memory with no external network dependency - Membase stores data on the Unibase DA network rather than locally.

Capabilities

  • get_conversation_id: get the ID of the current conversation.
  • switch_conversation: switch to a different conversation, preloading its history.
  • save_message: save a message or memory into the current conversation.
  • get_messages: retrieve the last n messages from the current conversation.

How to install

git clone https://github.com/unibaseio/membase-mcp.git
cd membase-mcp
uv run src/membase_mcp/server.py

Configure required environment variables: MEMBASE_ACCOUNT (your account to upload as, e.g. 0x...), MEMBASE_CONVERSATION_ID (a unique conversation identifier whose history will preload), and MEMBASE_ID (your instance/sub-account identifier).

Register with Claude, Windsurf, Cursor, or Cline:

{
  "mcpServers": {
    "membase": {
      "command": "uv",
      "args": ["--directory", "path/to/membase-mcp", "run", "src/membase_mcp/server.py"],
      "env": {
        "MEMBASE_ACCOUNT": "your account, 0x...",
        "MEMBASE_CONVERSATION_ID": "your conversation id, should be unique",
        "MEMBASE_ID": "your sub account, any string"
      }
    }
  }
}

Who it's for

Agent developers who want persistent, decentralized, and independently verifiable conversation memory for their AI agents rather than storage tied to a single centralized provider.

Source README

membase mcp server

Description

Membase is the first decentralized memory layer for AI agents, powered by Unibase. It provides secure, persistent storage for conversation history, interaction records, and knowledge - ensuring agent continuity, personalization, and traceability.

The Membase-MCP Server enables seamless integration with the Membase protocol, allowing agents to upload and retrieve memory from the Unibase DA network for decentralized, verifiable storage.

Functions

Messages or memoiries can be visit at: https://testnet.hub.membase.io/

  • get_conversation_id: Get the current conversation id.
  • switch_conversation: Switch to a different conversation.
  • save_message: Save a message/memory into the current conversation.
  • get_messages: Get the last n messages from the current conversation.

Installation

git clone https://github.com/unibaseio/membase-mcp.git
cd membase-mcp
uv run src/membase_mcp/server.py

Environment variables

  • MEMBASE_ACCOUNT: your account to upload
  • MEMBASE_CONVERSATION_ID: your conversation id, should be unique, will preload its history
  • MEMBASE_ID: your instance id

Configuration on Claude/Windsurf/Cursor/Cline

{
  "mcpServers": {
    "membase": {
      "command": "uv",
      "args": [
        "--directory",
        "path/to/membase-mcp",
        "run", 
        "src/membase_mcp/server.py"
      ],
      "env": {
        "MEMBASE_ACCOUNT": "your account, 0x...",
        "MEMBASE_CONVERSATION_ID": "your conversation id, should be unique",
        "MEMBASE_ID": "your sub account, any string"
      }
    }
  }
}

Usage

call functions in llm chat

  • get conversation id and switch conversation

  • save message and get messages

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.