Ably Control MCP integration for AI agents.
Connect AI agents to Ably Control through 14 structured actions, including get account stats, create app, and delete app. Review authentication, inputs, work…
- ACTION CONTRACTS
- 14
- 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 Control integration exposes
The Ably Control Agent App exposes 14 provider-backed actions for developer tools work. Its current contract lets an authorized agent retrieve account-level ably statistics for the connected account or account id, create an ably app in the connected account or supplied account id, and delete an ably app by app id. 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 Control account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Ably Control capabilities.
Showing 12 of 14 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_account_statsREADRetrieve account-level Ably statistics for the connected account or account ID.
INPUTS: accountId / appId / start / end / limit
create_appWRITECreate an Ably app in the connected account or supplied account ID.
INPUTS: accountId / name / status / tlsOnly / fcmKey
delete_appHIGH IMPACTDelete an Ably app by app ID.
INPUTS: appId
create_keyWRITECreate an API key for an Ably app.
INPUTS: appId / name / capability
create_queueWRITECreate a queue for an Ably app.
INPUTS: appId / name / region / ttl / maxLength
delete_queueHIGH IMPACTDelete an Ably queue by queue ID.
INPUTS: appId / queueId
get_app_statsREADRetrieve app-level Ably statistics for an Ably app.
INPUTS: accountId / appId / start / end / limit
get_current_accountREADRetrieve the Ably Control API token, user, and account associated with the access token.
list_appsREADList Ably apps in the connected account or supplied account ID.
INPUTS: accountId
list_keysREADList API keys for an Ably app.
INPUTS: appId
list_queuesREADList queues for an Ably app.
INPUTS: appId
revoke_keyHIGH IMPACTRevoke an Ably API key by key ID.
INPUTS: appId / keyId
INPUT CONTRACTS
Know what the action needs before it runs.
get_account_stats
accountIdOPTIONAL- The Ably account ID.
appIdOPTIONAL- The Ably application ID.
startOPTIONAL- A Unix timestamp in milliseconds.
endOPTIONAL- A Unix timestamp in milliseconds.
limitOPTIONAL- The maximum number of statistics records to return.
create_app
accountIdOPTIONAL- The Ably account ID.
nameREQUIRED- The app name.
statusOPTIONAL- The app status.
tlsOnlyOPTIONAL- Whether to enforce TLS for all connections.
fcmKeyOPTIONAL
delete_app
appIdREQUIRED- The Ably application ID.
create_key
appIdREQUIRED- The Ably application ID.
nameREQUIRED- The key name.
capabilityREQUIRED- Ably channel capabilities keyed by channel or resource name.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account Stats
Retrieve account-level Ably statistics for the connected account or account ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_account_statsControl Create App
Create an Ably app in the connected account or supplied account ID. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_appVerify with Get App Stats
Retrieve app-level Ably statistics for an Ably app. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_app_statsSAFETY BOUNDARY
Operate Ably Control with explicit limits
- Authorize Ably Control with API key and grant only the provider access required by the selected actions.
- 8 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_app`, `delete_queue`, and `revoke_key` 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 Control rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Ably Control task completed successfully.
CONNECTION MODEL
API key
Ably Control API access token used as a Bearer token. Create or view Control API access tokens in the Ably account dashboard: https://ably.com/users/access_tokens.
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
- 5
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 0
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 Control.