Feature Proposal: Role-Based Memory Isolation and API Permission Management in OpenMemory

[li1553770945]

🚀 The feature

Currently, I have different memory role requirements, such as my own personal information and memories shared with friends. I hope they can be isolated from each other so that my friends will not access my personal memories when they use them together. Currently, I implement this function by deploying multiple docker containers.

Propose to add the following core functions to OpenMemory MCP:

1. Role creation and allocation:

Allow roles to be created through configuration webui or APIs, and allocate independent memory storage space for each role. After the user/client is bound to a specific role, its memory read and write operations only apply to the scope of the role.

2. Permission hierarchical control:

Support role-level API permission configuration, each api key can only access the memory of a specific role, and add permission control, such as memory writing is limited to admin permission calls, and memory reading is allowed to be called by guest permission.

Motivation, pitch

1. Currently, OpenMemory's memory storage is globally shared, resulting in interference between memory data of different roles.

2. Lack of fine-grained control over API operations.