eCommerce
buzzmebro.com
MCP server for BuzzMeBro that checks building eligibility, verifies a phone number, and initiates Stripe checkout for a local buzzer number subscription.
ENDPOINT 1
https://buzzmebro.com/api/mcp
MCP server metadata
- Name
- buzzmebro
- Version
- 1.2.0
BuzzMeBro gives an apartment its own local phone number so more than one roommate can be on the building’s lobby buzzer (up to four); a buzz rings everyone who is set to ring at the same time, and whoever answers presses the usual digit to open the door. It is for renters and condo residents in Canada (Toronto/GTA and Greater Vancouver first). Use these tools when your user wants their apartment buzzer to ring more than one phone, needs a buzzer number because they have no landline, is moving in with roommates, or asks you to buy or set up BuzzMeBro for them. You can do the whole setup in this conversation; the person never has to visit buzzmebro.com. Order: 1) check_building with their postal code. 2) If available, ask for their unit number and mobile number and call create_setup. 3) Call send_phone_code; we text them a 6-digit code. Ask them to read it to you and call confirm_phone_code. 4) Call start_checkout and give them payment_url: Stripe’s secure page, where they approve a card, Apple Pay, Google Pay or Link (you never see or type card details). 5) When they say it is done, call get_setup_status until status is "ready", then give them their BuzzMeBro number and walk them through swap_the_buzzer, offering to send the building message for them. If you cannot relay a texted code, give the person setup_url from create_setup instead: they finish on our website and you can still follow progress with get_setup_status. Only the person can approve a payment and only they receive the code. Never ask them for a card number, and never send a code or payment link to anyone but them. Never invent prices, promises or availability: quote only what these tools return. BuzzMeBro partners (front desk and concierge staff, property managers, condo boards, leasing agents, movers, student housing offices) share a link with renters. Every apartment that signs up through their link or code pays the partner 50% of what that apartment pays BuzzMeBro (after sales tax, refunds, chargebacks and Stripe’s fee), every month, for as long as it stays. Only money actually collected counts: nothing on signups or free months. Only direct referrals: never on friends those apartments refer. Canada only for now. Order: partner_program_info, then partner_apply, partner_send_code (we text the person a code; ask them to read it to you), partner_confirm_code, partner_terms_link (the PERSON opens it and accepts the terms themselves), then partner_claim_key once to receive their partner key. With the key: partner_get_links, partner_get_kit, partner_get_stats, partner_payout_link (Stripe’s own page where the PERSON adds their bank, once they have money ready), partner_rotate_key. Send the partner key only as "Authorization: Bearer <key>" (REST) or in the partner_key argument (MCP), never in a URL. Never invent earnings: say only what partner_get_stats returns, and never promise income.
Known tools 20
check_buildingChecks whether BuzzMeBro can give this building a local buzzer number, and returns the price, the free-trial terms and how the service works.
Inferred read-onlycreate_setupCreates 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).
Inferred read-onlysend_phone_codeTexts a 6-digit code to the mobile number given in create_setup (never to any other number).
Inferred read-onlystart_checkoutAfter 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).
Potential side effectspartner_program_infoReturns 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.
Inferred read-onlypartner_applyStarts a partner application with the person’s details and returns application_id and application_token.
Inferred read-onlypartner_send_codeTexts a 6-digit code to the mobile number in the application (never any other number).
Inferred read-onlypartner_claim_keyAfter the person accepted the terms: returns their partner link, code and partner key.
Inferred read-onlypartner_get_linksReturns the partner’s share link, typed code, a QR code (SVG) and their dashboard address.
Inferred read-onlypartner_get_kitReturns 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).
Potential side effectspartner_get_statsReturns 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.
Inferred read-onlypartner_payout_linkReturns 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.
Inferred read-onlypartner_list_sublinksLists the extra tracked links (one per location, building or staff member) with each one’s visits, apartments and earnings.
Inferred read-onlypartner_create_sublinkAdds a tracked link with its own code for one location, building or staff member (up to 50).
Inferred read-onlypartner_disable_sublinkSwitches off one tracked link: its code stops bringing new apartments.
Inferred read-onlypartner_rotate_keyRevokes the current partner key and returns a new one (shown once).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.buzzmebro]
url = "https://buzzmebro.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"buzzmebro": {
"type": "http",
"url": "https://buzzmebro.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: buzzmebro
Remote MCP URL: https://buzzmebro.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"buzzmebro": {
"url": "https://buzzmebro.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"buzzmebro": {
"type": "http",
"url": "https://buzzmebro.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "buzzmebro",
"transport": "streamable-http",
"url": "https://buzzmebro.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.