An MCP server for the busy bar
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"busybar-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Busy Bar MCP Server A Python [MCP](https://modelcontextprotocol.io/) server written with [FastMCP](https://fastmcp.endpoints.com/) that wraps the **[busybar_python_sdk](https://github.com/nuxnik/busybar-python-sdk)** to communicate with a physical [Busy Bar](https://busy.app/) device over HTTP. The Busy Bar is a digital time-management display — this MCP server provides 32 tools for account retrieval, system information, time operations, BLE control, and input events, exposing its functionality through the standard Model Context Protocol so other tools and AI assistants can interact with it programmatically. > **Status:** 32 MCP tools are fully implemented across account retrieval, system information, time operations, device state queries, BLE control, and input events, with a complete test suite. The project is ready to use — see the [What's Next](#whats-next) section below for planned work. ## Prerequisites - **Python ≥ 3.12** — the project pins Python 3.12+ (see `.python-version`) - **[uv](https://github.com/astral-sh/uv)** — dependency manager and virtual environment resolver ## Installation Clone the repository and install dependencies: ```sh uv sync ``` This creates a virtual environment and installs all packages declared in `pyproject.toml` (including `busybar_python_sdk`). ## Configuration The server supports configuration through either a `.env` file or environment variables. The same two variables are required in both cases: | Variable | Description | Example | |---|---|---| | `BUSYBAR_API_TOKEN` | API auth token for authenticating with the Busy Bar device | `my-super-secret-token` | | `BUSYBAR_BASE_URL` | IP address or hostname of the Busy Bar device (no protocol prefix) | `10.0.4.20` | ### Using `.env` Create a `.env` file in the project root: ```env BUSYBAR_API_TOKEN=my-super-secret-token BUSYBAR_BASE_URL=10.0.4.20 ``` The server loads `.env` when it starts. ### Using environment variables You can also configure the server through va…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.