Pusher Channels vs fmsg
Pusher Channels is an MCP server published by CrashBytes. Marketplaces we read that list it: 1 (Official MCP Registry). fmsg is an MCP server published by markmnl. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Pusher Channels |  fmsg |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.3 Downloads/month (npm): 197 Downloads/week (npm): 33 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 1.2.0 Downloads/month (npm): 2 251 Downloads/week (npm): 1 240 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Pusher Channels | fmsg |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (better) | 1 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | On your machine (@crashbytes/pusher-mcp-server) | On your machine (@markmnl/fmsg-mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 4, secrets among them: 1 | 4, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/crashbytes/pusher-mcp-server | github.com/markmnl/fmsg-mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Pusher Channels
Trigger events, query channels, and manage realtime messaging on Pusher Channels.
fmsg
Federated messaging with your fmsg hosting provider. Connect with OAuth or an API key.
How to run each
Pusher Channels As a local MCP server: npm package
claude mcp add --env "PUSHER_APP_ID=<YOUR_PUSHER_APP_ID>" --env "PUSHER_CLUSTER=<YOUR_PUSHER_CLUSTER>" --env "PUSHER_KEY=<YOUR_PUSHER_KEY>" --env "PUSHER_SECRET=<YOUR_PUSHER_SECRET>" --transport stdio pusher-mcp-server -- npx -y @crashbytes/pusher-mcp-serverRequires: PUSHER_APP_ID, PUSHER_CLUSTER, PUSHER_KEY, PUSHER_SECRET (secret)
fmsg
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: FMSG_API_KEY (secret), FMSG_API_URL
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Pusher Channels asks for
PUSHER_APP_IDPUSHER_CLUSTERPUSHER_KEYPUSHER_SECRET (secret)
Only fmsg asks for
FMSG_API_KEY (secret)FMSG_API_URLFMSG_DEFAULT_DOMAINFMSG_MCP_DOWNLOAD_DIR
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Pusher Channels · What it can do: fmsg · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.