BuzzerAPI

com.buzzerapiPublished by buzzerapi.comOfficial publisherv1.0.0Updated Oct 27, 2026

Buzz in deliveries and guests: apartment access codes, timed or recurring entry, and access history.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

BuzzerAPI is a remote MCP server that lets an assistant buzz in deliveries and guests, manage apartment access codes and timed or recurring entry, and review…

What you can do
  • Buzz in deliveries and guests through the building entry system.
  • Create and manage apartment access codes.
  • Set up timed or recurring entry windows.
  • Review access history for the apartment.
When to use it
Useful for residents who want an assistant to handle building entry remotely: letting a courier or visitor in, issuing temporary or recurring access codes, and checking who came in and when.
Requirements
A remote MCP endpoint at api.buzzerapi.com using streamable HTTP. Authentication is required via OAuth; no environment variables or headers are declared. A BuzzerAPI account and a compatible building entry setup are implied by the service.
Before you install
The server grants physical building access, so an assistant connected to it can let people in and create entry codes. Access history is personal data about comings and goings. OAuth authorization should be limited to the intended account, and access should be revoked if the connection is no longer needed.

Installation

In SourceWeft

  1. Open BuzzerAPI in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.buzzerapi%2Fbuzzerapi/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. The client completes OAuth sign-in on first connect.

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

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 23, 2026

Score

67% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

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