BeeBoo MCP Server
Related Servers
Alternatives to BeeBoo MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables 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.-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to request human approvals with customizable forms, webhooks, and team features.46 npmMIT

HiveFlow MCP Serverofficial
AlicenseBqualityCmaintenanceConnects AI assistants (Claude, Cursor, etc.) directly to the HiveFlow automation platform, allowing them to create, manage, and execute automation flows through natural language commands.910 npm4MIT- AlicenseAqualityDmaintenanceHuman-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.11MIT
- AlicenseBqualityDmaintenanceProvides a document database with search, retrieval, and creation tools, and a task tracker with search and status filtering, enabling AI agents to manage documents and tasks via natural language.3MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables 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
Scored across 8 tools
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.
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.
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.
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.