Schema | BotBell MCP Server

BotBell MCP Server

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

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }
`prompts`	{ "listChanged": true }

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).

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

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/qq418716640/botbell-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server