Skip to main content
Glama
Sign In
mcp-banshee

mcp-banshee

by thiscustodian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

mcp-banshee

When an alert really, really needs to be heard, an app can be ignored. A scream cannot.

A satirical MCP server for the modern household: instead of pushing a notification to a screen nobody looks at, mcp-banshee dispatches a noisy mythical creature to inform the occupants. The banshee wails. The dragon roars. The poltergeist throws a pan. Message delivered.

The premise

Household notification systems have a delivery problem. Phones buzz in rooms. Watches vibrate on wrists. The notifications pile up unread in some digital graveyard, while the washing machine floods the utility room for the fourth time this month.

mcp-banshee returns notifications to their natural state: audible, urgent, and impossible to ignore. Each alert is fulfilled by dispatching the appropriate creature, chosen by severity:

Severity

Creature dispatched

Audible effect

Household impact

info

Pixie

Tinkle

Mildly noticed

notice

Brownie

Grumble

Chores guilt-tripped

warning

Poltergeist

Crockery

Dogs alerted

urgent

Banshee

Wail

Everyone looks up

critical

Dragon

Roar

Windows rattle, plans change

The banshee is the default courier. Per Irish tradition she keens outside the house of the person being notified; mcp-banshee assumes the washing machine, not the relative, but the volume is comparable.

Related MCP server: pushover-mcp

Dispatch etiquette

  • One creature per alert. Stacking is available for connoisseurs (--stack 2).

  • Banshees are scheduled no earlier than 07:00 unless the alert is critical, in which case all bets are off.

  • Dragons require household consent and, in some terraced properties, neighbour consent.

  • At Halloween, dispatch rates are uncapped and the neighbours will assume you have friends round.

Quick start

node src/cli.mjs dispatch "Kettle boiled" --severity info
node src/cli.mjs dispatch "Dishwasher finished" --severity warning
node src/cli.mjs dispatch "Roof is leaking" --severity critical --stack 2

Or wire it into an MCP-speaking agent as a stdio server:

node src/server.mjs

Exposed MCP tools:

  • dispatch_alert — send a notification, get a creature back.

  • list_couriers — the current roster of mythical dispatchers.

Tools, honestly assessed

Strengths: zero dependencies, sub-millisecond dispatch, unlimited scale (mythical creatures do not union), and a notification channel measured in decibels rather than open rates.

Known limitations: does not currently support silent mode, nightowl households, or households located next to a church. Banshee keening has no acknowledge button. Dragon-related property damage is not covered by the licence.

Halloween clause

Between 20 October and 2 November the service reverts to its native habitat: everything is a notification, everything is a wail, and nobody questions why there is a dragon on the porch.

Licence

MIT. No banshees were harmed. Crockery was.

Available Tools

2 tools
dispatch_alertB

Notify the household by dispatching a mythical creature. Severity picks the courier; stack summons more of them.

Inputs: message (required), stack, severity.

list_couriersC

Return the current roster of mythical dispatchers.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: dispatch_alert performs an action (notify) while list_couriers is a read-only lookup. There is no plausible way to confuse them, and the descriptions reinforce the boundary.

    Naming Consistency5/5

    Both names follow a clean verb_noun pattern (dispatch_alert, list_couriers). The convention is predictable and unambiguous.

    Tool Count3/5

    Two tools is thin for a functional server; the surface is essentially a single action plus a supporting lookup. It is not egregiously wrong for a whimsical notification utility, but it borders on under-scoped.

    Completeness3/5

    Core dispatch is covered, but there is no way to manage the courier roster (add/remove/configure), no delivery status or history, and no visibility into what severity values exist. Agents can perform the primary action but hit dead ends for lifecycle management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • mcp-notify

      mrfqcentic
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to alert users locally by playing a notification sound and showing a system banner when a task finishes or attention is needed, with support for custom sounds and multiple MCP clients.
      2
      59 npm
      MIT

    • pushover-mcp

      joshuawowk
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables sending push notifications to phones and other devices from any MCP client, with tools for validating users, listing sounds, checking limits, and managing emergency receipts.
      MIT

    • notifs

      Rottenwooood
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to send notifications through a local relay, inspect events and deliveries, and check whether alerts actually reached configured channels. It also provides prompts and a contract resource for building scripts, monitors, and pollers.
      25 npm
      MIT