
Pusher Mcp
io.github.mrfentmenv1.0.0Updated Oct 1, 2026
Query the Pusher HTTP API: channels, channel details, channel users.
Overview
AI-generated overview
Lets an assistant query the Pusher HTTP API for channels, channel details, and channel users.
- What it does
- This local MCP server exposes tools that query the Pusher HTTP API. Based on the description, it can list channels, fetch details for a specific channel, and retrieve the users currently subscribed to a channel. It runs as a local process over stdio and does not list any additional tools.
- When to use it
- Useful when you work with Pusher Channels and want an assistant to inspect channel state, such as which channels exist, what a channel looks like, or who is subscribed. It is aimed at read-style inspection of Pusher data rather than general development tasks.
- Requirements
- Runs as a local process on the user's machine over stdio, installed from the npm package pusher-mcp, so Node.js and npm are needed. The manifest declares no authentication, environment variables, or headers, but querying the Pusher HTTP API normally requires Pusher app credentials, so expect to supply them yourself.
Before you install
The manifest declares no authentication and no environment variables, yet the Pusher HTTP API is normally accessed with app credentials; any keys you provide should be treated as secrets. The description only mentions querying channels, channel details, and channel users, so verify whether the server can also write or change data before relying on it.
Installation
In SourceWeft
- Open Pusher Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 1, 2026

