mindwtr-mcp 1.0.5 → 1.1.1
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 +6 -6
- package/dist/index.js +5410 -2611
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# Mindwtr MCP Server
|
|
2
2
|
|
|
3
|
-
MCP server for Mindwtr. Connect MCP clients (Claude Desktop, etc.) to either your local Mindwtr SQLite database or a self-hosted Mindwtr Cloud endpoint
|
|
3
|
+
MCP server for Mindwtr. Connect MCP clients (Claude Desktop, etc.) to either your local Mindwtr SQLite database or a self-hosted Mindwtr Cloud endpoint.
|
|
4
4
|
|
|
5
5
|
This is a **stdio** server (no hosted HTTP endpoint). MCP clients launch it as a subprocess and talk over JSON-RPC on stdin/stdout.
|
|
6
6
|
|
|
@@ -21,7 +21,7 @@ On desktop, the app shows the exact local data path in **Settings -> Sync -> Loc
|
|
|
21
21
|
- Node.js 18+ (for the MCP client that spawns the server)
|
|
22
22
|
- npm package installs use better-sqlite3, a native SQLite addon. If no prebuilt binary is available for your platform, npm needs a working C/C++ build toolchain and Python for node-gyp.
|
|
23
23
|
- Bun (recommended for development in this repo)
|
|
24
|
-
- A local Mindwtr database (`mindwtr.db`) for local mode, or a self-hosted Mindwtr Cloud URL and bearer token for
|
|
24
|
+
- A local Mindwtr database (`mindwtr.db`) for local mode, or a self-hosted Mindwtr Cloud URL and bearer token for Cloud mode
|
|
25
25
|
|
|
26
26
|
Default database locations:
|
|
27
27
|
- Linux: `~/.local/share/mindwtr/mindwtr.db`
|
|
@@ -74,11 +74,11 @@ Or let an MCP client launch it through npx:
|
|
|
74
74
|
}
|
|
75
75
|
```
|
|
76
76
|
|
|
77
|
-
The npm package is read-only by default. Add `--write` only when you explicitly want add/update/complete/delete tools enabled
|
|
77
|
+
The npm package is read-only by default. Add `--write` only when you explicitly want add/update/complete/delete tools enabled.
|
|
78
78
|
|
|
79
|
-
###
|
|
79
|
+
### Self-hosted Cloud mode
|
|
80
80
|
|
|
81
|
-
Use Cloud mode when you run your own Mindwtr Cloud server and want MCP
|
|
81
|
+
Use Cloud mode when you run your own Mindwtr Cloud server and want MCP tools without pointing the helper at a local SQLite database:
|
|
82
82
|
|
|
83
83
|
```bash
|
|
84
84
|
npx -y mindwtr-mcp \
|
|
@@ -94,7 +94,7 @@ MINDWTR_MCP_CLOUD_TOKEN="$MINDWTR_TOKEN" \
|
|
|
94
94
|
npx -y mindwtr-mcp
|
|
95
95
|
```
|
|
96
96
|
|
|
97
|
-
Cloud mode uses the self-hosted Cloud API
|
|
97
|
+
Cloud mode uses the self-hosted Cloud API. Reads come from the current `/v1/data` snapshot; with `--write`, task/project/section/area writes go through the Cloud server's per-resource REST endpoints (`POST /v1/tasks`, `PATCH /v1/tasks/:id`, and so on), so they get the same validation and revision stamping as any other client. Without `--write`, write tools return `read_only`. Person edits and restoring deleted tasks are not available in Cloud mode yet.
|
|
98
98
|
|
|
99
99
|
This does not make Mindwtr Cloud itself a hosted MCP server. It is still the same stdio helper, backed by a Cloud URL that you operate.
|
|
100
100
|
|