CLI
Every rubit-mcp-mail subcommand and flag.
CLI
rubit-mcp-mail [-v|--verbose] [--version] <command> [args]
Running it with no command at all is the same as serve — that is how MCP
clients launch it.
| Command | Arguments | What it does |
|---|---|---|
serve | — | Run the MCP server on stdio. The default. |
install | --console | First-time setup wizard: writes config, signs you in, registers with Claude, creates shortcuts. Opens a window, falling back to the terminal. |
uninstall | --console | Removes the config, stored secrets, shortcuts and installed binaries. |
auth | [account] | Interactive sign-in. Device-code flow for Outlook, password prompt otherwise. Omit the account when only one is configured. |
doctor | [account] | Checks config, credentials, connectivity and authentication, then lists folders with their detected roles. Exits 1 on failure. |
gui | — | Opens the settings window. |
permissions | — | The same window, opened on its Permissions tab. |
Global flags
| Flag | Effect |
|---|---|
-v, --verbose | Debug logging. |
--version | Print the version and exit. |
doctor
The one to reach for when something is wrong. It prints the config path it found, the secret backend in use, and a verdict per account:
rubit-mcp-mail doctor
It also names any [providers.*] overrides currently in effect, and lists every
folder with the role it was classified as — the quickest way to find out why
folder: "junk" isn't resolving on your server.
Ctrl-C during auth exits 130 rather than dumping a traceback.
From a source checkout
Prefix with the venv:
./.venv/bin/rubit-mcp-mail doctor # Linux / macOS
.venv\Scripts\rubit-mcp-mail.exe doctor # Windows