Push notifications with personalized sounds - manage and trigger your vybits via MCP
net.vybit/mcp-server (MCP)
This MCP server provides integration for a push notification platform that supports personalized sounds. It lets developers manage and trigger “vybits” via MCP, aligning with the Vybit TypeScript/JavaScript SDKs. Vybit notifications use either recorded sounds or sounds selected from a searchable library.
🛠️ Key Features
Push notifications
Personalized sounds (recorded or chosen from a sound library)
Sound search via freesound.org (as part of the platform)
🚀 Use Cases
Sending notifications with custom audio
Managing and triggering vybits through an MCP workflow
⚡ Developer Benefits
Fits with the official TypeScript/JavaScript SDK approach
Integrates with @vybit/api-sdk and @vybit/oauth2-sdk (SDKs for the Vybit platform)
⚠️ Limitations
Server metadata provided here does not include specific tool names, capabilities, or tool counts beyond managing/triggering vybits
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).
import { VybitAPIClient } from'@vybit/api-sdk';
// With API keyconst client = newVybitAPIClient({
apiKey: 'your-api-key-from-developer-portal'
});
// Or with an OAuth2 access tokenconst client = newVybitAPIClient({
accessToken: 'your-oauth2-access-token'
});
Common Operations
Create and Manage Vybits
typescript
// Create a vybit (only name is required)const vybit = await client.createVybit({
name: 'Server Alert'
});
// List vybits with search and paginationconst vybits = await client.listVybits({
search: 'alert',
limit: 10,
offset: 0
});
// Get a specific vybitconst details = await client.getVybit('vybit-id');
// Update a vybitawait client.updateVybit('vybit-id', {
name: 'Updated Server Alert',
status: 'on'
});
// Delete a vybitawait client.deleteVybit('vybit-id');
Trigger Notifications
typescript
// Simple triggerawait client.triggerVybit('vybit-key');
// Trigger with custom contentawait client.triggerVybit('vybit-key', {
message: 'Server CPU usage at 95%',
imageUrl: 'https://example.com/graph.png', // Must be a direct link to a JPG, PNG, or GIF imagelinkUrl: 'https://dashboard.example.com',
log: 'CPU spike detected on web-server-01'
});
A trigger that is received but not sent (the account's monthly or daily limit is reached, or the
vybit is off) does not throw. It resolves with result: 0 and a reason:
typescript
const result = await client.triggerVybit('vybit123abc');
if (result.result === 0) {
console.log(result.reason); // 'monthly_limit', 'daily_limit', or 'vybit_off'
}
sendToOwner and sendToGroup answer the same way.
Manage Sounds
typescript
// List available soundsconst sounds = await client.listSounds({
search: 'alert',
limit: 20
});
// Get sound detailsconst sound = await client.getSound('sound-key');
Discover and Subscribe to Public Vybits
typescript
// Browse public vybits (returns PublicVybit[])const publicVybits = await client.listPublicVybits({
search: 'weather',
limit: 10
});
// Get details about a public vybit before subscribingconst vybitDetails = await client.getPublicVybit('subscription-key-abc123');
// Subscribe to a public vybit using its subscription keyconst follow = await client.createVybitFollow({
subscriptionKey: vybitDetails.key
});
// List your subscriptionsconst subscriptions = await client.listVybitFollows();
// Unsubscribe from a vybitawait client.deleteVybitFollow(follow.followingKey);
Monitor Usage
typescript
// Get current usage and limitsconst meter = await client.getMeter();
console.log(`Daily: ${meter.count_daily} / ${meter.cap_daily}`);
console.log(`Monthly: ${meter.count_monthly} / ${meter.cap_monthly}`);
console.log(`Plan: ${meter.tier}`);
const authUrl = oauthClient.getAuthorizationUrl({
state: 'random-state-string'
});
// Redirect user to authUrl// They will authorize your app and be redirected back to your redirectUri
Step 2: Exchange Authorization Code for Token
typescript
// After redirect, extract the code from query paramsconst code = urlParams.get('code');
// Exchange code for access tokenconst token = await oauthClient.exchangeCodeForToken(code);
// Store token.access_token securely for future requests
Step 3: Use the Token with the API SDK
typescript
import { VybitAPIClient } from'@vybit/api-sdk';
// Create an API client with the OAuth2 access tokenconst apiClient = newVybitAPIClient({
accessToken: token.access_token
});
// Now use the full Developer API on behalf of the userconst vybits = await apiClient.listVybits();
await apiClient.triggerVybit('vybit-key', {
message: 'Hello from your app!'
});
Token Management
typescript
// Verify a token is still validconst isValid = await oauthClient.verifyToken(token.access_token);
// Store and retrieve tokens
oauthClient.setAccessToken('existing-token');
const currentToken = oauthClient.getAccessToken();
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
bash
npm install -g @vybit/cli
Authentication
bash
# Option 1: Environment variable (recommended for CI/CD and agents)export VYBIT_API_KEY='your-api-key'# Option 2: Config file
vybit auth setup --api-key 'your-api-key'# Option 3: Per-command flag
vybit --api-key 'your-api-key' vybits list
Credentials are resolved in order: CLI flags > environment variables > config file (~/.config/vybit/config.json).
Common Operations
bash
# List your vybits
vybit vybits list
# Create a vybit
vybit vybits create --name "Deploy Alert" --trigger-type webhook
# Trigger a notification
vybit trigger <vybit-key> --message "Build passed"# Trigger in CI/CD (quiet mode returns just the key/ID)
vybit trigger <vybit-key> --message "$(git log -1 --oneline)" -q
# Search sounds
vybit sounds list --search "bell"# Check usage
vybit meter
Available Commands
Command
Operations
vybit vybits
list, get, create, update, delete
vybit trigger
Trigger a vybit notification
vybit reminders
list, create, update, delete
vybit sounds
list, get
vybit subscriptions
list, get, create, update, delete
vybit browse
list, get (public vybits)
vybit logs
list, get, vybit, subscription
vybit peeps
list, get, create, delete, vybit
vybit meter
API usage metrics
vybit status
API health check
vybit profile
User profile info
vybit auth
setup, status, logout
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
bash
npm install -g @vybit/mcp-server
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):
nvm users: Claude Desktop doesn't source your shell profile, so node/npx may resolve to the wrong version. Use which node and npm root -g to find your paths, then use node directly instead of npx. 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
code
You: Create a vybit called "Server Alert" for webhooks with an alarm sound
Claude: [Creates the vybit and shows details including trigger URL]
You: Trigger my Server Alert vybit with message "CPU at 95%"
Claude: [Sends the notification]
You: What public vybits are available about weather?
Claude: [Shows matching public vybits]
You: Subscribe me to the "Daily Weather" vybit
Claude: [Subscribes and confirms]
You: Show me recent notifications for my Server Alert
Claude: [Lists notification logs]
Features
The MCP server provides 31 tools across all Vybit API features: