Ably MCP integration for AI agents.
Connect AI agents to Ably through 11 structured actions, including get channel details, create channel, delete channel subscription, and batch presence. Revi…
- ACTION CONTRACTS
- 11
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Ably integration exposes
The Ably Agent App exposes 11 provider-backed actions for developer tools work. Its current contract lets an authorized agent retrieve ably metadata and occupancy details for one channel, activate an ably channel by retrieving its metadata, and delete an ably push notification subscription for a channel, device, or client. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Ably account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Ably capabilities.
Showing 11 of 11 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_channel_detailsREADRetrieve Ably metadata and occupancy details for one channel.
INPUTS: channel_id
create_channelWRITEActivate an Ably channel by retrieving its metadata.
INPUTS: channel_id
delete_channel_subscriptionHIGH IMPACTDelete an Ably push notification subscription for a channel, device, or client.
INPUTS: channel / client_id / device_id
batch_presenceREVIEWQuery current presence for multiple Ably channels.
INPUTS: channels / separator
batch_presence_historyREVIEWQuery presence history for multiple Ably channels.
INPUTS: channels / separator / start / end / limit
get_channel_historyREADRetrieve message history for one Ably channel.
INPUTS: channel_id / start / end / limit / direction
get_presence_historyREADRetrieve presence history for one Ably channel.
INPUTS: channel_id / start / end / limit / direction
get_service_timeREADRetrieve Ably service time in milliseconds since the Unix epoch.
get_statsREADRetrieve Ably application usage statistics.
INPUTS: start / end / limit / direction / unit
list_push_channel_subscriptionsREADList Ably push notification channel subscriptions.
INPUTS: channel / client_id / device_id / concat_filters / limit
publish_message_to_channelHIGH IMPACTPublish one message to an Ably channel.
INPUTS: channel_id / data / name / id / encoding
INPUT CONTRACTS
Know what the action needs before it runs.
get_channel_details
channel_idREQUIRED- The Ably channel ID or channel name.
create_channel
channel_idREQUIRED- The Ably channel ID or channel name.
delete_channel_subscription
channelOPTIONAL- The Ably channel ID or channel name.
client_idOPTIONAL- The Ably client ID to unsubscribe.
device_idOPTIONAL- The Ably device ID to unsubscribe.
batch_presence
channelsREQUIRED- One or more Ably channel names.
separatorOPTIONAL- The separator used when channels is provided as a string.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Channel Details
Retrieve Ably metadata and occupancy details for one channel. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_channel_detailsControl Create Channel
Activate an Ably channel by retrieving its metadata. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_channelVerify with Get Channel History
Retrieve message history for one Ably channel. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_channel_historySAFETY BOUNDARY
Operate Ably with explicit limits
- Authorize Ably with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_channel_subscription` and `publish_message_to_channel` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Ably rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Ably task completed successfully.
CONNECTION MODEL
API key
Ably API key used with HTTP Basic authentication. Create or view app API keys in the Ably dashboard under App settings > API keys: https://ably.com/dashboard.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 2
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Ably.