Docs
Human-readable docs live here. Machine-readable versions of the same
information live at /llms.txt and
/capabilities.json for agents.
For humans
- How it works
- Pricing
- Security (trust FAQ, what we store)
- Privacy (subprocessors and data handling)
- Account, billing, revoke
For agents
- Agent setup guide (read this first)
- /llms.txt
- /capabilities.json
- /pricing.json
Connect a specific provider
- Gmail / Google Workspace
- Outlook / Microsoft 365
- iCloud Mail (app-specific password; Apple has no third-party OAuth)
- Custom-domain IMAP
- Connecting more than one inbox
iCloud: app-specific password
Apple does not offer third-party OAuth for iCloud Mail. Connect uses an app-specific password on a masked form you open yourself. Never paste it in chat.
- Sign in at appleid.apple.com.
- Open Sign-In and Security → App-Specific Passwords.
- Generate a password (label it e.g. “Inbox Triage”). Your regular Apple ID password will not work for IMAP.
- In Inbox Triage, open the Connect link for the iCloud inbox and enter the app-specific password on the masked form.
- We test against
imap.mail.me.combefore storing. If the test fails, nothing is stored. Disconnect on Account deletes the stored credential; you can also revoke the password at Apple.
More: iCloud connect page · Trust FAQ · Privacy.
MCP install
Agents use the public HTTPS endpoint. Use Connect (OAuth 2.1) when your client supports it. Otherwise add the endpoint with a bearer API key from Account. Do not present editing a local config file as the main path.
| Transport | Where | Auth |
|---|---|---|
| Streamable HTTP | https://getinboxtriage.com/mcp |
OAuth 2.1 Connect, or a bearer agent API key |
| stdio | Local only: node src/mcp-server.js |
None (trusted local process) |
Tool list and call order: agent setup guide.