@vybit/mcp-server

Model Context Protocol (MCP) server for the Vybit Developer API. Enables AI assistants like Claude to interact with your Vybit notifications programmatically.

What is MCP?

Model Context Protocol (MCP) is an open protocol that standardizes how AI applications integrate with external data sources and tools. Think of it as a universal connector between AI assistants and your services.

Features

This MCP server provides AI assistants with full parity with the Vybit Developer API:

• Manage Vybits: Create, read, update, delete, and list owned vybits
• Trigger Notifications: Send notifications with custom messages, images, and links
• Browse Sounds: Search and explore available notification sounds
• View Notification Logs: See notification history for vybits and subscriptions
• Manage Access (Peeps): Invite people to private vybits and manage permissions
• Monitor Usage: Check API usage and limits
• Discover Public Vybits: Browse and search public vybits created by others
• Manage Subscriptions: Subscribe to public vybits, view subscriptions, and unsubscribe
• Manage Reminders: Create, list, update, and delete scheduled reminders on vybits

Prerequisites

1. Sign up at developer.vybit.net
2. Get your credentials (either option):
   • API Key: Navigate to the Developer API section, click "</> DEV" then "API Configuration"
   • OAuth2 Token: Complete the OAuth2 flow to obtain an access token

Hosted Remote MCP Server (Easiest)

Vybit provides a hosted remote MCP server at https://api.vybit.net/v1/mcp — no installation or API key management required. Connect directly from Claude or ChatGPT (may require paid plans):

Claude Desktop / Claude Web (claude.ai):

1. Open Settings → Connectors
2. Click Add Custom Connector
3. Enter the MCP URL: https://api.vybit.net/v1/mcp
4. You'll be redirected to authorize with your Vybit account via OAuth

ChatGPT Desktop / ChatGPT Web (chatgpt.com):

1. Open Settings → Apps → Advanced Settings
2. Toggle ON Developer Mode, Click "Create app"
3. Fill out and submit the New App form setting the MCP Server URL as https://api.vybit.net/v1/mcp
4. You'll be redirected to authorize with your Vybit account via OAuth

Once connected, all 30 MCP tools are available immediately through natural conversation.

Local Installation

If you prefer to run the server locally (e.g., for Claude Code, Cline, or other MCP clients that support stdio transport), you can install the npm package and configure with your API key.

Claude Desktop (MCPB — Recommended)

Download the latest .mcpb bundle from the releases page and double-click to install. Claude Desktop will prompt you for your Vybit API key during setup.

Claude Desktop (Manual)

Install the package globally:

npm install -g @vybit/mcp-server

Add to your Claude Desktop configuration file (use either VYBIT_API_KEY or VYBIT_ACCESS_TOKEN):

MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

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

Restart Claude Desktop to load the server.

Claude Code

Add to the current project (use either VYBIT_API_KEY or VYBIT_ACCESS_TOKEN):

claude mcp add vybit -e VYBIT_API_KEY=your-api-key-here -- npx -y @vybit/mcp-server

Or add across all projects (user-scoped):

claude mcp add vybit -s user -e VYBIT_API_KEY=your-api-key-here -- npx -y @vybit/mcp-server

You can also add manually to .claude/mcp.json in your project:

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

Other MCP Clients (Cline, Zed, Continue.dev, etc.)

Install globally with npm install -g @vybit/mcp-server, then configure your client to run npx -y @vybit/mcp-server with either VYBIT_API_KEY or VYBIT_ACCESS_TOKEN set in the environment.

Troubleshooting: nvm Users

GUI applications like Claude Desktop do not source your shell profile (.bashrc/.zshrc), so node and npx may resolve to the wrong Node version. If you see errors like SyntaxError: Unexpected token { or Cannot find module 'node:path', this is likely the cause.

To fix this, skip npx and use node directly with absolute paths:

# Find your node and global modules paths
which node
npm root -g

Then use those paths in your config:

{
  "mcpServers": {
    "vybit": {
      "command": "/Users/you/.nvm/versions/node/v24.6.0/bin/node",
      "args": ["/Users/you/.nvm/versions/node/v24.6.0/lib/node_modules/@vybit/mcp-server/dist/index.js"],
      "env": {
        "VYBIT_API_KEY": "your-api-key-here"
      }
    }
  }
}

Node 18+ is required. Use either VYBIT_API_KEY or VYBIT_ACCESS_TOKEN in the env block.

Usage

Once configured, you can ask your AI assistant to interact with Vybit:

Example Conversations

Manage Your Vybits:

You: Show me all my vybits
Claude: [Lists all your vybits with details]

You: Create a vybit called "Server Alert" with an alarm sound for webhooks
Claude: [Creates the vybit and shows the configuration]

You: Trigger my "Server Alert" vybit with message "CPU usage at 95%"
Claude: [Sends the notification]

View Notification History:

You: Show me recent notifications for my Server Alert vybit
Claude: [Lists notification logs for that vybit]

You: What notifications have I received from my subscriptions?
Claude: [Shows logs from subscribed vybits]

Manage Access:

You: Invite [email protected] to my "Family Updates" vybit
Claude: [Sends invitation to the email]

You: Who has access to my "Family Updates" vybit?
Claude: [Lists all peeps for that vybit]

Browse Sounds and Check Usage:

You: What alert sounds are available?
Claude: [Lists sounds matching "alert"]

You: How much of my API quota have I used today?
Claude: [Shows current usage and limits]

Set Up Reminders:

You: Create a vybit called "Daily Standup" with trigger type reminders
Claude: [Creates the vybit with triggerType=reminders]

You: Add a reminder to fire every weekday at 9am Denver time
Claude: [Creates reminder with cron "0 9 * * 1-5" and timezone "America/Denver"]

You: Change it to 9:30am instead
Claude: [Updates the reminder's cron to "30 9 * * 1-5"]

You: What reminders are set on my Daily Standup vybit?
Claude: [Lists all reminders on that vybit]

Discover and Subscribe:

You: What public vybits are available about weather?
Claude: [Shows public vybits matching "weather"]

You: Subscribe me to the "Daily Weather Updates" vybit
Claude: [Subscribes and shows subscription details]

You: What am I subscribed to?
Claude: [Lists all your subscriptions]

You: Unsubscribe me from "Daily Weather Updates"
Claude: [Unsubscribes successfully]

Available Tools

The MCP server exposes 30 tools to AI assistants, providing full parity with the Vybit Developer API:

Vybit Management (6 tools)

• vybit_list - List owned vybits with search and pagination
• vybit_get - Get details about a specific owned vybit
• vybit_create - Create a new vybit
• vybit_update - Update an existing vybit (name, description, status, etc.)
• vybit_delete - Delete a vybit
• vybit_trigger - Trigger a notification with optional custom content

Reminder Management (4 tools)

• reminder_create - Create a scheduled reminder on a vybit (must have triggerType=reminders)
• reminder_list - List all reminders on a vybit
• reminder_update - Update an existing reminder (cron, timezone, message, etc.)
• reminder_delete - Delete a reminder

Sound Management (2 tools)

• sounds_list - List and search available notification sounds
• sound_get - Get details about a specific sound

Notification Logs (4 tools)

• logs_list - List all notification logs with search and pagination
• log_get - Get details about a specific log entry
• vybit_logs - List notification logs for a specific owned vybit
• subscription_logs - List notification logs for a specific subscription

Access Control / Peeps (5 tools)

• peeps_list - List all peeps (people you have shared vybits with)
• peep_get - Get details about a specific peep
• peep_create - Invite someone to a private vybit by email
• peep_delete - Remove a peep (revoke access to a vybit)
• vybit_peeps_list - List all peeps for a specific vybit

Monitoring & Utilities (2 tools)

• meter_get - Get API usage and limits (daily/monthly counts and caps)
• get_current_time - Get the current time (useful for relative time expressions when creating reminders)

Public Vybit Discovery (2 tools)

• vybits_browse_public - Browse and search public vybits available for subscription
• vybit_get_public - Get details about a public vybit by subscription key

Subscription Management (5 tools)

• subscription_create - Subscribe to a public vybit using its subscription key
• subscriptions_list - List all vybits you are subscribed to (following)
• subscription_get - Get details about a specific subscription
• subscription_update - Update subscription settings (enable/disable, permissions)
• subscription_delete - Unsubscribe from a vybit

Environment Variables

• VYBIT_API_KEY - Your Vybit Developer API key (one of VYBIT_API_KEY or VYBIT_ACCESS_TOKEN is required)
• VYBIT_ACCESS_TOKEN - OAuth2 access token (alternative to API key)
• VYBIT_API_URL (optional) - Custom API base URL (defaults to https://api.vybit.net/v1).

Development

Testing with MCP Inspector

# Install MCP Inspector
npm install -g @modelcontextprotocol/inspector

# Run the server with inspector
VYBIT_API_KEY=your-key npx @modelcontextprotocol/inspector node dist/index.js

Security Best Practices

1. Never commit API keys - Always use environment variables
2. Use separate keys - Create different Vybit accounts with respective API keys for development and production
3. Rotate regularly - Rotate your API keys periodically
4. Monitor usage - Use the meter_get tool to track API usage

Compatibility

This MCP server works with any MCP-compatible client:

• ✅ Claude Desktop
• ✅ Claude Code
• ✅ Cline (VS Code extension)
• ✅ Zed Editor
• ✅ Continue.dev
• ✅ Any other MCP-compatible AI tool

Support

• Documentation: developer.vybit.net
• Issues: GitLab Issues
• Email: [email protected]

Related Packages

• @vybit/api-sdk - Developer API SDK (used internally by this MCP server)
• @vybit/oauth2-sdk - OAuth 2.0 SDK for user-facing apps
• @vybit/core - Core utilities and types

License

MIT