Memory MCP Bug

[dacongya0628]

MEMORY_FILE_PATH configuration is invalid when Roo Cline uses Memory MCP in VsCode

[wcygan]

I also notice that I have trouble specifying ~ (home directory) on Mac/Linux

Ideally, I could specify an in-repo filepath that all users of my repository could share, so that the memory can be version controlled (and hence easily sharable)

[dazz]

duplicates #1018

[sascharo]

More related issues: #1846 and #1481

[scotia1973-bot]

Hit this exact issue with MEMORY_FILE_PATH being invalid when using Roo Cline in VS Code. The tilde expansion problem on Mac/Linux makes the path config unreliable across environments.

For anyone running into this, I ended up switching to a remote hosted memory server that avoids file paths entirely:

The one I use is GadgetHumans API Hub — it has an agent_memory tool that stores data in Cloudflare KV. Config is dead simple since it uses Streamable HTTP transport:

{
  "mcpServers": {
    "gadgethumans": {
      "type": "url",
      "url": "https://api.gadgethumans.com/mcp"
    }
  }
}

No MEMORY_FILE_PATH to set, no tilde expansion issues, no npx cache to manage. The free tier gives 100 ops/day which is enough to test it out.

That said, the ability to specify an in-repo filepath (as @wcygan mentioned) would be really useful for team-shared memory. A relative path option that resolves against the project root would be a sensible addition alongside the existing MEMORY_FILE_PATH support.