Integration

Vybit integration

Vybit sends personalized sound notifications to phones: each vybit is a notification channel with its own sound, and triggering it plays that sound on every subscriber's device. Create, update and delete vybits, trigger them with a custom message, image or link, schedule one-off reminders, search sounds, manage subscriptions and subscribers (peeps), invite people by email, and read notification logs and usage limits. The health-check route and the raw audio download are not exposed. Authentication is a Developer API key from developer.vybit.net sent in the X-API-Key header.

Connect Vybit How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Vybit.Built from the 32 Vybit tools below, on the connection you add once.

What you can do with Vybit

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Subscription, 6 operations

create_subscriptionCreate subscriptionPOSTFollow a vybit by its subscription key (from list_public_vybits, a QR code or a share link). Returns the new followingKey; message says subscribed, invitation or already subscribed.
delete_subscriptionDelete subscriptionDELETEUnfollow a vybit, by the followingKey from list_subscriptions. Cannot be undone; to follow it again, call create_subscription with the vybit's subscription key.
get_public_vybitGet public vybitGETGet a public or shared vybit by its subscription key (from list_public_vybits, a QR code or a share link) before following it: name, description, sound, owner and whether you already follow it.
get_subscriptionGet subscriptionGETRetrieve details for a specific subscription you're following. Only the subscriber can read a subscription; any other key returns 404.
list_subscriptionsList subscriptionsGETRetrieve a paginated list of vybits the authenticated user is subscribed to.
update_subscriptionUpdate subscriptionPATCHChange a subscription you follow: turn it on or off, accept or decline an invitation, or (only when the vybit lets subscribers send) set its message, image and link. Send only the fields to change.

Vybit, 6 operations

create_vybitCreate vybitPOSTCreate a vybit (a notification channel with its own sound). Only name is required; pick soundKey from search_sounds. Returns the vybit with its key, triggerKey and subscriptionKey.
delete_vybitDelete vybitDELETEPermanently delete a vybit you own, with its subscriptions and QR codes; existing logs are kept. Cannot be undone.
get_vybitGet vybitGETRetrieve details for a specific vybit owned by the authenticated user.
list_public_vybitsList public vybitsGETDiscover public vybits created by other users that anyone can follow. Each key is a subscription key for create_subscription. Page with offset and limit (max 100), filter with search.
list_vybitsList vybitsGETList the vybits you own, with their key, sound, trigger type and settings, access and follower count. Page with offset and limit (max 100); search matches name and description.
update_vybitUpdate vybitPATCHUpdate a vybit you own: send only the fields to change, the others stay as they are. Other fields (personKey, triggerKey, subscriptionKey...) are refused with a 403.

Peep, 5 operations

create_peepCreate peepPOSTInvite a person by email to follow one of your vybits (key = the vybit key). A Vybit user gets an in-app invitation notification, anyone else gets an invitation email.
delete_peepDelete peepDELETERemove a subscriber (peep) from one of your vybits, by the peep key from list_peeps or list_vybit_peeps. The person stops receiving that vybit's notifications.
get_peepGet peepGETGet one subscriber (peep) of your vybits by the peep key from list_peeps or list_vybit_peeps: name, vybit key and access status (invited, granted, public, denied...).
list_peepsList peepsGETRetrieve all peeps (subscribers) across all vybits owned by the authenticated user.
list_vybit_peepsList vybit peepsGETList the subscribers (peeps) of one vybit you own, whether they joined through public discovery, an unlisted link or an invitation. Page with offset and limit (max 100).

Log, 4 operations

get_logGet logGETGet one notification log entry by its key (from list_logs, or the plk returned by trigger_vybit): the vybit, sender, time, message, image, link and log text of that notification.
list_logsList logsGETList notification logs of the account, covering both your own vybits and the vybits you follow. Page with offset and limit (max 100), filter with search on vybit name and diagnostic fields.
list_subscription_logsList subscription logsGETList notification logs of one vybit you follow, by its followingKey (from list_subscriptions). Page with offset and limit (max 100); search matches vybit name or diagnostic fields.
list_vybit_logsList vybit logsGETList the notification logs triggered for one vybit you own, by its key (from list_vybits). Page with offset and limit (max 100); search matches vybit name or diagnostic fields.

Reminder, 4 operations

create_reminderCreate reminderPOSTSchedule a one-off reminder on a vybit whose triggerType is reminders: it fires once at the cron date, sends its notification, then deletes itself. A recurring cron is refused with a 400.
delete_reminderDelete reminderDELETEDelete a reminder from a vybit. Removes the reminder from the vybit's triggerSettings and deletes the associated scheduled job. This action cannot be undone.
list_remindersList remindersGETList all reminders on a vybit. Returns the array of reminders from the vybit's triggerSettings, or an empty array if none exist.
update_reminderUpdate reminderPATCHUpdate a reminder: send only the fields to change. Changing cron or timeZone reschedules it.

Notification, 3 operations

send_to_groupSend to groupPOSTAs a subscriber, send a notification to every subscriber of a vybit whose sendPermissions is subs_group. The subscription must be on, with accessStatus granted or public. Counts against your tier limits.
send_to_ownerSend to ownerPOSTAs a subscriber, send a notification to the owner of a vybit whose sendPermissions is subs_owner. The subscription must be on, with accessStatus granted or public. Counts against your tier limits.
trigger_vybitTrigger vybitPOSTSend a vybit's notification now to all its subscribers, as its owner, optionally overriding message, image, link and log. Returns plk (the log key for get_log); a vybit that is off returns result 0 and warn, nothing sent.

Sound, 2 operations

get_soundGet soundGETRetrieve details for a specific sound by its unique key.
search_soundsSearch soundsGETSearch sounds to use as a vybit's soundKey; without search it returns your own sounds. A sound serves one vybit at a time: vybitKey is null when the sound is free, else the key of the vybit using it.

Profile, 1 operation

get_profileGet profileGETRetrieve the authenticated user's profile information. Returns read-only profile data including account name, email, unique key, and subscription tier.

Usage, 1 operation

get_meterGet meterGETGet the account's usage and tier limits: notifications sent today and this month, number of vybits, the tier's daily, monthly and vybit caps, and when the monthly count resets.

Use Vybit from Claude Code, Cursor or Codex

Connect Vybit in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Vybit operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Vybit

Create your workspace
Sign up free. Nothing to install.
Connect Vybit once
Add your Vybit connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.