BuzzMeBro

com.buzzmebroPublished by buzzmebro.comOfficial publisherv1.2.0Updated Oct 24, 2026

More than one roommate on your apartment buzzer number; settings decide who rings. Canada.

Overview

AI-generated overview

BuzzMeBro lets an assistant set up a shared apartment buzzer number, walk a person through phone verification and Stripe checkout, and manage a partner referral

What you can do
Check whether a building can get a local buzzer number, with price and trial terms, then create a setup and text/confirm a phone code to prove the number is the person's own before checkout. Read setup status and, once paid, return the new buzzer number and steps to have the building point the buzzer at it. Start a partner application, verify it by texted code, hand over the terms link, then claim the partner key and links. Retrieve partner kit texts, QR codes and printable move-in materials, and read stats, sublink performance and payout history. Create, list, disable and rotate partner tracked links and keys.
When to use it
Use it when someone in a Canadian apartment with a shared buzzer wants their own number so calls reach them, or when a partner (for example a landlord or building staff) wants referral links, materials and earnings figures.
Requirements
A remote streamable HTTP endpoint; no local package, environment variables or headers declared. The person needs a mobile number to receive texted codes and a card, Apple Pay, Google Pay or Link for Stripe checkout; partners need a Stripe payout setup.
Before you install
The server handles account creation, phone verification and payments: checkout goes to Stripe and nothing is charged until the free month ends. Partner keys are shown once and must be kept private; rotate the key if it may have leaked. Payout links are one-time and bank details are entered by the person on Stripe, not by the assistant. Actions create accounts, applications and tracked links, and disabling a sublink stops new apartments from counting.

Installation

In SourceWeft

  1. Open BuzzMeBro in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.buzzmebro%2Fbuzzmebro/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "buzzmebro": {
      "type": "http",
      "url": "https://buzzmebro.com/api/mcp"
    }
  }
}

Tools

20

check_building

Check a building

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.

Parameterspostal_coderequired

create_setup

Set up BuzzMeBro for the person

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.

Parametersunitrequiredagent_namepostal_coderequiredmobile_phonerequiredreferral_code

send_phone_code

Text the person a confirmation code

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.

Parameterssetup_idrequiredstatus_tokenrequired

confirm_phone_code

Confirm the code the person read to you

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.

Parameterscoderequiredsetup_idrequiredstatus_tokenrequired

start_checkout

Get the payment page

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.

Parameterssetup_idrequiredstatus_tokenrequired

get_setup_status

Check setup progress

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.

Parameterssetup_idrequiredstatus_tokenrequired

partner_program_info

Explain the BuzzMeBro partner program

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.

Takes no parameters.

partner_apply

Start a partner application for the person

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.

Parametersnamerequiredemailrequiredpersonarequiredbuildingemployer_okpayouts_offmobile_phonerequired

partner_send_code

Text the person a confirmation code

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.

Parametersapplication_idrequiredapplication_tokenrequired

partner_confirm_code

Confirm the code the person read to you

Checks the texted code. Five tries per application. Next: partner_terms_link.

Parameterscoderequiredapplication_idrequiredapplication_tokenrequired

partner_claim_key

Collect the partner key (once)

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.

Parametersapplication_idrequiredapplication_tokenrequired

partner_get_kit

Ready-to-send messages for residents

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).

Parameterspartner_key

partner_get_stats

The partner’s numbers

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.

Parameterspartner_key

partner_rotate_key

Replace the partner key

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.

Parameterspartner_key

Version history

2
  1. v1.2.0LatestOct 15, 2026
  2. v1.1.0Oct 13, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.