MCP server for interacting with your LINE Official Account
Nothing to run from here
BuzzMeBro is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
17
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Set up an apartment buzzer number that rings every roommate’s phone. Canada.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http buzzmebro-mcp https://buzzmebro.com/api/mcp
# 2 — ask your agent for something these tools do
# check_building, create_setup, send_phone_code and 14 more
BuzzMeBro costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
BUAll 1 server
buzzmebro1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http buzzmebro-mcp https://buzzmebro.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
17 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| postal_code | string | yes | The apartment building’s postal code, e.g. "M4B 1B3". Canadian postal codes only for now. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| postal_code | string | yes | The apartment building’s postal code, e.g. "M4B 1B3". Canadian postal codes only for now. |
| unit | string | yes | Their apartment or unit number as the lobby panel lists it, e.g. "1502", "B" or "PH3". |
| mobile_phone | string | yes | The person’s own mobile number. It becomes the first phone the buzzer rings and how they sign in; we text it a code when they open the link. |
| referral_code | string | no | Optional BuzzMeBro referral code from a friend. |
| agent_name | string | no | Optional: your name as the person knows you (e.g. "ChatGPT", "Claude"), shown on their link page. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setup_id | string | yes | setup_id from create_setup. |
| status_token | string | yes | status_token from create_setup. Keep it private. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setup_id | string | yes | setup_id from create_setup. |
| status_token | string | yes | status_token from create_setup. Keep it private. |
| code | string | yes | The digits from the BuzzMeBro text, e.g. "482913". |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setup_id | string | yes | setup_id from create_setup. |
| status_token | string | yes | status_token from create_setup. Keep it private. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| setup_id | string | yes | setup_id from create_setup. |
| status_token | string | yes | status_token from create_setup. Keep it private. |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The person’s name. |
| mobile_phone | string | yes | The person’s own Canadian mobile number. We text it a code. |
| string | yes | The person’s email. | |
| persona | string | yes | How they meet renters. |
| building | string | no | Optional: the building or company they work with. |
| employer_ok | boolean | no | If they work for a building or concierge company: has their employer allowed it? |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| application_id | string | yes | application_id from partner_apply. |
| application_token | string | yes | application_token from partner_apply. Keep it private; it collects the partner key once. |
Checks the texted code. Five tries per application. Next: partner_terms_link.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| application_id | string | yes | application_id from partner_apply. |
| application_token | string | yes | application_token from partner_apply. Keep it private; it collects the partner key once. |
| code | string | yes | The digits from the text. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| application_id | string | yes | application_id from partner_apply. |
| application_token | string | yes | application_token from partner_apply. Keep it private; it collects 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| application_id | string | yes | application_id from partner_apply. |
| application_token | string | yes | application_token from partner_apply. Keep it private; it collects the partner key once. |
Returns the partner’s share link, typed code, a QR code (SVG) and their dashboard address.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| partner_key | string | no | The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead. |
Returns ready texts, a resident email, desk card and move-in insert wording with the partner’s link, plus the house rules for sharing (honest words only, no pressure, never ask residents for phone numbers or door codes).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| partner_key | string | no | The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| partner_key | string | no | The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| partner_key | string | no | The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| partner_key | string | no | The partner key from partner_claim_key. On REST send it as "Authorization: Bearer <key>" instead. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install BuzzMeBro or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish BuzzMeBro can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.