BumbleBox

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as ai.bumblebox/mail and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 22 Oct 2026. Not supplied by the maker.

• search_emails

  Searches every connected mailbox (sender, subject, preview), newest first. Operators: from:, subject:, before:YYYY-MM-DD, after:YYYY-MM-DD; the rest is free text. Deleted emails are not returned.

• get_email

  One email in full: sender, recipients, date, subject, plain-text body, attachment names, folder and BumbleBox classification.

• list_to_answer

  Received emails BumbleBox classified as needing a reply and still in the inbox, newest first.

• search_contacts

  Contacts BumbleBox knows from the mail history (name, address, organization domain, exchange counts, last exchanges, VIP mark, note), matched on name, address or domain.

• list_folders

  The folders of each connected mailbox, as last synced. Trash, spam, sent and drafts are left out.

• list_calendar_events

  Events of the connected Google calendars between two dates (default: the next 7 days, at most 62 days).

• draft_reply

  Saves the text as the reply draft of a received email, from the mailbox that received it. Nothing is sent: the draft waits in BumbleBox (Pilotage › prepared replies) until the user reviews it and clic

• send_reply

  Replies to the sender of one received email, and only to them (no Cc, no Bcc, no attachment), from the mailbox that received it. What happens next is the level the user set in BumbleBox for this kind

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.