Mindwtr runs on your own machine — the client starts it, so there is no endpoint to ping. 449 installs a week from npm. Last commit 2 Nov 2026.
Task automation via SQLite, desktop Local API, or Mindwtr Cloud; read-only by default.
We read the source, 2 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const serviceDir = path.join(mainRoot, 'java', packageDir, 'quicksettings');
val drop = {
val center = startTop + height / 2 + (finger - grab)
"plaintextB64": "VGhlIHF1aWNrIGJyb3duIGZveCBqdW1wcyBvdmVyIHRoZSBsYXp5IGRvZy4gVGhlIHF1aWNrIGJyb3duIGZveCBqdW1wcyBvdmVyIHRoZSBsYXp5IGRvZy4gVGhlIHF1aWNrIGJyb3duIGZveCBqdW1wcyBvdmVyIHRoZSBsYXp5IGRvZy4gVGhlIHF1aWNrIGJyb3duIGZveCBqdW1wcyBvdmVyIHRoZSBsYXp5IGRvZy4gVGhlIHF1aWNrIGJyb3d…
USER root
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mindwtr -- npx -y mindwtr-mcp
{
"mcpServers": {
"mindwtr": {
"command": "npx",
"args": [
"-y",
"mindwtr-mcp"
]
}
}
}
[mcp_servers.mindwtr]
command = "npx"
args = ["-y", "mindwtr-mcp"]
{
"mcpServers": {
"mindwtr": {
"command": "npx",
"args": [
"-y",
"mindwtr-mcp"
]
}
}
}
{
"servers": {
"mindwtr": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mindwtr-mcp"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
MINDWTR_DB_PATH (Optional path to the local Mindwtr SQLite database), MINDWTR_MCP_CLOUD_URL (Optional self-hosted Mindwtr Cloud base URL for Cloud mode), MINDWTR_MCP_CLOUD_TOKEN (Bearer token for self-hosted Mindwtr Cloud mode), MINDWTR_MCP_API_URL (Desktop Local API origin, e.g. http://127.0.0.1:3456. Selects API mode), MINDWTR_MCP_API_TOKEN (Bearer token from the desktop Local API settings; required in API mode).
MCP server for libSQL/Turso, local or remote. Read-only by default, row caps, timeouts.
MCP server for SQLite databases. Read-only by default, row caps, statement timeouts.
Safe, read-only-by-default MySQL, PostgreSQL & SQLite access for AI agents. TOON output.
Safety-railed database access: Postgres, MySQL, SQLite, Redis. Read-only by default.
Agent-safe MCP sidecar for one live SQLite database: read-only default, bounded writes.
Read-only WHOOP v2 data for MCP clients, with local SQLite cache and CSV/JSONL/Parquet exports.
MCP server for PostgreSQL. Read-only by default, row caps, timeouts, secrets never logged.
MCP server for MariaDB. Read-only by default, row caps, timeouts, secrets never logged.
Answers built from our own checks of this server.