Pusher Channels MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUSHER_KEY | Yes | Your Pusher app key | |
| PUSHER_APP_ID | Yes | Your Pusher app ID | |
| PUSHER_SECRET | Yes | Your Pusher app secret | |
| PUSHER_CLUSTER | Yes | Your Pusher cluster (e.g., us2, eu, ap1) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| trigger_eventA | Send an event to one or more Pusher channels. Use this to push realtime messages to connected clients. |
| trigger_batch_eventsA | Send up to 10 events in a single API call. More efficient than triggering events individually when you need to notify multiple channels. |
| list_channelsA | List all active channels in your Pusher app. Optionally filter by prefix (e.g. 'presence-' or 'private-') and request subscription or user counts. |
| get_channel_infoA | Get detailed information about a specific Pusher channel, including whether it is occupied and optional subscription/user counts. |
| get_presence_usersA | List all users currently connected to a presence channel. Only works with channels that start with 'presence-'. |
| authorize_channelA | Generate an authorization token for a private or presence channel. Useful when building auth endpoints for Pusher client connections. |
| terminate_user_connectionsA | Disconnect all connections for a specific user. Useful for moderation or security — forces a user offline across all channels. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools target distinct actions (trigger, list, get, authorize, terminate). The only overlap is between trigger_event and trigger_batch_events, but descriptions clearly differentiate single vs. batch. Slight confusion possible between list_channels and get_channel_info, though one lists while the other fetches a single channel.
All tool names follow a consistent verb_noun pattern with snake_case (e.g., trigger_event, list_channels, get_channel_info). Verbs are clear and consistent, and compound names like trigger_batch_events and terminate_user_connections align with the same convention.
Seven tools is well within the ideal 3-15 range. Each tool covers a necessary operation for a Pusher Channels server without redundancy, making the set appropriately scoped.
The tool set covers the core lifecycle: triggering events (single/batch), inspecting channels, retrieving presence users, authorizing private/presence access, and terminating users. No major gaps are apparent for the domain; all common Pusher Channels operations are represented.