ably

MCP server for Ably — channel history, presence, occupancy, stats, publish, and app management.

我該用這個嗎

品質與安全性

A
說明品質
99%
結構描述完整度
88%
命名品質
80%
汙染風險
100%
權限相符程度
100%
協定合規性
100%

根據工具定義與協定合規性的自動化分析。

上下文成本

~2,329Token(工具定義)
~1.1 KB典型回應大小
中等的注意力影響(128k 上下文的 1.82%)

這是每次將伺服器的工具載入模型上下文時所消耗的約略 token 數量。數量越高,可用於其他工作的注意力就越少。

安裝

一鍵安裝

將以下內容加入你的 `claude_desktop_config.json` 檔案:

{
  "mcpServers": {
    "ably": {
      "url": "https://ably.usefulapi.io/mcp"
    }
  }
}

遠端端點

https://ably.usefulapi.io/mcpstreamable-http

它能做什麼

工具清單

工具(15)

🟢 唯讀🟡 寫入🔴 刪除⚪ 未知
🟢ably_get_channel_history(channel, start, end, limit, direction)

Retrieve historical messages published to a channel, newest-first by default. REST: GET /channels/{channel}/messages.

輸入結構描述

{
  "type": "object",
  "properties": {
    "channel": {
      "type": "string",
      "description": "Channel name, e.g. 'chat:room1'."
    },
    "start": {
      "description": "Earliest message time, ms since epoch (inclusive).",
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "end": {
      "description": "Latest message time, ms since epoch (inclusive).",
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "limit": {
      "description": "Max messages (<=1000). Default 100.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 1000
    },
    "direction": {
      "description": "forwards (oldest-first) or backwards (newest-first, default).",
      "type": "string",
      "enum": [
        "forwards",
        "backwards"
      ]
    }
  },
  "required": [
    "channel"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_get_presence(channel, clientId, connectionId, limit)

List the members currently present on a channel (who is online now). REST: GET /channels/{channel}/presence.

輸入結構描述

{
  "type": "object",
  "properties": {
    "channel": {
      "type": "string",
      "description": "Channel name."
    },
    "clientId": {
      "description": "Filter to a specific clientId.",
      "type": "string"
    },
    "connectionId": {
      "description": "Filter to a specific connectionId.",
      "type": "string"
    },
    "limit": {
      "description": "Max members (<=1000). Default 100.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 1000
    }
  },
  "required": [
    "channel"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_get_presence_history(channel, start, end, limit, direction)

Retrieve historical presence events (enter/leave/update) for a channel. REST: GET /channels/{channel}/presence/history.

輸入結構描述

{
  "type": "object",
  "properties": {
    "channel": {
      "type": "string",
      "description": "Channel name."
    },
    "start": {
      "description": "Earliest event time, ms since epoch (inclusive).",
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "end": {
      "description": "Latest event time, ms since epoch (inclusive).",
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "limit": {
      "description": "Max events (<=1000). Default 100.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 1000
    },
    "direction": {
      "description": "forwards or backwards (default backwards).",
      "type": "string",
      "enum": [
        "forwards",
        "backwards"
      ]
    }
  },
  "required": [
    "channel"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_get_channel_details(channel)

Get status and occupancy metrics for a single channel (connections, publishers, subscribers, presence members). REST: GET /channels/{channel}.

輸入結構描述

{
  "type": "object",
  "properties": {
    "channel": {
      "type": "string",
      "description": "Channel name."
    }
  },
  "required": [
    "channel"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_list_channels(prefix, limit, by)

Enumerate channels that are currently active in the app. Requires the API key to have the 'channel-metadata' capability. REST: GET /channels.

輸入結構描述

{
  "type": "object",
  "properties": {
    "prefix": {
      "description": "Only return channels whose name starts with this prefix.",
      "type": "string"
    },
    "limit": {
      "description": "Max channels per page (<=1000). Default 100.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 1000
    },
    "by": {
      "description": "Return channel ids only ('id', default) or full details ('value').",
      "type": "string",
      "enum": [
        "id",
        "value"
      ]
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_get_stats(start, end, unit, limit, direction)

Retrieve message/connection/channel usage statistics for the app tied to the API key, bucketed by time. REST: GET /stats.

輸入結構描述

{
  "type": "object",
  "properties": {
    "start": {
      "description": "Start of range, ms since epoch (inclusive).",
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "end": {
      "description": "End of range, ms since epoch (inclusive).",
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "unit": {
      "description": "Bucket size: minute | hour | day | month. Default minute.",
      "type": "string",
      "enum": [
        "minute",
        "hour",
        "day",
        "month"
      ]
    },
    "limit": {
      "description": "Max buckets (<=1000). Default 100.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 1000
    },
    "direction": {
      "description": "forwards or backwards (default backwards).",
      "type": "string",
      "enum": [
        "forwards",
        "backwards"
      ]
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_get_service_time

Return the current Ably service time in ms since epoch. Useful for aligning start/end windows to the server clock. REST: GET /time.

輸入結構描述

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴ably_publish_message(channel, data, name, clientId)

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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "channel": {
      "type": "string",
      "description": "Channel name to publish to, e.g. 'chat:room1'."
    },
    "data": {
      "type": "string",
      "description": "Message payload (string; send JSON as a stringified value)."
    },
    "name": {
      "description": "Optional event name for the message.",
      "type": "string"
    },
    "clientId": {
      "description": "Optional clientId to attribute the message to.",
      "type": "string"
    }
  },
  "required": [
    "channel",
    "data"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_whoami

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.

輸入結構描述

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_list_apps(account_id)

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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "account_id": {
      "description": "Override the account id (defaults to the token's account).",
      "type": "string"
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_list_keys(app_id)

List the API keys for an app, including their capabilities (but not the full secret). Control API: GET /apps/{app_id}/keys.

輸入結構描述

{
  "type": "object",
  "properties": {
    "app_id": {
      "type": "string",
      "description": "App id (from ably_list_apps)."
    }
  },
  "required": [
    "app_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_list_namespaces(app_id)

List the channel namespaces (channel-rule prefixes) configured for an app, e.g. persistence and push settings. Control API: GET /apps/{app_id}/namespaces.

輸入結構描述

{
  "type": "object",
  "properties": {
    "app_id": {
      "type": "string",
      "description": "App id (from ably_list_apps)."
    }
  },
  "required": [
    "app_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_list_queues(app_id)

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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "app_id": {
      "type": "string",
      "description": "App id (from ably_list_apps)."
    }
  },
  "required": [
    "app_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_list_rules(app_id)

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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "app_id": {
      "type": "string",
      "description": "App id (from ably_list_apps)."
    }
  },
  "required": [
    "app_id"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ably_get_account_stats(account_id, start, end, unit, limit)

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.

輸入結構描述

{
  "type": "object",
  "properties": {
    "account_id": {
      "description": "Override the account id (defaults to the token's account).",
      "type": "string"
    },
    "start": {
      "description": "Start of range, ms since epoch (inclusive).",
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "end": {
      "description": "End of range, ms since epoch (inclusive).",
      "type": "integer",
      "minimum": -9007199254740991,
      "maximum": 9007199254740991
    },
    "unit": {
      "description": "Bucket size: minute | hour | day | month. Default minute.",
      "type": "string",
      "enum": [
        "minute",
        "hour",
        "day",
        "month"
      ]
    },
    "limit": {
      "description": "Max buckets (<=1000). Default 100.",
      "type": "integer",
      "exclusiveMinimum": 0,
      "maximum": 1000
    }
  },
  "$schema": "http://json-schema.org/draft-07/schema#"
}

建議的提示詞

retrieve_data
Get details about [item] from ably
預期的工具: ably_get_channel_history
fetch_info
Fetch [information type] using ably
預期的工具: ably_get_channel_history
list_items
List all [items] available in ably
預期的工具: ably_list_channels
browse_collection
Show me the [collection] from ably
預期的工具: ably_list_channels
explore_workflow
List available [items], then get details for each one using ably
預期的工具: ably_list_channelsably_get_channel_history

社群

為此伺服器評分

證據

近期觀測

已驗證未記錄版本15 個工具