BuzzMeBro
Server Details
More than one roommate on your apartment buzzer number; settings decide who rings. Canada.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 20 tools
The consumer setup flow (check_building, create_setup, send_phone_code, confirm_phone_code, start_checkout, get_setup_status) and the partner flow are clearly distinct, and each tool maps to a specific step. A few partner tools (partner_get_links vs partner_list_sublinks, partner_get_stats vs partner_get_kit) are close in scope, but the descriptions do enough to separate them.
Nearly all tools follow a predictable snake_case verb_noun pattern (create_setup, send_phone_code, partner_get_stats, partner_rotate_key). The partner_* namespace prefix is applied consistently on one side and not the other, which is a minor asymmetry but still readable and predictable.
20 tools looks heavy at first glance, but the server serves two full workflows (a customer buzzer setup and a partner program with sublink management), and each tool appears to earn its place. Slightly over the ideal band but justifiable for the dual scope.
Both lifecycles are well covered: discovery, creation, phone verification, checkout, and status for customers; apply, verify, terms, key claim, links, stats, kit, sublink create/list/disable, payout, and key rotation for partners. Minor gaps exist (no way to cancel an abandoned setup or permanently delete a sublink), but agents can work around them.
Available Tools
20 toolscheck_buildingCheck a buildingARead-onlyIdempotentInspect
Checks whether BuzzMeBro can give this building a local buzzer number, and returns the price, the free-trial terms and how the service works. Call this first. Stores nothing and costs nothing.
Inputs: postal_code (required).
confirm_phone_codeConfirm the code the person read to youAIdempotentInspect
Checks the code the person read back to you. This proves the phone is theirs, which matters because that phone will open their front door. Five tries per setup. Next: start_checkout.
Inputs: code (required), setup_id (required), status_token (required).
create_setupSet up BuzzMeBro for the personAInspect
Creates a BuzzMeBro setup for the person and returns setup_id and a status_token you must keep for every later call (plus setup_url, a fallback link if you cannot relay a texted code). Only call it after check_building said available and the person has asked you to set it up. No text message is sent and nothing is charged by this call. Next: send_phone_code.
Inputs: unit (required), postal_code (required), mobile_phone (required), agent_name, +1 more.
get_setup_statusCheck setup progressAIdempotentInspect
Reads how far the setup has got and says what to do next. Once the person has paid, this call gets their number; when status is "ready" it returns their new BuzzMeBro number and swap_the_buzzer: the steps to get the building to point the buzzer at that number, and ready-to-send messages for building management, the landlord, the concierge, the superintendent or a building portal.
Inputs: setup_id (required), status_token (required).
partner_applyStart a partner application for the personAInspect
Starts a partner application with the person’s details and returns application_id and application_token. Only call it when the person has asked to join. No text is sent by this call. Next: partner_send_code.
Inputs: name (required), email (required), persona (required), mobile_phone (required), +3 more.
partner_claim_keyCollect the partner key (once)AInspect
After the person accepted the terms: returns their partner link, code and partner key. The key is shown once; keep it private and use it for the partner_get_* tools. The application token stops working after this call.
Inputs: application_id (required), application_token (required).
partner_confirm_codeConfirm the code the person read to youAIdempotentInspect
Checks the texted code. Five tries per application. Next: partner_terms_link.
Inputs: code (required), application_id (required), application_token (required).
partner_create_sublinkAdd a tracked linkAInspect
Adds a tracked link with its own code for one location, building or staff member (up to 50). Renters who use it count for this partner, with the same two-months-free perk.
Inputs: label (required), partner_key.
partner_disable_sublinkSwitch off a tracked linkADestructiveIdempotentInspect
Switches off one tracked link: its code stops bringing new apartments. Apartments it already brought stay with the partner.
Inputs: sublink_id (required), partner_key.
partner_get_kitReady-to-send messages for residentsBRead-onlyIdempotentInspect
Returns ready texts, a resident email, a move-in text and email to forward to new tenants, desk card and move-in insert wording with the partner’s link, links to the partner’s printable move-in package (move-in insert and QR card PDFs with their own QR and code), plus the house rules for sharing (honest words only, no pressure, never ask residents for phone numbers or door codes).
Inputs: partner_key.
partner_get_linksThe partner’s link, code and QRBRead-onlyIdempotentInspect
Returns the partner’s share link, typed code, a QR code (SVG) and their dashboard address.
Inputs: partner_key.
partner_get_statsThe partner’s numbersARead-onlyIdempotentInspect
Returns status, visits, signups, free months, paying apartments, collected revenue, earnings by state (on hold, ready, paid, reversed), the share ledger (apartments as codes only, never names or addresses) and payout history. Quote only these numbers.
Inputs: partner_key.
partner_list_sublinksThe partner’s tracked linksBRead-onlyIdempotentInspect
Lists the extra tracked links (one per location, building or staff member) with each one’s visits, apartments and earnings. Every apartment and every dollar rolls up to the partner.
Inputs: partner_key.
partner_payout_linkLink for the person to add their bank on StripeAInspect
Returns a one-time link to a BuzzMeBro page that sends the person to Stripe’s own secure page, where THEY confirm their identity and add their bank. You never see or type bank details. Payouts start once they have at least $25 ready. First-time setup only: once payouts work, payout changes are made by the partner on their signed-in dashboard. The partner gets a text whenever this link is made.
Inputs: partner_key.
partner_program_infoExplain the BuzzMeBro partner programARead-onlyIdempotentInspect
Returns how the partner program works: the 50% share of collected revenue, what counts and what does not, when and how payouts happen, the rules, and the steps to join. Call it first and explain it to the person before applying. Stores nothing.
Inputs: no named parameters.
partner_rotate_keyReplace the partner keyADestructiveInspect
Revokes the current partner key and returns a new one (shown once). Use it if the key may have leaked. The partner gets a text whenever the key is replaced.
Inputs: partner_key.
partner_send_codeText the person a confirmation codeAInspect
Texts a 6-digit code to the mobile number in the application (never any other number). Ask the person to read it to you, then call partner_confirm_code. Each application gets 3 codes, at least a minute apart.
Inputs: application_id (required), application_token (required).
partner_terms_linkGet the terms page for the personAInspect
Returns a one-time link to the partner terms. Give it to the person: they read the terms and press Accept themselves. You cannot accept for them. When they say it is done, call partner_claim_key.
Inputs: application_id (required), application_token (required).
send_phone_codeText the person a confirmation codeAInspect
Texts a 6-digit code to the mobile number given in create_setup (never to any other number). Tell the person a text is coming and ask them to read the code to you, then call confirm_phone_code. Call again only if it has not arrived after a minute; each setup gets 3 codes.
Inputs: setup_id (required), status_token (required).
start_checkoutGet the payment pageAIdempotentInspect
After confirm_phone_code: creates the person’s BuzzMeBro account and apartment and returns payment_url, Stripe’s own secure page where the person approves a card, Apple Pay, Google Pay or Link (with the free month when it applies, nothing is charged until it ends). Give them the link or message_for_the_person; you never see or type card details. Calling it again returns a fresh link for the same apartment.
Inputs: setup_id (required), status_token (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Buzz in deliveries and guests: apartment access codes, timed or recurring entry, and access history.
Condo residents in Malaysia: visitor passes, parcels, bills, facility bookings and notices.
Split rent and utilities by room, settle up and generate roommate agreements. Free.
Private phone numbers so AI agents can call each other, on one person's computers or between people.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI agents to autonomously manage incoming packages by logging parcels, cross-referencing unit directories, surfacing aging uncollected items, and recording pick-up signatures without physical locker hardware.3MIT
- AlicenseAqualityCmaintenanceEnables pre-approving deliveries and visitors at your gate via the NoBrokerHood resident app, so you or an LLM can automate gate access.6MIT
- AlicenseNot gradedqualityCmaintenanceA self-hosted MCP server that lets a homeowner give sitters, dog walkers, and family short spoken pass codes so whoever is home can ask Alexa+ about notes, routines, and emergencies and hear only the parts they're allowed to. Unanswered questions are routed to the owner, who replies by voice, and the answer is saved as a shared note for next time.MIT

Family Relayofficial
AlicenseNot gradedqualityCmaintenanceEnables an Alexa+ add-on to relay spoken messages between household members by voice alone, learning voices and names from everyday conversation without enrollment. It weaves pending messages and replies into assistant responses, with 24-hour expiry and delivery receipts.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.