Other · Local MCP server
Pusher Channels
Trigger events, query channels, and manage realtime messaging on Pusher Channels.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.CrashBytes/pusher-mcp-server- Version
- 1.0.3
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-02-13
- Updated
- 2026-02-13
- Publisher
- CrashBytes (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/CrashBytes) · how
- Repository
- github.com/CrashBytes/pusher-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @crashbytes/pusher-mcp-server | 1.0.3 | stdio |
How to connect Pusher Channels
Pusher Channels runs locally from a Node.js package published to the npm registry: @crashbytes/pusher-mcp-server version 1.0.3. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @crashbytes/pusher-mcp-server@1.0.3. It reads these environment variables: PUSHER_APP_ID (required), PUSHER_KEY (required), PUSHER_SECRET (required, secret) and PUSHER_CLUSTER (required); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"pusher-mcp-server": {
"command": "npx",
"args": [
"-y",
"@crashbytes/pusher-mcp-server@1.0.3"
],
"env": {
"PUSHER_APP_ID": "<value>",
"PUSHER_KEY": "<value>",
"PUSHER_SECRET": "<secret>",
"PUSHER_CLUSTER": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| PuppetflowBuild, run, monitor, and control Puppetflow browser automations from AI clients. | Remote · HTTP |
| purchaseiq.ioPre-purchase trust checks for AI agents: recalls, scam signals, proceed/caution/avoid verdict. | Remote · HTTPLive check: ✓ handshake |
| PursersCoordinate AI-agent work on a local-first, owner-controlled MCP board. | Local · HTTP, stdio |
| PusharyThe decision layer for AI agents. Your agent asks, a person approves or denies on their phone. | Remote · HTTP, SSELive check: ✓ handshake |
| Pusher MCPQuery the Pusher HTTP API: channels, channel details, channel users. | Local · stdio |
| pushinpay.com.brMCP oficial da PushinPay: cobranças PIX, consulta de transações e saldo via IA. | Local · stdio |
| puter.comPuter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more. | Remote · HTTPLive check: sign-in required |
| Putput MCPFile uploads for AI agents. Upload, list, and manage files. No signup required. | Remote & Local · HTTP, stdioLive check: ✓ handshake |