BusyBar MCP
Related Servers
Alternatives to BusyBar MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI tools like Claude Code and Codex CLI to read and write serial port data, facilitating embedded development workflows such as coding, flashing, and debugging.24 npmMIT
- AlicenseAqualityDmaintenanceControl your Elgato Stream Deck from Claude Code with high-quality icons, full profile management, and task context aggregation from Slack, Notion, and GitHub.10MIT
- AlicenseNot gradedqualityCmaintenanceEnables you to see, start, read, message, approve, interrupt, and stop Claude Code sessions running in tmux across all your SSH-reachable machines from the Claude app, voice mode, or another session. Hooks report which sessions are waiting on you, a shared git-backed memory is injected into new sessions, and small jobs can be routed to local OpenAI-compatible models.MIT
- AlicenseAqualityBmaintenanceTalk to your Flipper Zero from Claude Code — or any MCP client. Storage, app deployment, screen capture, button automation, JavaScript execution on the device, and honest answers about what is nearby.66MIT
- AlicenseNot gradedqualityAmaintenanceConnects Claude, Cursor, VS Code, and other MCP clients to OpenCode's headless API, enabling users to ask questions, implement features, monitor background work, respond to questions and permissions, and review changes across projects. It provides tools, resources, and prompts for setup, multi-project workflows, and asynchronous coding task management.25,387 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code to see and drive Bambu Lab 3D printers over the local network via MQTT, providing status, file management, print control, filament, maintenance, and diagnosis without any cloud dependency.MIT
TDQS
Scored across 22 tools
Most tools target clearly distinct actions (show text, show pixels, play sound, screenshot, connect), so selection is generally unambiguous. However, bar_status, busybar_get_status, and busybar_get_connectivity overlap around device/connection state, and bar_clear versus the WM overlay lifecycle (show_message, start_timer, return_to_auto) leaves some uncertainty about which tool owns cleanup.
Two near-identical prefixes, bar_ and busybar_, refer to the same physical device, and the GitHub/weather integrations are unprefixed, creating a mixed namespace. Within each prefix patterns differ too: bar_text/bar_pixels are noun-only while busybar_get_status/list_apps follow verb_noun, so naming is readable but not predictable.
At 22 tools the surface is heavy for a single device-control server, sitting in the borderline 16-25 range. The display and WM operations justify most tools, but the three status readers and bundled GitHub/weather integrations inflate the count and could likely be consolidated.
Coverage is strong across display modes (text, pixels, progress, image, animation, sound, screenshot) and WM app control (list, switch, overlays, input, auto-return). Minor gaps remain: no explicit stop/cancel for a playing animation, sound, or active timer, and no brightness or volume control, though bar_clear and return_to_auto cover some cleanup.