Botbell MCP

What qq418716640/botbell-mcp MCP server does

The qq418716640/botbell-mcp MCP server gives compatible AI clients access to BotBell messaging. An agent can send a notification to the BotBell app, then retrieve replies written by the recipient. This supports workflows where a task runs asynchronously but still needs human confirmation, input, or status acknowledgment.

BotBell delivers notifications to iPhone, iPad, and Mac. Messages may include a title, attached URL, image URL, and interactive action buttons. The provided description also identifies Markdown support. Actions can represent choices such as approval or rejection, or open an input field for a typed response.

How it works

Authentication for qq418716640/botbell-mcp MCP server is selected from the token prefix. A bt_ bot token is restricted to one bot and provides a simpler single-bot setup. A pak_ personal access token can manage all bots associated with the account, including listing and creating bots.

The server exposes four tool names. botbell_send submits a notification, while botbell_get_replies retrieves responses from the BotBell app. In PAT mode, botbell_list_bots returns available bots so the client can obtain a bot_id, and botbell_create_bot creates another bot. Bot-token mode does not provide the bot-management tools.

Additional bot tokens can be configured under aliases. When an alias is supplied to sending or reply retrieval, the request uses that token instead of the primary one. PAT-mode bot listing includes bots associated with the extra tokens.

Setup and configuration

To run qq418716640/botbell-mcp MCP server, install the BotBell app from the App Store, create a bot or personal access token, and provide the resulting value as BOTBELL_TOKEN. The documented package is @botbell/mcp-server, and its MCP executable is botbell-mcp.

Claude Desktop configuration places the server under the mcpServers object with command set to botbell-mcp. Cursor and other MCP clients use the same command-and-environment pattern. Keep the token in the client environment configuration rather than passing it as a tool argument.

BOTBELL_EXTRA_TOKENS is optional. Its value is a comma-separated list in the form alias:token, such as separate aliases for operations and personal notifications. The primary token is used when no alias is given.

Tools and capabilities

• botbell_send: Sends a message through a selected bot. The message may be up to 4096 characters and can include an optional title, URL, image URL, and up to five actions.
• botbell_get_replies: Fetches replies, with a default maximum of 20 results. Replies from action buttons include the action key as well as message content.
• botbell_list_bots: Lists bots available through a PAT and helps identify the bot_id required by other PAT-mode operations.
• botbell_create_bot: Creates a bot with a required name of up to 50 characters and an optional description.

Action definitions require a key and label, each limited to 64 characters. An action can use the default button type or an input type; input actions may define a placeholder of up to 128 characters.

Limitations and notes

A bot token cannot provide multi-bot management because it is scoped to one bot. PAT mode is needed for listing and creating bots. Sending through a selected bot in PAT mode requires the relevant bot_id, normally obtained with botbell_list_bots.

Reply retrieval is polling-style access through botbell_get_replies; the material does not describe streaming events or delivery guarantees. The documented setup requires the BotBell app and a valid BotBell token. The supplied material does not state a software license or service pricing model.