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
Each tool targets a distinct resource+action: getting one channel's info, listing all channels, listing presence users, authorizing, triggering single vs batch events, and terminating users. The only mild adjacency is get_channel_info vs list_channels, but descriptions make the single-vs-collection boundary explicit.
All 7 tools follow a consistent snake_case verb_noun pattern (get_, list_, authorize_, terminate_, trigger_). No mixing of conventions or vague verbs.
7 tools is well-scoped for the Pusher Channels HTTP API surface, with no redundant or filler tools. Each maps to a meaningful capability agents need.
Covers the core lifecycle: channel info, channel listing, presence users, auth, event triggering (single and batch), and user termination. Minor gaps exist (e.g. webhook/signature handling or per-channel event queries), but core realtime workflows are fully covered.