Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"pusher": {
"env": {
"PUSHER_KEY": "your_app_key",
"PUSHER_APP_ID": "your_app_id",
"PUSHER_SECRET": "your_app_secret",
"PUSHER_CLUSTER": "us2"
},
"args": [
"/path/to/pusher-mcp-server/build/index.js"
],
"command": "node"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An MCP (Model Context Protocol) server that gives AI agents the ability to send realtime messages, query channels, and manage users through Pusher Channels.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@crashbytes/pusher-mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @crashbytes/pusher-mcp-server against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
PubNub Model Context Protocol MCP Server for Cursor and Claude
Social layer for Claude Code - DMs, presence, discovery, and games between AI-assisted developers
MCP server for Voximplant API — call history, users, SMS. 3 tools.
MCP Security Weekly
Get CVE alerts and security updates for Pusher MCP Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
An MCP (Model Context Protocol) server that gives AI agents the ability to send realtime messages, query channels, and manage users through Pusher Channels.
| Tool | Description |
|---|---|
trigger_event | Send an event to one or more channels |
trigger_batch_events | Send up to 10 events in a single API call |
list_channels | List active channels with optional prefix filter |
get_channel_info | Get subscription/user count for a channel |
get_presence_users | List users connected to a presence channel |
authorize_channel | Generate auth tokens for private/presence channels |
terminate_user_connections | Disconnect all connections for a user |
npm install -g @crashbytes/pusher-mcp-server
Or clone and build from source:
git clone https://github.com/CrashBytes/pusher-mcp-server.git
cd pusher-mcp-server
npm install
npm run build
You need four environment variables from your Pusher dashboard:
| Variable | Description |
|---|---|
PUSHER_APP_ID | Your Pusher app ID |
PUSHER_KEY | Your Pusher app key |
PUSHER_SECRET | Your Pusher app secret |
PUSHER_CLUSTER | Your Pusher cluster (e.g. us2, eu, ap1) |
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"
}
}
}
}
claude mcp add pusher -- node /path/to/pusher-mcp-server/build/index.js
Set the environment variables in your shell before running, or configure them in your Claude Code MCP settings.
Once configured, you can ask Claude things like:
npm install
npm run dev # Run with tsx (hot reload)
npm run build # Compile TypeScript
npm run type-check # Check types without emitting
For a step-by-step guide on building this server from scratch, see the full tutorial on CrashBytes.
MIT