Claude Vybit Notifications connectorWhat Claude can do in your Vybit Notifications account.
The Claude Vybit Notifications connector exposes 30 tools. 18 read your vybits, sounds, logs and usage, and 12 create, change, send or delete. Here: what Claude can fire off, what it asks first, and what it cannot reach.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can reach your Vybit account
Vybit is a notification service where every alert has its own sound, and each channel is called a vybit. With the connector, you stop opening the dashboard to set up channels, share them or check what went out. You describe it to Claude, and it sets up the channel, fires the alert or reads back the history for you.
An alert channel in one sentence. Ask for a "Server Alert" with an alarm sound: sounds_list finds a fitting sound, vybit_create sets up the channel, and vybit_trigger fires a test with your message.
Reminders that ring on schedule. On a vybit set to reminders, reminder_create adds a stand-up reminder for every weekday at nine in your timezone, and reminder_update moves it when the meeting does.
Who hears what, under control. peep_create invites someone to a private channel by email, vybit_peeps_list shows who is on it, and peep_delete revokes access when a job ends.
Now what it does not do. The directory lists this connector as a desktop extension, for Claude Desktop only. Vybit's own package describes 33 tools, three more than the sheet, so the extra ones are not something to count on here. And nothing runs on its own inside Claude: a reminder rings on Vybit's schedule, but no tool wakes Claude up. For alerts sent from other apps on an event, see the Vybit Notifications Make integration.
The vocabulary in one minute
Five words you will meet while plugging Vybit in.
- Connector
- The link you set up once between Claude and an account you already have, so it can work in that account while it answers you.
- Tool
- One named action a connector opens to Claude. Claude picks the ones it needs by itself; the directory sheet lists them by name.
- Vybit
- Vybit's name for one notification channel: an endpoint with its own sound that you trigger, share with people or let others subscribe to.
- Approval
- The confirmation Claude waits for before it goes through with something that changes your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Vybit.
Plug Vybit Notifications into Claude in three steps
- 01
Find Vybit Notifications in Claude
In Claude Desktop's settings, open Customize, then Connectors, and look for Vybit Notifications. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch it on first, then each member connects on their own.
- 02
Start the connection
Click Connect on its row. According to Vybit, Claude Desktop then asks for your Vybit API key during setup. If the link breaks later, use Disconnect and plug it back in.
- 03
Check what you hand over
Read what the service asks for before you accept. It is Vybit, not Claude, that sets what the access covers, and that access can be withdrawn later from your Vybit account as well.
The 30 Claude Vybit Notifications connector tools, grouped by what they do
Vybit Notifications gives Claude 30 tools: 18 that read your account, 12 that change something in it.
Two groups: what Claude reads, and what it creates, changes, sends or removes. The names stay exactly as Claude shows them.
- 18 read
- 12 write
What Claude reads (18)
18 toolsTools that look at your vybits, sounds, subscriptions, logs, peeps and usage without touching them.
vybit_list
Lists the vybits you own, Vybit's notification channels, each tied to its own sound, with search and paging for accounts that hold many of them.
vybit_get
Reads the full setup of one vybit you own, so Claude can tell you how that channel is set up before you touch it.
sounds_list
Lists and searches the notification sounds Vybit offers, the heart of the service, so Claude can suggest one that fits the alert.
sound_get
Gets the details of one specific sound, which helps before assigning it to a channel people will hear every day, sometimes at night.
meter_get
Returns your API usage against its limits, with daily and monthly counts and caps, so you see how much headroom is left.
get_current_time
Gives Claude the current time, which Vybit describes as useful for relative expressions like "in two hours" when setting reminders.
vybits_browse_public
Browses and searches the public vybits other people have opened to subscription, a catalogue of ready-made channels you can follow without building anything.
vybit_get_public
Reads the details of a public vybit from its subscription key, so you know what you would be signing up for.
subscriptions_list
Lists every vybit you are subscribed to, the channels you follow rather than own, which is the quickest way to find where a stray alert comes from.
subscription_get
Shows one subscription with its settings, whether it is on or off and what it allows, before you decide to keep, mute or drop it.
logs_list
Lists all your notification logs, with search and paging: the record of what fired, on which channel and when, across everything you own and follow.
log_get
Opens a single log entry in detail, useful when one particular notification is in question and the overall history is too broad to settle it.
vybit_logs
Pulls the notification logs of a single vybit you own, so the history of one channel comes out on its own instead of mixed with the rest.
subscription_logs
Retrieves the alerts a channel you follow has sent you, the log of one subscription on its own, handy when you only care about one source.
peeps_list
Returns every peep on your account, Vybit's word for the people you have shared vybits with, across all your channels at once.
peep_get
Looks at one peep in detail, that is one person's access to your channels, so you can check exactly what they can hear.
vybit_peeps_list
Shows every peep of one specific vybit, the people who can hear that channel, which is the channel-by-channel view of everything you share.
reminder_list
Gives the full list of reminders set on one vybit, with their schedules, so you can see what will ring and when before touching anything.
What Claude changes or sends (12)
12 toolsTools that set things up, edit, fire notifications, invite people or delete. No source gives any of them its own confirmation rule: the general rule below applies.
vybit_create
Approval: see the ruleCreates a new vybit, the channel that will carry your notifications with the sound you pick, straight from a sentence in the chat.
vybit_update
Approval: see the ruleChanges an existing vybit: its name, description, status, who may send to it and other settings Vybit lists.
vybit_delete
Approval: see the ruleDeletes one of your vybits. Vybit's description stops there and mentions no way to bring it back.
vybit_trigger
Approval: see the ruleTriggers a notification on a vybit, with optional custom content such as a message, and it goes out as a push notification with the sound of that vybit.
subscription_create
Approval: see the ruleSubscribes you to a public vybit using its subscription key, so its notifications start reaching you.
subscription_update
Approval: see the ruleUpdates the settings of a subscription, such as switching it on or off or changing its permissions, without leaving the channel.
subscription_delete
Approval: see the ruleUnsubscribes you from a vybit, which stops its notifications from reaching you.
peep_create
Approval: see the ruleInvites a person to one of your private vybits by email, which sends them an invitation.
peep_delete
Approval: see the ruleRemoves a peep, which revokes that person's access to the vybit.
reminder_create
Approval: see the ruleCreates a scheduled reminder on a vybit, with its own timing, timezone and message, so the channel rings on a schedule.
reminder_update
Approval: see the ruleUpdates an existing reminder: its schedule, timezone, message and other settings.
reminder_delete
Approval: see the ruleDeletes a reminder from a vybit, so it stops ringing on its schedule.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it carries out on an account for you. The request shows up in the conversation, at the moment it matters.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organisation, keeping the lookups open and closing everything that sends or deletes, for example. That setting applies to everyone and nobody overrides it from their own account. And Claude works with the key you gave it and nothing more: another person's private vybit stays out of reach unless they invited you.
Which plans it is available on
None of the 819 directory sheets shows availability by plan. The answer, connector by connector, is not published anywhere: it is a real gap in the catalogue.
The general rule is published, though. Remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions like this one install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner opens a connector for the organisation before members can connect individually. For the current state, check the Vybit Notifications sheet in the official directory. This connector is documented only by Vybit itself.
Where the Claude Vybit Notifications connector stops
A connector is not an automation. Claude calls these tools while it answers you: Vybit may ring on its own schedule, but nothing makes Claude act when an alert fires or a log appears.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The directory's partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as announced. Plug in only what comes from a publisher you trust. Here, the installed extension works with your API key, so anyone holding that key holds the same access. Other connectors are gathered on the Integrations hub.
Need help connecting Vybit Notifications to Claude?
A person reads every message.
