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., "@Bell call notify_done with summary 'Task complete'"
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.
Desktop popup notifications that ring when Claude pauses on you.
Claude Code: fires a popup on Stop (turn finished, only if the turn took >30s), Notification (Claude is idle or asking for permission), and SubagentStop.
Claude Desktop: exposes an MCP tool notify_done(summary) that Claude calls when it finishes a task.
Clicking the popup dismisses it and can bring the relevant Claude, VS Code, or terminal window to the front.
Bell records local notification history in ~/.bell/history.sqlite3 using SQLite. Each row includes timestamp, source, title, message, and focus target.
Popups center on the monitor containing the current foreground window. If monitor detection fails, Bell falls back to the primary-display behavior.
cd "C:\Users\<you>\Desktop\projects\bell"
py -m venv .venv
.\.venv\Scripts\Activate.ps1
pip install -e .Related MCP server: Notifications MCP Server
python -m bell.notify "Bell" "Hello from Bell" none
echo '{"hook_event_name":"Stop","session_id":"test-session","cwd":"C:\\tmp","transcript_path":"","stop_hook_active":false}' | python -m bell.hook
python -m bell.codex_notify turn-ended
python -m bell.doctorDo not wire this automatically from the repo build. In a later approved step, merge hook commands into the relevant Claude settings file.
The MCP entry point is:
python -m bell.mcp_serverCodex CLI/App can call Bell through its notify config:
notify = ["C:\\Users\\<you>\\Desktop\\projects\\bell\\.venv\\Scripts\\pythonw.exe", "-m", "bell.codex_notify"]Bell only opens a popup for Codex completion notifications: either the turn-ended wrapper event or a JSON payload with type = "agent-turn-complete". Other Codex notify invocations are logged to ~/.bell/bell.log and skipped without writing history.
Show a Bell popup when a task finishes; keep summary short, about 120 characters.
Inputs: summary (required), session. Returns: result
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 1 tool
With only one tool, there is no possibility of confusion. The tool's purpose is clearly defined and distinct.
A single tool name cannot be inconsistent. 'notify_done' follows a clear verb_noun pattern.
One tool for a simple notification purpose is reasonable, though the server could potentially benefit from additional tools like notify_error or notify_progress.
The single tool covers the core use case of notifying task completion, but lacks other common notification types, making it somewhat incomplete for broader notification needs.
Let your AI agent notify you by email, Slack, Discord, or webhook. One tool: send_notification.
Push notifications for AI agents - send instant iPhone notifications from any MCP client.
Turn user requests and support messages into tasks and tell users what shipped, from any AI agent.
Create Tasks and run Workflows in Bleep from Claude, ChatGPT, and other AI assistants.
