Ably
for LuumenAI
Read channel, presence, and push state in Ably, then publish with approval
Connect Ably with an API key and Luumen can answer questions about your real-time layer directly in the terminal: which channels are active, who is present, what a channel's recent message history looks like, and which devices are registered for push. When you need to act, Luumen previews the publish or registration change and asks before sending it.
The Ably toolbox
25 tools: 14 read, 11 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadQuery Batch PresenceThis tool enables querying the presence states of multiple channels in a single API request.
- ReadQuery Batch Presence HistoryThis tool enables querying presence history for multiple channels in a single API request.
- ReadGet Channel DetailsThis tool retrieves metadata and details for a specific channel in Ably.
- ReadGet Channel HistoryThis tool retrieves the message history for a specified Ably channel.
- ReadGet Channel PresenceObtain the set of members currently present for a channel.
- ReadGet Message VersionsRetrieve all historical versions of a specific message from an Ably channel.
- ReadGet Channel Presence HistoryThis tool retrieves the history of presence messages for a specified channel in Ably.
- ReadGet Push Device RegistrationGet the full details of a device registration for push notifications.
- ReadGet Ably Service TimeThis tool retrieves the current server time from Ably's service in milliseconds since the epoch.
- ReadGet Application StatsThis tool retrieves your application's usage statistics from Ably.
- ReadList ChannelsEnumerate all active channels in the Ably application.
- ReadList Push ChannelsList all channels with at least one subscribed device.
- ReadList Push Channel SubscriptionsThis tool retrieves a list of all push notification channel subscriptions.
- ReadList Registered Push DevicesList all devices registered for receiving push notifications in your Ably application.
- WriteDelete Channel SubscriptionThis tool allows you to unsubscribe devices or clients from push notifications for specific channels. Approval by default
- WritePatch Push Device RegistrationPartially update specific attributes of an existing device registration in Ably's push notification system. Approval by default
- WriteBatch Publish MessagesBatch publish messages to multiple channels in parallel. Approval by default
- WritePublish Message to ChannelAllow users to publish a message to a specified Ably channel using a POST request. Approval by default
- WritePublish Push NotificationPublish a push notification directly to device(s) via Ably's Push Notifications API. Approval by default
- WriteBatch Publish Push NotificationsBatch publish push notifications directly to specific recipients. Approval by default
- WriteRegister Push DeviceRegister a device for receiving push notifications in Ably. Approval by default
- WriteRequest Access TokenRequest an access token for Ably authentication. Approval by default
- WriteUnregister All Push DevicesUnregister matching devices for push notifications. Approval by default
- WriteUnregister Push DeviceUnregister a single device from push notifications in Ably. Approval by default
- WriteUpdate Push Device RegistrationUpdate (upsert) a device registration for push notifications in Ably. Approval by default
One prompt, start to finish
What a governed Ably run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — delete channel subscription, patch push device registration, batch publish messages, publish message to channel, and more — is shown as a plan and requires approval by default, including the 3 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Ably — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Ably to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.