@memoraone/mcp

MCP server for MemoraOne: timeline events, ask-with-memory, project binding.

Option A: single-project binding

This server enforces one MCP process = one MemoraOne project for the process lifetime. Re-initializing with a different project in the same process is rejected.

Manual reproduction: “already bound” error

1. Start the MCP server (e.g. from Cursor with one workspace root that has memoraone.m1 for project A). Wait until it logs bound to project <id> (Option A: single-project binding).
2. In the same process, trigger a second Initialize that would bind project B (e.g. open another folder that has memoraone.m1 for project B, in a setup where the IDE reuses the same MCP process).
3. Expected:
   • A single ERROR log line containing: boundProjectId, requestedProjectId, workspaceRoot, and the action: "Open this repo in a separate window or configure a separate MCP server instance per root."
   • The IDE receives an MCP Initialize error response (the request fails).
   • The process exits with non-zero (e.g. process.exit(1) after the error is sent).

To avoid the conflict: open each project in a separate window, or configure a separate MCP server instance per root, so each process binds only one project.