Use rtm with AI assistants
Both programs include an MCP server, so an AI assistant such as Claude Desktop or Claude Code can list your items, projects and contexts, and add, edit, complete, reopen and delete items. Use whichever program you installed:
rtmcli mcpserves one file, from-for$TODOTXT.rtmapp mcpserves the files open in the desktop app (its[[files]]inrtm/config.toml), the shown one first, and picks up files you add or rename there. The app does not need to be running, and no window opens.
Add exactly one rtm server to each client, rtmcli mcp or rtmapp mcp, not both, and name it
rtm. A second rtm server in the same client offers no tools.
Clients may start the server without your shell's environment. Pass the variables it needs
explicitly (-e in Claude Code, env in Claude Desktop): TODOTXT, RTM_NO_SYNC and RTM_VCS
for rtmcli mcp, and XDG_CONFIG_HOME for rtmapp mcp if you set it (GNU/Linux), so that it finds
rtm/config.toml.
The server runs on your computer and talks to the client over stdin and stdout. It uses the network only to sync with your repository's remote; the items the assistant reads reach its AI service like anything else you show it. It can use only the files listed above, never a path the assistant names. Changes are saved and synced as rtmcli saves and syncs them: each change is committed and pushed at once when the file is in a Git or Pijul repository (see Syncing in the README), and the desktop app, if it is open, shows them. Deleting is marked as destructive, so clients that confirm tool calls ask you first.
Where the programs are, once installed:
| Installed from | rtmcli | rtmapp |
|---|---|---|
| deb, RPM | /usr/bin/rtmcli | /usr/bin/rtmapp |
| AppImage | the .AppImage file itself, wherever you keep it | |
| macOS | where you moved it | /Applications/Rusty Todo.txt Manager.app/Contents/MacOS/rtmapp |
| Windows | where you moved it | C:\Program Files\Rusty Todo.txt Manager\rtmapp.exe |
| Nix profile | ~/.nix-profile/bin/rtmcli | ~/.nix-profile/bin/rtmapp |
| NixOS system | /run/current-system/sw/bin/rtmcli | /run/current-system/sw/bin/rtmapp |
Claude Code
claude mcp add --scope user rtm -- rtmcli mcp -f ~/todo.txt
or, for the desktop app's files, claude mcp add --scope user rtm -- rtmapp mcp (on macOS, the full
path from the table). --scope user makes it available in every directory; without it, only in the
current one. On Windows, quote paths with spaces:
claude mcp add --scope user rtm -- "C:\Program Files\Rusty Todo.txt Manager\rtmapp.exe" mcp.
Environment variables go before the name: claude mcp add --scope user -e RTM_VCS=git rtm -- ....
Claude Desktop
Open Settings > Developer > Edit Config, which opens claude_desktop_config.json
(~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows), and add the
server under mcpServers:
{
"mcpServers": {
"rtm": {
"command": "/usr/local/bin/rtmcli",
"args": ["-f", "/Users/me/todo.txt", "mcp"]
}
}
}
or, for the desktop app's files:
{
"mcpServers": {
"rtm": {
"command": "/Applications/Rusty Todo.txt Manager.app/Contents/MacOS/rtmapp",
"args": ["mcp"]
}
}
}
Then restart Claude Desktop. Claude Desktop does not start the server from a shell, so:
- Use absolute paths for the command and the file:
~and environment variables are not expanded. On Windows, write backslashes twice ("C:\\Users\\me\\todo.txt"). - Your shell's environment does not reach the server. Put the variables it needs (see above) in an
envobject next toargs, for example"env": {"RTM_VCS": "git"}.rtmapp mcptakes its other settings, sync included, fromrtm/config.toml. - Syncing runs the
gitorpijulon thePATHthe client gives the server. If yours is elsewhere (Homebrew's/opt/homebrew/bin, for example), setPATHinenvtoo; without it, changes are saved but not synced.
Other clients
Any MCP client that starts local servers over stdio works the same way: the command is rtmcli
with the arguments -f <file> mcp, or rtmapp with mcp.