# BumbleBox Muse connector From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta. ## BumbleBox Search, triage and reply to emails across all your mailboxes with full control before sending. - Record: https://musedirectory.ai/connector/bumblebox - Category: Productivity - Developer: BumbleBox (https://bumblebox.ai/integrations) - Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse. - Health: Working, 763ms, checked 2026-10-29T20:16:15Z - Endpoint: https://api.bumblebox.ai/api/mcp - Auth: No account needed; Pricing: unknown - Screening: Screened, no issues found (2026-10-29T20:16:15Z) - Source: Found in the official MCP Registry (ai.bumblebox/mail) https://registry.modelcontextprotocol.io/v0/servers?search=ai.bumblebox%2Fmail Connects to your email accounts to search and organize messages, draft replies and outreach campaigns, and manage contacts. Muse can help you find emails, prepare responses, and handle inbox triage while you review and approve before anything is sent. Example request: "Find emails from my boss about the Q4 budget and draft a reply for me to review." How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use BumbleBox to help me. It is a free service with an MCP server at https://api.bumblebox.ai/api/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer. Tools: - 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 clicks Send. Saving again replaces the previous draft of the same email. - 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 of reply: a draft, a reply waiting for one tap (the default), or a reply that le - archive_email: Moves one inbox email to its mailbox's archive folder, on the mail server too. Undone by restore_to_inbox. Nothing is deleted. - move_email: Moves 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_email: Moves 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 - restore_to_inbox: Moves an archived, filed or trashed email back to the inbox, on the mail server too. - list_missions: The user's prospection campaigns (missions), most recently active first, with the number of drafts waiting, emails sent and prospects who replied. - list_campaign_drafts: The 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_validate: Replies 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_draft: Writes 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_draft: Changes 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. Screening checks: - MCP handshake: pass (Answered in 763ms) - Domain against threat feeds (Cloudflare security DNS): pass (api.bumblebox.ai, bumblebox.ai not flagged) - Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published) - Hidden instructions or invisible characters in tool text: pass (17 tools read, nothing found) - Inputs asking for passwords, card numbers or seed phrases: pass (None found) - Domain and redirects: pass (Domain registered 344 days ago) - AI review of purpose and tool behavior: pass (No concerns)