How it works
Your agent handles setup and triage. You approve payment and open one connect link per inbox. Credentials never go through chat.
Setup sequence
- Discover the service. Your agent reads
/llms.txtor the agent setup guide, then adds the public MCP endpointhttps://getinboxtriage.com/mcp. It signs in with OAuth 2.1 Connect, or uses a bearer API key once you have one. - Subscribe. The agent opens a checkout link for you to approve. The agent never sees card details.
- Issue an API key. Create one from Account (or via the account API). It is shown once. Anyone who holds it can read your synced mail, so store it like a password.
- Connect each inbox. The agent calls
add_inbox, thenstart_google_oauth,start_microsoft_oauth, orstart_imap_secret_capture. Each returns a human link. You open it: Google or Microsoft sign-in, or a masked form for iCloud/IMAP. Whichever link you get, you finish it in your browser. Do not paste passwords into chat. - Sync.
sync_inboxpulls the newest ~300 messages per selected folder (~40 for Gmail) into the triage window. - Triage.
list_messages/get_messageto read;create_draftto write a draft in your mailbox, which is never sent on its own;send_draftto send it once you turn sending on and approve the full message in chat (Gmail, iCloud, and IMAP; Microsoft is draft-only for now);trash_messageto move unwanted mail to Trash;mark_as_spamto move junk to Spam or Junk.
What you do vs. what the agent does
You approve
- The subscription charge
- Each inbox connect (OAuth click or app-password form)
- Revoking access or disconnecting an inbox
You never
- Paste a password or OAuth code into agent chat
- Watch a triage dashboard. The agent does that work
- Re-sync by hand. The agent calls
sync_inboxwhen it needs fresh mail