Install from source
Install from source
Everything the installer automates, done by hand. This is also the only route on macOS, which has no published installer.
Requires Python 3.11 or newer.
Linux and macOS
cd /path/to/rubit-mcp-mail
conda create -p ./.venv python=3.12 pip -y # this machine has no python3-venv
./.venv/bin/python -m pip install -e .
A plain python3 -m venv .venv works just as well wherever python3-venv is
available.
Windows
Use a standard venv (no conda needed — venv ships with the Python installer
on Windows) from PowerShell:
cd C:\path\to\rubit-mcp-mail
py -3.12 -m venv .venv
.venv\Scripts\python.exe -m pip install -e .
Everywhere the rest of these docs show ./.venv/bin/rubit-mcp-mail, use
.venv\Scripts\rubit-mcp-mail.exe instead (or .venv\Scripts\python.exe -m rubit_mcp_mail if you'd rather not depend on the .exe shim). For example:
.venv\Scripts\rubit-mcp-mail.exe auth outlook
.venv\Scripts\rubit-mcp-mail.exe doctor
The config file lives at %USERPROFILE%\.config\rubit-mcp-mail\config.toml
— Path.home() / ".config" resolves there on Windows too. The simplest way to
create it is .venv\Scripts\rubit-mcp-mail.exe gui and adding an account there,
which writes the file for you; to do it by hand, use mkdir and a text editor
instead of the heredoc the
Configuration page shows:
mkdir $env:USERPROFILE\.config\rubit-mcp-mail
notepad $env:USERPROFILE\.config\rubit-mcp-mail\config.toml
keyring talks to the
built-in Windows Credential Manager with no extra setup, so the DBUS/keyring
workaround described in
Register with Claude clients
does not apply — every environment (terminal, Claude Desktop, a scheduled task)
can already reach the same credential store.Next
- Configure an account
- Sign in:
./.venv/bin/rubit-mcp-mail auth <account> - Verify:
./.venv/bin/rubit-mcp-mail doctor - Register with Claude