Pusher Channels MCP Server
Provides tools for sending realtime events, querying channels, managing users, and generating auth tokens through the Pusher Channels API.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Pusher Channels MCP Server Send a 'new-message' event to 'chat-room' with data 'Hello world'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Pusher Channels MCP Server
An MCP (Model Context Protocol) server that gives AI agents the ability to send realtime messages, query channels, and manage users through Pusher Channels.
Tools
Tool | Description |
| Send an event to one or more channels |
| Send up to 10 events in a single API call |
| List active channels with optional prefix filter |
| Get subscription/user count for a channel |
| List users connected to a presence channel |
| Generate auth tokens for private/presence channels |
| Disconnect all connections for a user |
Related MCP server: agent-comm
Prerequisites
Node.js 18 or later
A Pusher Channels account (free tier available)
Installation
npm install -g @crashbytes/pusher-mcp-serverOr clone and build from source:
git clone https://github.com/CrashBytes/pusher-mcp-server.git
cd pusher-mcp-server
npm install
npm run buildConfiguration
You need four environment variables from your Pusher dashboard:
Variable | Description |
| Your Pusher app ID |
| Your Pusher app key |
| Your Pusher app secret |
| Your Pusher cluster (e.g. |
Usage with Claude Desktop
Add the following to your Claude Desktop config file:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"pusher": {
"command": "node",
"args": ["/path/to/pusher-mcp-server/build/index.js"],
"env": {
"PUSHER_APP_ID": "your_app_id",
"PUSHER_KEY": "your_app_key",
"PUSHER_SECRET": "your_app_secret",
"PUSHER_CLUSTER": "us2"
}
}
}
}If installed globally via npm:
{
"mcpServers": {
"pusher": {
"command": "pusher-mcp-server",
"env": {
"PUSHER_APP_ID": "your_app_id",
"PUSHER_KEY": "your_app_key",
"PUSHER_SECRET": "your_app_secret",
"PUSHER_CLUSTER": "us2"
}
}
}
}Usage with Claude Code
claude mcp add pusher -- node /path/to/pusher-mcp-server/build/index.jsSet the environment variables in your shell before running, or configure them in your Claude Code MCP settings.
Example Prompts
Once configured, you can ask Claude things like:
"Send a 'deploy-complete' event to the notifications channel with the message 'v2.1.0 deployed'"
"Show me all active presence channels"
"How many users are on the presence-lobby channel?"
"Disconnect user abc123 from all channels"
Development
npm install
npm run dev # Run with tsx (hot reload)
npm run build # Compile TypeScript
npm run type-check # Check types without emittingTutorial
For a step-by-step guide on building this server from scratch, see the full tutorial on CrashBytes.
License
MIT
Available Tools
7 toolsauthorize_channelA
Generate an authorization token for a private or presence channel. Useful when building auth endpoints for Pusher client connections.
Inputs: channel (required), socketId (required), presenceData.
get_channel_infoA
Get detailed information about a specific Pusher channel, including whether it is occupied and optional subscription/user counts.
Inputs: channel (required), info.
get_presence_usersA
List all users currently connected to a presence channel. Only works with channels that start with 'presence-'.
Inputs: channel (required).
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.
Inputs: info, prefix.
terminate_user_connectionsA
Disconnect all connections for a specific user. Useful for moderation or security — forces a user offline across all channels.
Inputs: userId (required).
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.
Inputs: events (required).
trigger_eventA
Send an event to one or more Pusher channels. Use this to push realtime messages to connected clients.
Inputs: data (required), event (required), channel (required), socketId.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
MCP server for Sendbird — chat users, channels, members, and messages from your AI client.
MCP server for building and testing AI agents with multi-model experimentation and insights.
MCP server for AI agents: posts, messages and comments on WhatsApp, Instagram, TikTok and Facebook.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Related MCP Servers
AlicenseAqualityAmaintenanceMCP server that integrates the LINE Messaging API to enable AI agents to send messages and manage LINE Official Accounts.122,059 npm807Apache 2.0- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.79 npm10MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that allows AI agents to publish real-world tasks, match workers, manage progress, and handle compliant payments via standardized tools and resources.32 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA standalone MCP server providing AI agents with full access to the Pumble messaging platform via OAuth2 and the Pumble SDK, including messaging, files, channels, search, scheduling, and real-time events.MIT