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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/CrashBytes/pusher-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server