BeeBoo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BEEBOO_API_KEY | Yes | Your BeeBoo API key (e.g., bb_sk_xxxxxxxxxxxx) | |
| BEEBOO_API_URL | No | The BeeBoo API endpoint | https://beeboo-api-625726065149.us-central1.run.app |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| beeboo_knowledge_searchC | Search the BeeBoo knowledge base for information using semantic search |
| beeboo_knowledge_addC | Add a new entry to the BeeBoo knowledge base |
| beeboo_knowledge_listB | List all knowledge base entries |
| beeboo_approval_requestA | Request human approval for an action. Use this when you need explicit permission before proceeding with a potentially impactful operation. |
| beeboo_approval_checkC | Check the status of an approval request |
| beeboo_approvals_listB | List all approval requests with optional status filter |
| beeboo_request_createB | Create a work request for the team. Use this to queue up tasks that need human attention or execution. |
| beeboo_requests_listC | List all work requests with optional status filter |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.