fix: Change memory server default filename from memory.json to memory.jsonl

[olaservo]

The Memory MCP server uses JSONL format (JSON Lines) where each line contains a separate JSON object, but was using a .json file extension. This caused IDE lint errors and confusion since the file is not valid JSON.

Changes:

• Update default filename in index.ts from memory.json to memory.jsonl
• Update documentation references in README.md
• Maintain backward compatibility for existing MEMORY_FILE_PATH configs

Fixes #2361

Generated with Claude Code

[domdomegg]

Might this cause some weird backwards compatibility problems, e.g. if people have npx -y @modelcontextprotocol/server-memory in config, suddenly it'll seem to them like all their memories have disappeared.

Maybe we could also check before this: if no custom path is set AND memory.json exists AND memory.jsonl does not exist, move memory.json to memory.jsonl.

[olaservo]

I made this change.

[domdomegg]

Good, although maybe want to address the backwards compatibility comment above

[olaservo]

@claude could you take a look at the latest comments and incorporate these suggestions?

[claude]

Claude finished @olaservo's task —— View job

---

Implementing backward compatibility suggestion ✅

I've successfully implemented the reviewer's suggestion to add backward compatibility for existing memory.json files.

Tasks:

• Read repository setup instructions (CLAUDE.md) - No repo-specific instructions found
• Examine current memory server implementation
• Implement file migration logic (memory.json → memory.jsonl)
• Test the implementation (builds successfully)
• Commit and push changes

Implementation Details

Added backward compatibility logic that:

1. When no custom MEMORY_FILE_PATH is set: Checks if memory.json exists and memory.jsonl doesn't exist
2. If migration is needed: Renames memory.json to memory.jsonl and logs the migration
3. Maintains existing behavior: Custom paths work exactly as before
4. Safe migration: Only migrates when new file doesn't exist to avoid data loss

The migration happens during server startup in the main() function, before any file operations occur.

Key changes to src/memory/index.ts:14-49:

• Added ensureMemoryFilePath() async function for migration logic
• Changed MEMORY_FILE_PATH to be initialized at runtime instead of module load
• Added migration logic that safely renames old file to new format

Commit: 53104a6 - Add backward compatibility for memory.json -> memory.jsonl migration

The backward compatibility feature is now implemented! Users with existing memory.json files will have them automatically migrated to memory.jsonl on their first run, ensuring no data loss while fixing the IDE linting issues.

---