You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to configure the MCP memory server to store data in a custom location, but it continues to store the memory.json file in the NPX temporary directory instead.
Configuration
In my Claude desktop config file, I've specified a custom path:
I've created the target directory and ensured it has appropriate permissions
The memory functionality works correctly, but uses the wrong file location
Claude can read/write to the temporary file location, but this isn't persistent
Can someone help explain why the environment variable isn't being recognized, or if there's a different way to specify a custom storage location? This is concerning because NPX temporary directories may be cleaned up, potentially losing all memory data.
The text was updated successfully, but these errors were encountered:
I've been trying to configure the MCP memory server to store data in a custom location, but it continues to store the memory.json file in the NPX temporary directory instead.
Configuration
In my Claude desktop config file, I've specified a custom path:
Actual Behavior
Despite setting the
MEMORY_FILE_PATH
environment variable, the memory.json file is still being created in the NPX temporary directory:Additional Information
Can someone help explain why the environment variable isn't being recognized, or if there's a different way to specify a custom storage location? This is concerning because NPX temporary directories may be cleaned up, potentially losing all memory data.
The text was updated successfully, but these errors were encountered: