Zenitsu

com.xernaitechPublished by xernaitech.comv1.22.0Updated Oct 25, 2026

Your local Zenitsu tasks and notes for AI apps. Needs the Zenitsu app (Linux).

Overview

AI-generated overview

Zenitsu is a local MCP server that lets AI assistants read and update your Zenitsu tasks, notes and daily journal on a Linux desktop.

What you can do
Read your Zenitsu tasks, notes and daily journal from the local app database and bring them into an AI conversation, under rules you set in the app's AI settings. Update those tasks and notes on your behalf, with the app preventing the AI from erasing your data. Support daily journaling and review routines when used through the Claude Code plugin, which adds daily-line and sunday-review commands. Optionally enforce that every task an AI adds has a priority, a type and a due date.
When to use it
Use it if you already run the Zenitsu task manager and notebook on Linux and want an AI assistant such as Claude, Codex, VS Code Copilot or Cursor to work with your tasks, notes and journal without leaving your machine.
Requirements
The Zenitsu app must be installed and opened once on a Linux desktop; the server runs as a local stdio process (zenitsu-mcp) bundled with the app. The database is expected at ~/.local/share/com.xernai.zenitsu/ unless the ZENITSU_DB environment variable points to zenitsu.sqlite elsewhere. With the AppImage, the AppImage path is used as the command with mcp as the first argument, or ZENITSU_APPIMAGE is set for the plugin. No authentication is declared.
Before you install
The server can update your tasks and notes, so changes made by an assistant affect your real local data; the README states the AI can never erase your data. Access is governed by rules you configure in the app's AI apps settings, including whether AI-added tasks must have a priority, type and due date. The README says nothing is sent anywhere by Zenitsu, but review what your AI app itself transmits. Desktop Linux only.

Installation

In SourceWeft

  1. Open Zenitsu in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Zenitsu

Zenitsu is a fast, private task manager and notebook for Linux. Your tasks, notes and daily journal stay on your own computer, and AI apps such as Claude can read and update them for you, under rules you set.

Download (Linux, free)

Your systemDownload
Ubuntu, Debian, Mintzenitsu-latest-amd64.deb
Fedora, RHEL, openSUSEzenitsu-latest-x86_64.rpm
Any distributionZenitsu-latest-x86_64.AppImage or the tarball

Older versions are on the Releases page.

Use Zenitsu with AI apps

Install Zenitsu first and open it once. It includes zenitsu-mcp, a small program that lets AI apps work with your tasks and notes on this computer. Nothing is sent anywhere by Zenitsu, and the AI can never erase your data.

Claude Code — install the Zenitsu plugin. It connects Claude to Zenitsu and teaches it how to use it well, and adds /zenitsu:daily-line and /zenitsu:sunday-review:

text
/plugin marketplace add ANSHAY/zenitsu-releases/plugin install zenitsu@zenitsu

Other AI apps — point them at zenitsu-mcp:

AppHow
Codexcodex mcp add zenitsu -- zenitsu-mcp
VS Code (Copilot)code --add-mcp '{"name":"zenitsu","type":"stdio","command":"zenitsu-mcp"}'
Cursor, Claude Desktop, Gemini and othersadd {"mcpServers": {"zenitsu": {"command": "zenitsu-mcp", "args": []}}} to the app's MCP settings

With the AppImage, use the AppImage's path as the command and mcp as its first argument (for the Claude Code plugin, set ZENITSU_APPIMAGE to the AppImage's path instead). In Zenitsu, Settings → AI apps shows the exact setup for your computer and lets you require that every task an AI adds has a priority, a type and a due date.

Licence

The plugin in claude-plugin/ is MIT-licensed; everything else is all rights reserved. See LICENSE.md.

Source: README.md at commit d98d1e8

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

1
  1. v1.22.0LatestOct 25, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.