Loading...
{
"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"
}
}
}
}get_conversation_idRetrieves the current conversation ID.
Read-only operation, no side effects.
switch_conversationSwitches to a different conversation using its ID.
Changes the current conversation context, potentially affecting subsequent operations.
save_messageSaves a message/memory into the current conversation.
Writes data to the decentralized storage, but is limited to message content.
get_messagesRetrieves the last n messages from the current conversation.
Read-only operation, retrieves existing messages.
The Membase-MCP server offers a moderate level of safety. While it provides a limited set of functions and stores data on a decentralized network, the reliance on environment variables for authentication and potential lack of input sanitization pose risks. It's safer when used with strong environment variable management and input validation.