BeeBoo MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@BeeBoo MCP Server request approval to deploy the new database schema"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
BeeBoo MCP Server
Model Context Protocol (MCP) server for BeeBoo — Human-in-the-Loop Infrastructure for AI Agents.
This server enables AI agents like Claude, Cursor, and Windsurf to natively interact with BeeBoo's capabilities:
Knowledge Base — Search, add, and list knowledge entries
Approvals — Request and check human approval status
Work Requests — Create and track work requests
Quick Start
1. Get your API Key
Get your BeeBoo API key from beeboo.ai/settings/api-keys.
Your key will look like: bb_sk_xxxxxxxxxxxx
2. Install & Configure
Choose your AI tool:
Claude Desktop
Add to your claude_desktop_config.json:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"beeboo": {
"command": "npx",
"args": ["-y", "@beeboo/mcp-server"],
"env": {
"BEEBOO_API_KEY": "bb_sk_your_key_here"
}
}
}
}Then restart Claude Desktop.
Cursor
Add to your Cursor settings (~/.cursor/mcp.json or via Settings > MCP):
{
"mcpServers": {
"beeboo": {
"command": "npx",
"args": ["-y", "@beeboo/mcp-server"],
"env": {
"BEEBOO_API_KEY": "bb_sk_your_key_here"
}
}
}
}Windsurf
Add to your Windsurf MCP configuration:
{
"mcpServers": {
"beeboo": {
"command": "npx",
"args": ["-y", "@beeboo/mcp-server"],
"env": {
"BEEBOO_API_KEY": "bb_sk_your_key_here"
}
}
}
}Alternative: Local Install
npm install -g @beeboo/mcp-serverThen use beeboo-mcp-server instead of npx @beeboo/mcp-server.
Related MCP server: Finizi B4B MCP Server
Available Tools
Tool | Description |
| Search the knowledge base using semantic search |
| Add a new entry to the knowledge base |
| List all knowledge base entries |
| Request human approval for an action |
| Check status of an approval request |
| List all approval requests (with optional filter) |
| Create a work request for the team |
| List all work requests (with optional filter) |
Usage Examples
Once configured, you can ask your AI assistant:
Knowledge Base:
"Search the knowledge base for deployment procedures"
"Add to the knowledge base: our AWS account ID is 123456789"
"List all knowledge entries"
Approvals:
"I need approval to delete the staging database"
"Check if approval abc123 has been approved"
"Show me all pending approvals"
Work Requests:
"Create a high-priority request to update the SSL certificate"
"List all open work requests"
Environment Variables
Variable | Required | Default | Description |
| Yes | — | Your BeeBoo API key |
| No |
| API endpoint |
Testing
Test the server locally:
# List available tools
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | BEEBOO_API_KEY=your_key node index.js
# Test a tool call
echo '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"beeboo_knowledge_list","arguments":{}}}' | BEEBOO_API_KEY=your_key node index.jsTroubleshooting
"BEEBOO_API_KEY environment variable is required"
Make sure you've set the BEEBOO_API_KEY in your MCP configuration.
Server not appearing in tools list
Restart your AI tool (Claude Desktop, Cursor, etc.)
Check the configuration file path is correct
Verify the JSON syntax is valid
API errors
Check your API key is valid
Ensure you have network connectivity
Check the BeeBoo status at status.beeboo.ai
Development
# Clone the repo
git clone https://github.com/beeboo-ai/beeboo.git
cd beeboo/mcp-server
# Install dependencies
npm install
# Run locally
BEEBOO_API_KEY=your_key npm startLicense
MIT
Available Tools
8 toolsbeeboo_approval_checkC
Check the status of an approval request
Inputs: id (required).
beeboo_approval_requestA
Request human approval for an action. Use this when you need explicit permission before proceeding with a potentially impactful operation.
Inputs: title (required), description (required).
beeboo_approvals_listB
List all approval requests with optional status filter
Inputs: status.
beeboo_knowledge_addC
Add a new entry to the BeeBoo knowledge base
Inputs: title (required), content (required), tags.
beeboo_knowledge_listB
List all knowledge base entries
Inputs: no named parameters.
beeboo_knowledge_searchC
Search the BeeBoo knowledge base for information using semantic search
Inputs: query (required).
beeboo_request_createB
Create a work request for the team. Use this to queue up tasks that need human attention or execution.
Inputs: title (required), description, priority.
beeboo_requests_listC
List all work requests with optional status filter
Inputs: status.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
Bee governed intelligence for chat, code, research, documents, and memory.
Run business workflows and route requests for human approval from AI agents.
Shared business knowledge, tools and skills for AI agents, with citations and approval controls.
Ask people questions, get approvals and keep team decisions, from any AI agent.
Related MCP Servers
AlicenseBqualityFmaintenanceConnects AI assistants (Claude, Cursor, etc.) directly to the HiveFlow automation platform, allowing them to create, manage, and execute automation flows through natural language commands.94 npm4MIT- 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
- 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.-
- 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