@marlinjai/email-mcp 1.7.2 → 1.8.1

package/README.md

@@ -123,7 +123,7 @@ npx -y -p @marlinjai/email-mcp@latest email-mcp-setup
 |------|-------------|
 | `email_list_accounts` | List all configured accounts with connection status |
 | `email_add_account` | Add a new IMAP or iCloud account (Gmail/Outlook require setup wizard) |
-| `email_remove_account` | Remove an account and its stored credentials |
+| `email_remove_account` | Remove an account and its stored credentials; revokes the Google grant for Gmail, removes Outlook tokens from the local token cache, and reports the outcome |
 | `email_test_account` | Test connection to an account |
 
 ### Reading & Searching (6)
@@ -248,6 +248,21 @@ export EMAIL_MCP_KEY="your-strong-passphrase"
 When `EMAIL_MCP_KEY` is set, existing credential files are transparently
 re-encrypted with the passphrase the next time they are read.
 
+The Outlook refresh token lives in the token cache of Microsoft's authentication
+library (MSAL), `~/.email-mcp/msal-cache.enc`, encrypted with the same scheme and key
+derivation as `credentials.enc`, so `EMAIL_MCP_KEY` protects both files. Versions before 1.8.0
+kept this cache as plain JSON in `~/.email-mcp/msal-cache.json`; 1.8.0 encrypts it and
+deletes the plain file the first time it reads it, without signing you out. Going back
+to an older version afterwards means signing in to Outlook again.
+
+On macOS and Linux, attachments saved with `email_save_attachment` are written
+owner-only (`0600`), and folders email-mcp creates for them are `0700`. They are not
+encrypted.
+
+The OAuth sign-in callback started by `email-mcp-setup` listens on the loopback
+addresses only (`127.0.0.1`, and `::1` when available), so nothing else on your network
+can reach it.
+
 ## Support
 
 If this project is useful to you, consider supporting its development: