Skip to main content
Glama
CrashBytes

Pusher Channels MCP Server

by CrashBytes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Pusher Channels MCP Server

No user-submitted related servers found.

    Related Servers

    • fluxpy

      saudaljuaid
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables real-time data streaming for AI agents, with persistent connections to live feeds, reactive operator pipelines, and consumption via push, pull, or block modes.
      MIT

    • agent-comm

      keshrath
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.
      44 npm
      8
      MIT

    • pumble-mcp

      nitindermohan
      F
      license
      Not graded
      quality
      D
      maintenance
      A 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.
      -
    • LINE Bot MCP Server by line

      LINE Bot MCP Serverofficial

      line
      A
      license
      A
      quality
      A
      maintenance
      MCP server that integrates the LINE Messaging API to enable AI agents to send messages and manage LINE Official Accounts.
      12
      643 npm
      782
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools target distinct actions (trigger, list, get, authorize, terminate). The only overlap is between trigger_event and trigger_batch_events, but descriptions clearly differentiate single vs. batch. Slight confusion possible between list_channels and get_channel_info, though one lists while the other fetches a single channel.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case (e.g., trigger_event, list_channels, get_channel_info). Verbs are clear and consistent, and compound names like trigger_batch_events and terminate_user_connections align with the same convention.

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range. Each tool covers a necessary operation for a Pusher Channels server without redundancy, making the set appropriately scoped.

    Completeness5/5

    The tool set covers the core lifecycle: triggering events (single/batch), inspecting channels, retrieving presence users, authorizing private/presence access, and terminating users. No major gaps are apparent for the domain; all common Pusher Channels operations are represented.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources