@memoraone/mcp 0.1.16 → 0.1.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +18 -0
- package/dist/cli.cjs +254 -1196
- package/dist/daemon.cjs +1923 -0
- package/dist/index.cjs +939 -491
- package/package.json +11 -7
package/README.md
ADDED
|
@@ -0,0 +1,18 @@
|
|
|
1
|
+
# @memoraone/mcp
|
|
2
|
+
|
|
3
|
+
MCP server for MemoraOne: timeline events, ask-with-memory, project binding.
|
|
4
|
+
|
|
5
|
+
## Option A: single-project binding
|
|
6
|
+
|
|
7
|
+
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.
|
|
8
|
+
|
|
9
|
+
### Manual reproduction: “already bound” error
|
|
10
|
+
|
|
11
|
+
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)`.
|
|
12
|
+
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).
|
|
13
|
+
3. **Expected:**
|
|
14
|
+
- 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."*
|
|
15
|
+
- The IDE receives an MCP Initialize error response (the request fails).
|
|
16
|
+
- The process exits with non-zero (e.g. `process.exit(1)` after the error is sent).
|
|
17
|
+
|
|
18
|
+
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.
|