
Vybit
net.vybitPublished by vybit.netOfficial publisherv1.10.0Updated Oct 24, 2026
Push notifications with personalized sounds - manage and trigger your vybits via MCP
Overview
Remote Vybit MCP server that lets an assistant create, manage and trigger personalized-sound push notifications from a Vybit account.
- What you can do
- Create, update, delete and list notification vybits, and trigger them with custom messages, images and links
- Browse and search public vybits, subscribe to them and manage subscriptions
- Search the sound library and view notification logs for vybits and subscriptions
- Invite people to private vybits and manage access permissions
- Create, update and delete scheduled reminders on vybits
- Check API usage, quota limits and profile information
- When to use it
- Useful when you want an assistant to send push alerts to your phone or team, for example build or server alerts, daily summaries, or reminders, and to manage the Vybit notification objects behind them from a conversation.
- Requirements
- Remote endpoint at api.vybit.net with OAuth authorization against a Vybit account; the README notes connecting from Claude or ChatGPT may require paid plans. A local npm variant exists that uses a VYBIT_API_KEY environment variable instead.
Installation
In SourceWeft
- Open Vybit in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/net.vybit%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"vybit": {
"type": "http",
"url": "https://api.vybit.net/v1/mcp"
}
}
}README
Vybit SDK
Official TypeScript/JavaScript SDKs for integrating with the Vybit notification platform.
Vybit is a push notification service with personalized sounds that can be recorded or chosen from a library of thousands of searchable sounds (via freesound.org).
[npm version] [npm version] [npm version] [npm version] [npm version] [License: MIT]
Overview
Vybit provides multiple integration options for different use cases:
All packages share common utilities from @vybit/core.
Developer API SDK
For backend services, automation, and server-to-server integrations
Installation
Getting Started
-
Get Your API Key
- Sign up at developer.vybit.net
- Navigate to the Developer API section
- Copy your API key
-
Initialize the Client
Common Operations
Create and Manage Vybits
Trigger Notifications
Manage Sounds
Discover and Subscribe to Public Vybits
Monitor Usage
API Reference
- 📖 Interactive Documentation: developer.vybit.net/api-reference
- 📋 OpenAPI Spec: docs/openapi/developer-api.yaml
OAuth2 SDK
For user-facing applications that need to access Vybit on behalf of users
The OAuth2 SDK handles the authorization flow only. Once you have an access token, use VybitAPIClient from @vybit/api-sdk for all API operations.
Installation
Getting Started
-
Register Your Application
- Sign up at developer.vybit.net
- Navigate to the OAuth Configuration section
- Enter your OAuth Client ID and Redirect URI
- Copy your Client ID and Client Secret
-
Initialize the OAuth2 Client
OAuth Flow
Step 1: Redirect User to Authorization
Step 2: Exchange Authorization Code for Token
Step 3: Use the Token with the API SDK
Token Management
API Reference
- 📖 Interactive Documentation: developer.vybit.net/oauth-reference
- 📋 OpenAPI Spec: docs/openapi/oauth2.yaml
CLI
For command-line access, shell scripting, CI/CD pipelines, and AI agent tooling
The Vybit CLI provides full parity with the MCP server — every operation available to AI assistants is also available from the command line. All output is structured JSON to stdout, making it equally useful for humans, shell scripts, and AI agents.
Installation
Authentication
Credentials are resolved in order: CLI flags > environment variables > config file (~/.config/vybit/config.json).
Common Operations
Available Commands
Agent-Friendly Design
- JSON to stdout — all data output is parseable JSON
- Errors to stderr — structured
{"error":"...","statusCode":404}format - Exit codes — 0 success, 1 error, 2 auth error
--quiet/-q— output only keys/IDs for chaining commands- Never prompts — all input via flags, safe for non-interactive use
MCP Server
For AI assistants like Claude to interact with your Vybit notifications
The Model Context Protocol (MCP) server enables AI assistants to manage your Vybit notifications through natural conversation. It provides full parity with the Developer API, giving AI assistants access to all Vybit features.
Installation
Hosted Remote MCP Server (Easiest)
Vybit provides a hosted remote MCP server at https://api.vybit.net/v1/mcp — no installation required. Connect directly from Claude or ChatGPT (may require paid plans):
Claude Desktop / Claude Web (claude.ai):
- Open Settings → Connectors
- Click Add Custom Connector
- Enter the MCP URL:
https://api.vybit.net/v1/mcp - You'll be redirected to authorize with your Vybit account via OAuth
ChatGPT Desktop / ChatGPT Web (chatgpt.com):
- Open Settings → Apps → Advanced Settings
- Toggle ON Developer Mode, Click "Create app"
- Fill out and submit the New App form setting the MCP Server URL as
https://api.vybit.net/v1/mcp - You'll be redirected to authorize with your Vybit account via OAuth
Local MCP Server
If you prefer to run the MCP server locally (e.g., for Claude Code, Cline, or other MCP clients), install the npm package and configure with your API key:
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json):
Claude Code (.claude/mcp.json in your project):
nvm users: Claude Desktop doesn't source your shell profile, so
node/npxmay resolve to the wrong version. Usewhich nodeandnpm root -gto find your paths, then usenodedirectly instead ofnpx. See the MCP Server README for details.
What You Can Do
Once configured, you can ask your AI assistant to:
- Manage Vybits: Create, update, delete, and list your notification vybits
- Send Notifications: Trigger notifications with custom messages and content
- Discover Public Vybits: Browse and search public vybits created by others
- Manage Subscriptions: Subscribe to public vybits and manage your subscriptions
- Browse Sounds: Search available notification sounds
- View Logs: See notification history for your vybits and subscriptions
- Manage Access: Invite people to private vybits and control permissions
- Manage Reminders: Create, update, and delete scheduled reminders on vybits
- Monitor Usage: Check your API usage and quota limits
Example Conversations
Features
The MCP server provides 31 tools across all Vybit API features:
- Vybit management (6 tools)
- Reminder management (4 tools)
- Public vybit discovery (2 tools)
- Subscription management (5 tools)
- Sound browsing (2 tools)
- Notification logs (4 tools)
- Access control / peeps (5 tools)
- Usage monitoring (1 tool)
Compatibility
Works with any MCP-compatible client:
- ✅ Claude Desktop
- ✅ Claude Code
- ✅ Cline (VS Code extension)
- ✅ Zed Editor
- ✅ Continue.dev
- ✅ Any other MCP-compatible AI tool
Documentation
See the MCP Server README for complete documentation.
n8n Community Nodes
For workflow automation and no-code/low-code integrations
Installation
Self-Hosted n8n:
Then restart your n8n instance.
n8n Cloud: Once verified, search for "Vybit" in the n8n nodes panel to install. Verification is currently under review.
Getting Started
The Vybit n8n node supports both authentication methods:
Option 1: API Key (Recommended for Personal Automation)
- Get your API key from developer.vybit.net
- In n8n, add a Vybit node
- Select "API Key" authentication
- Create a new credential and paste your API key
Option 2: OAuth2 (For Multi-User Services)
- Configure OAuth2 at developer.vybit.net
- In n8n, select "Vybit OAuth2 API" authentication
- Connect and authorize your Vybit account
Available Operations
The n8n node provides access to 34 operations across 7 resources:
Profile (3 operations)
- Get Profile, Get Usage Metrics, Check API Status
Vybits (6 operations)
- List, Get, Create, Update, Delete, Trigger
Logs (4 operations)
- List All, Get, List by Vybit, List by Subscription
Sounds (3 operations)
- Search, Get, Play
Peeps (5 operations)
- List All, List by Vybit, Invite, Get, Delete
Subscriptions (9 operations)
- List Public, Get Public, Subscribe, List My Subscriptions, Get Subscription, Update Subscription, Unsubscribe, Send to Owner, Send to Group
Reminders (4 operations)
- List, Create, Update, Delete
Example Workflows
Alert on Server Error:
Daily Report:
Automated Vybit Creation:
Documentation
- 📖 Node Documentation: packages/n8n-nodes/README.md
- 🚀 Deployment Guide: packages/n8n-nodes/DEPLOYMENT.md
- 📋 Integration Guide: docs/n8n-integration-guide.md
- 💡 Example Workflows: examples/n8n/
Environment Management
Both SDKs connect to Vybit production endpoints:
- OAuth Authorization:
https://app.vybit.net - API Endpoints:
https://api.vybit.net/v1
Managing Multiple Environments
For development, staging, and production environments, create separate Vybit developer accounts:
Developer API Approach:
- Each environment gets its own API key
- Configure different keys per environment in your app
OAuth2 Approach:
- Each environment gets its own OAuth client credentials
- Configure different redirect URIs per environment
Error Handling
Both SDKs use consistent error classes from @vybit/core:
Examples
The examples/ directory contains complete working examples:
Developer API Examples
- developer-api-notifications.js - Creating and triggering vybits
- simple-notifications.js - Sending notifications with various options
OAuth2 Examples
- oauth2-simple.js - Basic OAuth 2.0 flow
- oauth2-complete-flow.js - Complete OAuth implementation with error handling
- oauth2-express-server.js - Full Express.js integration with session management
n8n Workflow Examples
- n8n/server-monitoring.json - Monitor server health and alert on errors
- n8n/daily-summary.json - Send daily summary notifications
- n8n/airtable-integration.json - Create vybits from Airtable records
- n8n/webhook-to-notification.json - Convert webhook events to notifications
TypeScript Support
All packages are written in TypeScript and include full type definitions:
Contributing
Interested in contributing? Check out our Contributing Guide for:
- Development setup and testing
- Code style guidelines
- Pull request process
- How to report issues
Support
- Documentation: developer.vybit.net
- Issues: GitHub Issues
- Email: [email protected]
License
MIT
Source: README.md at commit 0fca93e
Tools
0Version history
5- v1.10.0LatestOct 12, 2026
- v1.9.0Oct 9, 2026
- v1.8.0Sep 27, 2026
- v1.7.0Sep 21, 2026
- v1.5.1Sep 16, 2026
Score
75% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.