Skip to main content
Glama

Related Servers

Alternatives to BeeBoo MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with the Beep platform to manage bounties, assets, and payments. It supports operations for starting and stopping streaming sessions, verifying transactions, and issuing payments on the Beep network.
      -
    • A
      license
      B
      quality
      C
      maintenance
      Connects AI assistants (Claude, Cursor, etc.) directly to the HiveFlow automation platform, allowing them to create, manage, and execute automation flows through natural language commands.
      9
      10 npm
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Human-in-the-loop approval gate for AI agents. Your agent calls submit_approval before any irreversible action; a human reviews on a branded page; a signed webhook fires back with the decision.
      1
      1
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to interact with the Finizi B4B platform through 15 comprehensive tools for managing business entities, invoices, vendors, and products. Features secure JWT authentication, automatic retries, and full business-to-business workflow integration through natural language commands.
      MIT

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The tools are cleanly separated into three functional groups: approvals (check, request, list), knowledge base (add, list, search), and work requests (create, list). There is no overlap in functionality between these groups or within each group.

    Naming Consistency5/5

    All tools follow a perfect and consistent naming pattern: 'beeboo_' prefix followed by resource name (approval/knowledge/request) and action verb (check/request/list/add/search/create). The pattern is uniformly applied across all 8 tools with no deviations in style or structure.

    Tool Count5/5

    With 8 tools, the server is well-scoped for its purpose of handling approvals, knowledge management, and work requests. Each tool earns its place by providing distinct functionality within these three domains, neither feeling too sparse nor overloaded.

    Completeness4/5

    The tool surface provides excellent coverage for the three domains, with CRUD-like operations for each: approvals (request, check, list), knowledge (add, list, search), and work requests (create, list). Minor gaps include no update/delete operations for knowledge entries or work requests, but agents can work around this limitation.

    Maintenance

    ActivityInactive
    ResponsivenessSyncing