BumbleBox

Tools

• search_emailsSearches every connected mailbox (sender, subject, preview), newest first. Operators: from:, subject:, before:YYYY-MM-DD, after:YYYY-MM-DD, in:sent (only what the user sent, from any mailbox or alias); the rest is free text. Deleted emails are not returned.
• get_emailOne email in full: sender, recipients, date, subject, plain-text body, attachment names, folder and BumbleBox classification.
• list_to_answerReceived emails BumbleBox classified as needing a reply and still in the inbox, newest first.
• search_contactsContacts BumbleBox knows from the mail history (name, address, organization domain, exchange counts, last exchanges, VIP mark, note), matched on name, address or domain.
• list_foldersThe folders of each connected mailbox, as last synced. Trash, spam, sent and drafts are left out.
• list_calendar_eventsEvents of the connected Google calendars between two dates (default: the next 7 days, at most 62 days).
• draft_replySaves the text as the reply draft of a received email, from the address the email was written to (a brand address or the mailbox). needsIdentity: that address cannot send until the user verifies it in BumbleBox. Nothing is sent: the draft waits in BumbleBox (Pilotage › prepared replies) until the user reviews it and clicks Send. Saving again replaces the previous draft of the same email.
• send_replyReplies to the sender of one received email, and only to them (no Cc, no Bcc, no attachment), from the address the email was written to. What happens next is the level the user set in BumbleBox for this kind of reply: a draft, a reply waiting for one tap (the default), or a reply that leaves after a delay the user can cancel. Anything that commits the user (amounts, bank details, acceptance, contracts, dates, links) always waits for the user, and so does a reply from an address the user has not verified (needsIdentity). The result says which one applied.
• archive_emailMoves one inbox email to its mailbox's archive folder, on the mail server too. Undone by restore_to_inbox. Nothing is deleted.
• move_emailMoves one inbox email to an existing folder of the same mailbox (see list_folders), on the mail server too. No folder is created. Undone by restore_to_inbox.
• trash_emailMoves one inbox email to its mailbox's trash when BumbleBox certifies it as noise (spam, newsletter, promotion, with a unanimous safety vote and no known contact or action word). Any other email is not moved: it becomes a proposal the user confirms in one tap in BumbleBox. Never a permanent deletion; undone by restore_to_inbox.
• restore_to_inboxMoves an archived, filed or trashed email back to the inbox, on the mail server too.
• list_missionsThe user's prospection campaigns (missions), most recently active first, with the number of drafts waiting, emails sent and prospects who replied.
• list_campaign_draftsThe drafts of one campaign that wait for the user to validate them in BumbleBox (recipient, subject, plain-text body, sender), newest first, with the true totals.
• list_replies_to_validateReplies received on campaigns that still need the user: prepared reply drafts waiting for validation, and replies with no answer yet (with the stored AI triage: kind, summary, whether a human is needed).
• create_campaign_draftWrites one draft inside an existing campaign, to one recipient (added to the campaign list if new), from the campaign's sender. Nothing is sent: the draft waits for the user to validate the campaign send in BumbleBox.
• update_campaign_draftChanges the subject, body or recipient of a draft that is still a draft. Nothing is sent, and a draft the user already validated cannot be changed.

Updated：2026-10-29 (tools/list verified)

Configure in Claude / Cursor

{
  "mcpServers": {
    "remote-ai-bumblebox-mail": {
      "type": "http",
      "url": "https://api.bumblebox.ai/api/mcp"
    }
  }
}