Best for
- Existing Mindwtr users who want AI assistance with task capture and processing
- Developers or power users comfortable configuring a local stdio MCP server
- Self-hosters running a Mindwtr Cloud instance who need read-only querying
M
Mindwtr MCP Server
Official
Let AI assistants read and manage your local Mindwtr GTD tasks.
GitHub source repository ↗
57FMRS · C
This is the official MCP server bundled with the Mindwtr open-source GTD app (version 1.1.4, AGPL-3.0 license), distributed as the npm package mindwtr-mcp over stdio, enabling local task automation with optional read-only self-hosted Cloud access.
Mindwtr MCP Server is the official first-party component bundled with the Mindwtr open-source GTD app, distributed as the npm package mindwtr-mcp running over stdio. It lets AI assistants read and manage tasks and projects in a local Mindwtr SQLite database, with optional read-only access to a self-hosted Mindwtr Cloud instance.
Tools
The tool list has not been reviewed yet.
Setup
- Make sure Node.js and npm are installed. 2. In your MCP client's stdio server configuration, add the command
npx -y mindwtr-mcp(or runnpm install -g mindwtr-mcpfirst and reference themindwtr-mcpcommand directly). 3. Optionally set MINDWTR_DB_PATH to point to your local Mindwtr SQLite database file if it isn't in the default location. 4. For self-hosted Cloud read-only mode, optionally set MINDWTR_MCP_CLOUD_URL (your self-hosted Cloud base URL) and MINDWTR_MCP_CLOUD_TOKEN (bearer token). 5. Save the config and restart the client to confirm the connection.
claude_desktop_config.json
{"mcpServers": {"mindwtr": {"command": "npx", "args": ["-y", "mindwtr-mcp"]}}}
Fit and risk
Not for
- Users without Mindwtr installed or without a local SQLite database
- Teams needing multi-user collaborative writes via Cloud (Cloud mode is read-only)
- Non-technical users unfamiliar with npm package installs and environment variables
Required permissions
- Read/write access to the local Mindwtr SQLite database file (path set via MINDWTR_DB_PATH)
- Network access to a self-hosted Mindwtr Cloud URL when Cloud mode is configured (read-only)
- A bearer token credential for Cloud API access
Risks and side effects
- The server has write access to the local database, so erroneous AI-issued changes could corrupt or pollute local task data
- Storing the Cloud bearer token insecurely in environment variables risks credential exposure
- Task and project data is exposed to whichever AI model is connected, with no additional sandboxing on scope
Troubleshooting
- If tasks don't appear, verify MINDWTR_DB_PATH points to the correct local Mindwtr SQLite file
- Confirm npm/npx can reach the registry to install mindwtr-mcp
- For Cloud mode, check that MINDWTR_MCP_CLOUD_URL and MINDWTR_MCP_CLOUD_TOKEN are set correctly and the self-hosted Cloud instance is reachable
- Check the MCP client's stdio connection logs for startup or handshake errors
Use cases
Have an AI assistant help clarify the Inbox, add, or process GTD tasks during a chat
Ask the AI to surface overdue or waiting-for items to support a weekly review
Get a read-only task overview from a self-hosted Mindwtr Cloud instance
Supported clients
Claude DesktopFull support