Get started free
All integrations

Ably integration

Realtime messaging and data synchronization platform. Build live chat, multiplayer games, IoT dashboards, and collaborative applications. Features include pub/sub messaging, presence detection, message history, push notifications, and WebSocket connections. Supports millions of concurrent connections with guaranteed message delivery and low latency.

32 toolsBasic authAPI docs

Common Ably use cases

  • push administration
  • edit history
  • token refresh
  • device management
  • subscription management
  • metadata update
  • capacity planning
  • channel discovery
  • content moderation
  • device cleanup

What you can do with Ably

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.

Push device, 8 operations

  • DELETEdelete_push_device

    Unregisters a single device from push notifications by device ID. Returns empty response on success.

  • DELETEdelete_push_devices

    Unregisters multiple devices matching the filter. Use deviceId or clientId (not both) to specify which devices to remove.

  • GETget_push_device

    Retrieves details of a registered push device. Returns device id, platform, form factor, metadata, push state, and recipient information.

  • GETlist_push_devices

    Lists registered push devices with optional filtering by deviceId or clientId. Returns paginated array of device registration objects.

  • PATCHpatch_push_device

    Partially updates a push device registration. Only sends changed fields. Returns the complete updated device object.

  • POSTregister_push_device

    Registers a device for push notifications. Provide platform, form factor, and push recipient details. Returns device registration with updateToken.

  • POSTreset_push_device_token

    Resets the update token for a push device registration. Invalidates the old token and returns updated device details with a new token.

  • PUTupdate_push_device

    Updates an existing push device registration. Mutable fields include clientId, metadata, and push.recipient. Returns updated device details.

Message, 6 operations

  • POSTbatch_publish

    Publishes messages to multiple channels in a single HTTP request. Supports up to 100 channels and 1000 messages per batch specification. Maximum request body is 2MiB.

  • GETget_channel_messages

    Retrieves message history from an Ably channel. Filter by time range, limit results, and specify order. Returns messages with timestamps, IDs, and full payload. Requires history to be enabled on the channel.

  • GETget_message_version

    Retrieves the latest version of a specific message by its serial. Returns the current state after any updates, deletes, or appends.

  • GETget_message_versions

    Retrieves all historical versions of a message. Returns the original and all updates or deletes ordered by version serial (oldest to newest).

  • POSTpublish_message

    Publishes a message to an Ably channel for real-time delivery to all subscribers. Include event name and data payload. Messages are persisted for history if enabled. Returns message ID and timestamp on success.

  • PATCHupdate_message

    Updates, deletes, or appends to an existing message. Specify action type (1=update, 2=delete, 5=append) and new content. Returns the version serial of the operation.

Annotation, 3 operations

  • GETget_annotation_client_summary

    Retrieves the annotation summary for a message filtered to a specific client ID. Returns aggregated annotation types relevant to that client with clipped=true indicating filtered results.

  • GETget_annotations

    Retrieves all annotations on a specific message. Returns paginated list of reactions, votes, and other annotations ordered from earliest to latest.

  • POSTpublish_annotations

    Publishes annotations (reactions, votes, etc.) on a specific message. Supports create and delete actions with various aggregation types.

Presence, 3 operations

  • GETbatch_presence

    Retrieves presence data for multiple channels in a single request. Returns an array of objects each containing the channel name and its presence members.

  • GETget_channel_presence

    Gets the current presence set showing all clients on a channel. Returns client IDs, connection IDs, and optional presence data. Use to show who's online in chat rooms, active players in games, or live viewers.

  • GETget_presence_history

    Retrieves presence history showing enter, leave, and update events over time. Filter by time range. Returns timeline of who was present and when they joined/left.

Push subscription, 3 operations

  • GETlist_push_subscriptions

    Lists push channel subscriptions with filtering by channel, clientId, or deviceId. Returns paginated array of subscription objects.

  • POSTsubscribe_push_channel

    Subscribes a device or client to push notifications on a channel. Either deviceId or clientId must be provided.

  • DELETEunsubscribe_push_channel

    Removes push channel subscriptions. Unsubscribe by channel, deviceId, or clientId. Omitting channel removes all subscriptions for the target.

Channel, 2 operations

  • GETget_channel_status

    Gets channel status including whether it's active, presence occupancy count, and connection metrics. Useful for monitoring and capacity planning.

  • GETlist_channels

    Lists all active channels in your Ably application. Filter by prefix to find specific channel types. Returns channel names with pagination support.

Push, 2 operations

  • POSTbatch_push_publish

    Publishes push notifications to multiple recipients in a single request. Each spec can target different recipients with different payloads. Maximum 10,000 notifications per request.

  • POSTpush_publish

    Publishes a push notification directly to a specific device or client. Supports generic notifications and platform-specific overrides for APNs, FCM, and web push.

Token, 2 operations

  • POSTrequest_token

    Requests a new authentication token for Ably clients. Specify TTL, capabilities (channel permissions), and optional client ID. Returns token for secure client-side authentication.

  • POSTrevoke_tokens

    Revokes tokens matching specified target criteria such as clientId or revocationKey. Forces affected clients to re-authenticate. Returns revocation details with timestamps.

Push channel, 1 operation

  • GETlist_push_channels

    Lists all channels that have at least one push subscription. Returns a paginated array of channel name strings.

Stat, 1 operation

  • GETget_stats

    Retrieves usage statistics for your Ably app. Get message counts, peak connections, API calls, and bandwidth. Aggregate by minute, hour, day, or month.

Time, 1 operation

  • GETget_time

    Returns the current Ably server time as milliseconds since the Unix epoch. Useful for clock synchronization and verifying connectivity. No authentication required.

Use Ably from Claude Code, Cursor or Codex

Connect Ably in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Ably 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 Ably

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Ably once

    Add your Ably connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. 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.

Ably integration FAQ

What can you do with the Ably integration?
LiveContext exposes 32 operations on Ably, covering push device, message, annotation and presence. Common uses include push administration, edit history and token refresh.

Popular integrations

Browse the whole catalog