Server providing Argo CD integration for MCP clients.
Nothing to run from here
Ably is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
90/100
tool-list score
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
MCP server for Ably — channel history, presence, occupancy, stats, publish, and app management.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http ably-mcp https://ably.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# ably_get_channel_history, ably_get_presence, ably_get_presence_history and 12 more
Ably costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http ably-mcp https://ably.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Retrieve historical messages published to a channel, newest-first by default. REST: GET /channels/{channel}/messages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | string | yes | Channel name, e.g. 'chat:room1'. |
| start | integer | no | Earliest message time, ms since epoch (inclusive). |
| end | integer | no | Latest message time, ms since epoch (inclusive). |
| limit | integer | no | Max messages (<=1000). Default 100. |
| direction | string | no | forwards (oldest-first) or backwards (newest-first, default). |
List the members currently present on a channel (who is online now). REST: GET /channels/{channel}/presence.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | string | yes | Channel name. |
| clientId | string | no | Filter to a specific clientId. |
| connectionId | string | no | Filter to a specific connectionId. |
| limit | integer | no | Max members (<=1000). Default 100. |
Retrieve historical presence events (enter/leave/update) for a channel. REST: GET /channels/{channel}/presence/history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | string | yes | Channel name. |
| start | integer | no | Earliest event time, ms since epoch (inclusive). |
| end | integer | no | Latest event time, ms since epoch (inclusive). |
| limit | integer | no | Max events (<=1000). Default 100. |
| direction | string | no | forwards or backwards (default backwards). |
Get status and occupancy metrics for a single channel (connections, publishers, subscribers, presence members). REST: GET /channels/{channel}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | string | yes | Channel name. |
Enumerate channels that are currently active in the app. Requires the API key to have the 'channel-metadata' capability. REST: GET /channels.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prefix | string | no | Only return channels whose name starts with this prefix. |
| limit | integer | no | Max channels per page (<=1000). Default 100. |
| by | string | no | Return channel ids only ('id', default) or full details ('value'). |
Retrieve message/connection/channel usage statistics for the app tied to the API key, bucketed by time. REST: GET /stats.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start | integer | no | Start of range, ms since epoch (inclusive). |
| end | integer | no | End of range, ms since epoch (inclusive). |
| unit | string | no | Bucket size: minute | hour | day | month. Default minute. |
| limit | integer | no | Max buckets (<=1000). Default 100. |
| direction | string | no | forwards or backwards (default backwards). |
Return the current Ably service time in ms since epoch. Useful for aligning start/end windows to the server clock. REST: GET /time.
No parameter schema on file.
WRITE: publish a message to a channel. Every connected subscriber receives it in real time. This is a real, outward-facing side effect — confirm the channel and payload before calling. REST: POST /channels/{channel}/messages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| channel | string | yes | Channel name to publish to, e.g. 'chat:room1'. |
| data | string | yes | Message payload (string; send JSON as a stringified value). |
| name | string | no | Optional event name for the message. |
| clientId | string | no | Optional clientId to attribute the message to. |
Return details about the configured control token: the account and user it belongs to and its capabilities. Good first call to confirm control-plane access. Control API: GET /me.
No parameter schema on file.
List all apps in the account (id, name, status, tls-only). Account id is resolved automatically from the control token when ABLY_ACCOUNT_ID is unset. Control API: GET /accounts/{account_id}/apps.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | string | no | Override the account id (defaults to the token's account). |
List the API keys for an app, including their capabilities (but not the full secret). Control API: GET /apps/{app_id}/keys.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | string | yes | App id (from ably_list_apps). |
List the channel namespaces (channel-rule prefixes) configured for an app, e.g. persistence and push settings. Control API: GET /apps/{app_id}/namespaces.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | string | yes | App id (from ably_list_apps). |
List the Ably Queues (AMQP/STOMP message queues) provisioned for an app, with their state and messaging stats. Control API: GET /apps/{app_id}/queues.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | string | yes | App id (from ably_list_apps). |
List the integration rules (reactor rules: webhooks, AWS Lambda/SQS/Kinesis, Kafka, Pulsar, etc.) configured for an app. Control API: GET /apps/{app_id}/rules.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| app_id | string | yes | App id (from ably_list_apps). |
Retrieve aggregated usage statistics across the whole account, bucketed by time. Account id is resolved from the control token when ABLY_ACCOUNT_ID is unset. Control API: GET /accounts/{account_id}/stats.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| account_id | string | no | Override the account id (defaults to the token's account). |
| start | integer | no | Start of range, ms since epoch (inclusive). |
| end | integer | no | End of range, ms since epoch (inclusive). |
| unit | string | no | Bucket size: minute | hour | day | month. Default minute. |
| limit | integer | no | Max buckets (<=1000). Default 100. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Ably or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 90 / 100
Release 1.11.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score90
Findings0 threat · 1 capability
Capabilityhigh
Coveragemanifest
Verificationnot in this report
Surface digest08ed5c5614e1db142702ef2cb2935aacc3f9cbc2f7ed1fa655271f39027ba011
Score vectorthreat 100 → client 90
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ably_get_channel_history | no tags | |
| ably_get_presence | no tags | |
| ably_get_presence_history | no tags | |
| ably_get_channel_details | no tags | |
| ably_list_channels | no tags | |
| ably_get_stats | no tags | |
| ably_get_service_time | no tags | |
| ably_publish_message | external-sinkstate-write | external-sink: keyword "publish_message"; state-write: declares readOnlyHint: false, destructiveHint: true |
| ably_whoami | no tags | |
| ably_list_apps | no tags | |
| ably_list_keys | sensitive-source | sensitive-source: keyword "list_keys" |
| ably_list_namespaces | no tags | |
| ably_list_queues | no tags | |
| ably_list_rules | no tags | |
| ably_get_account_stats | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
ably_list_keys → ably_publish_message
A sensitive-source → external-sink chain exists: ably_list_keys ⇒ ably_publish_message.
Supply chain and provenance
Integrityfirst-seen
Surface digest08ed5c5614e1db14
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Ably can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.