Vybit Notifications MCP Server

Send push notifications with personalized sounds, manage vybits, reminders, subscriptions, and view notification logs through natural language.

Automation by Vybit (Flatiron Tek) API Key, OAuth2 active

Connect (Remote Server) GitHub Docs npm: @vybit/mcp-server

Overview

Vybit Notifications MCP Server is the official Model Context Protocol integration for Vybit, a push notification service that lets users attach personalized sounds (custom recordings or thousands of searchable sounds from freesound.org) to every alert. The server lets AI assistants create, trigger, and manage notification routes ("vybits") through natural conversation, providing full parity with the Vybit Developer API.

The server exposes 30 tools spanning eight functional areas: vybit management, reminders, public discovery, subscriptions, sound browsing, notification logs, access control (peeps), and usage monitoring. It is distributed as part of the official @vybit/vybit-sdk mono-repo maintained by Flatiron Tek, alongside the Vybit API SDK, OAuth2 SDK, CLI, and n8n nodes.

Two deployment modes are available: a hosted remote MCP server at https://api.vybit.net/v1/mcp (OAuth2-based, no installation required) and a local npm package (@vybit/mcp-server) authenticated with an API key. Both work with Claude Desktop, Claude Code, Cline, Zed, Continue.dev, and other MCP-compatible clients.

Tools

Tool	Description
`vybit_create`	Create a new vybit (notification route) with a chosen sound, trigger type, and metadata.
`vybit_list`	List all vybits owned by the authenticated user.
`vybit_get`	Retrieve details for a specific vybit by ID or key.
`vybit_update`	Update properties of an existing vybit.
`vybit_delete`	Delete a vybit.
`vybit_trigger`	Send a push notification through a specific vybit with a custom message.
`reminder_create`	Create a scheduled reminder that fires a vybit at a future time.
`reminder_list`	List active reminders.
`reminder_update`	Update a reminder's schedule or payload.
`reminder_delete`	Delete a reminder.
`vybits_browse_public`	Browse public vybits available to discover and subscribe to.
`vybit_get_public`	Get details on a single public vybit.
`subscription_create`	Subscribe to a public vybit to receive its notifications.
`subscriptions_list`	List the user's current subscriptions.
`subscription_get`	Get details about a subscription.
`subscription_update`	Update subscription preferences.
`subscription_delete`	Unsubscribe from a vybit.
`sounds_list`	Search the Vybit sound library (backed by freesound.org).
`sound_get`	Get details on a specific sound asset.
`logs_list`	List notification delivery logs across the account.
`log_get`	Retrieve a specific log entry.
`vybit_logs`	List delivery logs for a specific vybit.
`subscription_logs`	List logs for a specific subscription.
`peeps_list`	List 'peeps' (people granted access to your private vybits).
`peep_get`	Get a specific peep record.
`peep_create`	Invite a peep to access a private vybit.
`peep_delete`	Revoke a peep's access.
`vybit_peeps_list`	List peeps with access to a given vybit.
`meter_get`	Retrieve current API usage and quota metrics.
`get_current_time`	Return the server-side current time, useful for scheduling reminders.

Setup Guide

Prerequisites

A Vybit account (sign up and get an API key at developer.vybit.net)
Node.js 18+ for the local install option
An MCP-compatible client (Claude Desktop, Claude Code, Cline, Zed, Continue.dev, etc.)

Option 1: Hosted Remote Server (recommended)

Connect your MCP client directly to the hosted endpoint, no installation required:

https://api.vybit.net/v1/mcp

Authentication uses OAuth2: the client opens a browser to authorize, then receives an access token automatically.

Option 2: Local Installation

Install globally (optional):

npm install -g @vybit/mcp-server

Then add this to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "vybit": {
      "command": "npx",
      "args": ["-y", "@vybit/mcp-server"],
      "env": {
        "VYBIT_API_KEY": "your-api-key-here"
      }
    }
  }
}

Restart your MCP client to load the server.

Use Cases

Send build-failure or deploy-success push alerts with distinctive custom sounds from a CI/CD pipeline driven by an AI agent
Have an assistant create and schedule recurring reminder vybits (medication, meetings, standups) without leaving chat
Trigger high-priority on-call notifications with a unique siren sound when monitoring agents detect incidents
Browse and subscribe to public vybits (e.g. weather alerts, news bulletins) and route them to your devices
Review and audit notification delivery logs and API quota usage through natural language queries

Example Prompts

"Create a new vybit called 'Deploy Failed' using an alarm sound, then trigger it with the message 'Production deploy rolled back'."
"List all my vybits and show me which ones fired in the last 24 hours."
"Set a reminder on my 'Standup' vybit to fire every weekday at 9:55am."
"Find a doorbell sound in the library and create a vybit named 'Front Door' with it."
"How much of my Vybit API quota have I used this month?"

Pros

Official server maintained by Vybit (Flatiron Tek), with full parity to the Developer API across 30 tools
Offers both a zero-install hosted remote endpoint with OAuth2 and a local npm package with API key auth
Covers the entire lifecycle: creation, triggering, scheduling, subscriptions, access control, and observability
Distinctive value beyond plain notifications: personalized sounds make alerts immediately recognizable

Limitations

Requires a Vybit account and API key, and is tied to the Vybit notification service (not a generic push provider)
Delivery still depends on having the Vybit mobile/web client installed to receive notifications
Tool-level documentation in the public README is high level; detailed per-tool parameter schemas live inside the package

Alternatives

ntfy MCP server: community server for the open-source ntfy.sh pub/sub notification service
mcp-server-notify: sends local desktop system notifications when an agent task is done
Pushover integrations or community Pushover MCP wrappers for simple device push without custom sounds