Skip to main content
Glama
Busy Bar MCP Server

Busy Bar MCP Server

by nuxnik

Related Servers

Alternatives to Busy Bar MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for LobbyStack, an open-source AI receptionist. 18 tools to read calls, messages and contacts, check availability, book and change appointments, and update opening hours and FAQs. Streamable HTTP with OAuth or API keys.
      63
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Lightweight MCP server providing system time tools (current time, date, datetime, time components, unix timestamp) for LLM applications.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      The Time MCP Server is a Model Context Protocol (MCP) server that provides AI assistants and other MCP clients with standardized tools to perform time and date-related operations. This server acts as a bridge between AI tools and a robust time-handling back
      112 npm
      25
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that wraps the TimePRO API, enabling AI assistants to automatically create, view, and manage timesheets for authenticated users. It provides tools for searching clients and projects, retrieving configuration defaults, and performing full CRUD operations on timesheet entries.
      10
      MIT

    TDQS

    A3.9/5.0

    Scored across 28 tools

    Disambiguation3/5

    Most tools target distinct endpoints, but there is overlap between the comprehensive get_device_status and its individual sub-getters (e.g., get_device_info, get_firmware_info, get_system_status, get_power_status), which could lead to redundant calls. Similarly, get_transport and get_wifi_status both relate to network connectivity, and the three account getters (info/status/backend) are closely related, though descriptions help differentiate them.

    Naming Consistency4/5

    The naming pattern is overwhelmingly consistent: almost every tool follows get_<resource>. The only deviations are list_storage_files (uses 'list' instead of 'get') and get_tzlist (a slightly non-standard noun form for a list), but these are minor and do not seriously disrupt the overall pattern.

    Tool Count2/5

    28 tools is above the threshold where a toolset starts to feel heavy; the calibration suggests 25+ tools is too many. While each tool corresponds to a distinct device endpoint, the sheer number of read-only getters makes the surface feel bloated and could overwhelm an agent, especially since many are minor status variations.

    Completeness2/5

    The tool surface is entirely read-only—there are no set, update, create, or delete operations. This is a significant gap for a device management server, as users cannot change brightness, volume, timezone, device name, firmware update settings, or perform any configuration action. The description of get_tzlist even references set_timezone, implying such functionality should exist but does not.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues