BotBell MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOTBELL_TOKEN | Yes | The primary authentication token. Supports Bot Token (prefix 'bt_') for single bot access or Personal Access Token (prefix 'pak_') for full control over all bots. | |
| BOTBELL_EXTRA_TOKENS | No | Optional additional Bot Tokens from multiple accounts. Format: alias1:bt_token1,alias2:bt_token2 |
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
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| botbell_sendA | Send a push notification to the user's iPhone/Mac via BotBell. You can include action buttons for quick replies. Use type 'input' to let the user type a custom response. |
| botbell_get_repliesA | Check if the user has replied to your messages in the BotBell app. Messages are consumed on fetch (won't be returned again). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| notify | Send a push notification to the user's phone with a summary of your work |
| ask | Ask the user a question via push notification and wait for their reply |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have entirely distinct purposes: one sends notifications, the other checks for replies. There is no overlap or ambiguity.
Both tools follow a consistent botbell_ prefix and verb_noun pattern (get_replies, send), making them easy to distinguish and predict.
With only two tools, the server is minimal but covers the core send/reply cycle for a notification service. Slightly below average count but still reasonable.
The tools cover the essential operations for a push notification service: sending and retrieving replies. Minor gaps like history or subscription management are present but not critical for basic functionality.