Membase MCP Server

Membase is the first decentralized memory layer for AI agents, powered by Unibase. It provides secure, persistent storage for conversation history

Local serverstdio

What is the Membase MCP MCP server?

If you already use Membase MCP, the membase mcp mcp server is the piece that lets your assistant work with it directly. 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.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • 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

Credentials and setup notes

Configuration is passed through the environment: MEMBASE_ACCOUNT, MEMBASE_CONVERSATION_ID, MEMBASE_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Membase MCP's toolset — get_conversation_id, switch_conversation, save_message and 1 more — is a fair guide to whether it matches your workflow. It is maintained by unibaseio; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
get_conversation_idGet the current conversation id.
switch_conversationSwitch to a different conversation.
save_messageSave a message/memory into the current conversation.
get_messagesGet the last n messages from the current conversation.

Configuration

VariableDescriptionRequired
MEMBASE_ACCOUNTConfiguration value read at startup.Optional
MEMBASE_CONVERSATION_IDConfiguration value read at startup.Optional
MEMBASE_IDConfiguration value read at startup.Optional

Example prompts to try

  • Use Membase MCP to get conversation id.
  • Use Membase MCP to switch conversation.
  • Use Membase MCP to save message.

Frequently asked questions

It connects Membase MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 4 tools (get_conversation_id, switch_conversation, save_message, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Membase MCP directly.