Read occupied channel names and known channel occupancy from your own Pusher Channels app. Requests are signed server-side with the app secret and bound to its app ID and public cluster. No presence users, subscriber counts, cached messages, event publishing, websocket connections, polling, retries or managed OAuth.
What you can do (2)
What you can do
Available commands: 2 (2 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List occupied channels — pusher.channels.list |
Read |
Read channel occupancy — pusher.channels.get |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for Pusher Channels, then enter the issued values in the connection form below.
- In the Pusher dashboard select your Channels app and open App Keys. Copy app_id, key, secret and cluster into Pusher app ID, Pusher app key, Pusher app secret and Pusher cluster in this integration’s connection form. Use credentials from the same app and its exact public cluster. The key may be used by Pusher clients, but the app secret is a server-only credential and must never go in client settings or command input. Save, allow channel reads and call examples with your separate Tooluse.net API key. Tooluse.net signs each HTTPS GET with the app secret, timestamp and credential-bound app path. This subset lists occupied channel names or reads one channel’s occupied status, without presence users, subscriber counts, cached messages or event publishing. Lists are unpaged and bounded by the existing response-size limit; your Pusher plan and request limits apply. No websocket subscriptions, event writes, custom dedicated clusters, polling, retries or managed OAuth.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| Pusher app ID | Required |
| Pusher app key | Required |
| Pusher app secret | Required |
| Pusher cluster | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
List occupied channels — pusher.channels.list
List occupied channel names in your Pusher Channels app. The documented collection is unpaged and bounded by the existing response-size limit. No subscription/user counts, message caches or event publishing.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read channel occupancy — pusher.channels.get
Read whether a known channel in your Pusher Channels app is occupied. Returns only occupied status, without subscription/user counts, presence members or cached message data.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.channel_name |
string | Required | Channel name; this subset accepts letters, numbers, underscore, hyphen and dot up to 200 characters. | minLength: 1; maxLength: 200; pattern: "^[A-Za-z0-9_.-]+$" |
Full JSON Schema
Example input
{
"path": {
"channel_name": "public-example"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.