Skip to main content
Glama
Sign In
Pusher Channels MCP Server

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
      C
      maintenance
      MCP server that enables AI coding agents to communicate, share state, and coordinate work in real time via MCP tools or REST API.
      246 npm
      9
      MIT

    • pumble-mcp

      nitindermohan
      A
      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.
      MIT
    • LINE Bot MCP Server

      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
      3,415 npm
      796
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action: getting one channel's info, listing all channels, listing presence users, authorizing, triggering single vs batch events, and terminating users. The only mild adjacency is get_channel_info vs list_channels, but descriptions make the single-vs-collection boundary explicit.

    Naming Consistency5/5

    All 7 tools follow a consistent snake_case verb_noun pattern (get_, list_, authorize_, terminate_, trigger_). No mixing of conventions or vague verbs.

    Tool Count5/5

    7 tools is well-scoped for the Pusher Channels HTTP API surface, with no redundant or filler tools. Each maps to a meaningful capability agents need.

    Completeness4/5

    Covers the core lifecycle: channel info, channel listing, presence users, auth, event triggering (single and batch), and user termination. Minor gaps exist (e.g. webhook/signature handling or per-channel event queries), but core realtime workflows are fully covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources