# Pusher Channels MCP > Pusher Channels MCP lets your AI client manage real-time messaging infrastructure directly through natural language. Trigger events, monitor which channels are active, list connected users, and even force logouts without touching a debug console or API dashboard. It's operational control for pub/sub systems. ## Overview - **Category:** developer-tools - **Price:** Free - **Tags:** real-time, websockets, pub-sub, event-broadcasting, webhooks ## Description This MCP connects your entire Pusher Channels setup to any compatible AI client, giving your agent direct access to real-time messaging controls. Instead of navigating separate dashboards to check system health, you talk to your AI and it executes the necessary operations immediately. You can trigger events—whether that's sending a single notification or broadcasting data across dozens of channels—by simply stating what needs to happen. It also lets you monitor who's connected right now; you get lists of active channels and see exactly which users are subscribed to presence streams. If security demands it, the agent can terminate specific user connections instantly. Connecting through Vinkius means your AI client accesses this control layer alongside thousands of other tools, making it a single point for managing complex web infrastructure. ## Tools ### get_channel Fetches specific metadata and status information for one particular communication channel. ### list_channel_users Retrieves the list of user IDs currently subscribed to a defined presence channel. ### list_channels Fetches an overview and status data for multiple existing channels. ### terminate_user_connections Stops all active WebSocket connections associated with a single user ID, forcing a logout or reset. ### trigger_batch_events Sends multiple events to various channels simultaneously in one efficient operation. ### trigger_event Sends a single, specific event with a defined data payload to one or more channels. ## Prompt Examples **Prompt:** ``` Trigger a 'new-order' event on the 'orders' channel with data '{"id": 123, "total": 50.00}'. ``` **Response:** ``` Event 'new-order' successfully triggered on channel 'orders'. The payload has been broadcasted to all active subscribers. ``` **Prompt:** ``` List all active channels that start with 'presence-'. ``` **Response:** ``` I found 3 active presence channels: 'presence-chat-room-1', 'presence-lobby', and 'presence-editor-v2'. Would you like to see the users in any of these? ``` **Prompt:** ``` Terminate all connections for user ID 'user_999'. ``` **Response:** ``` All active WebSocket connections for 'user_999' have been terminated. The user will need to re-authenticate to reconnect. ``` ## Capabilities ### Broadcast real-time events You can trigger specific messages or send multiple event batches to one or more channels instantly. ### Audit channel status and users The MCP lists all active channels, helps you filter them by prefix, and retrieves the current list of subscribed user IDs for any given presence channel. ### Control individual connections It handles security and session management by terminating all WebSocket connections for a specific user ID when needed. ## Use Cases ### Debugging an order webhook failure A developer notices that the 'orders' channel isn't receiving test notifications. They prompt their agent, asking it to `trigger_event` with a sample payload. The AI confirms if the event was broadcasted correctly and checks the channel state using `get_channel`, confirming the issue is upstream. ### Auditing user access during an incident The ops engineer suspects unauthorized access. They ask their agent to use `list_channels` to see all active channels, then select a suspicious channel and run `list_channel_users`. This immediately reveals who is currently subscribed. ### Forcing a user logout due to security risk A support team member needs to instantly disconnect an account. They instruct their agent to use `terminate_user_connections` with the user ID. The connection drops immediately, securing the session without needing console access. ### Updating multiple system components simultaneously A new feature launches across five different microservices that rely on real-time updates. Instead of running five separate commands, the engineer uses `trigger_batch_events` to update all channels in one go. ## Benefits - You stop jumping into the Pusher Debug Console. Instead, your AI client becomes a full infrastructure operator, allowing you to trigger test events and verify payloads instantly. - Manage user presence easily. You can use `list_channel_users` to get immediate lists of who's connected to a channel without manually checking status dashboards. - Maintain security by controlling sessions. The `terminate_user_connections` tool lets you force logouts or end problematic connections simply by naming the user ID. - Handling large updates is fast. Use `trigger_batch_events` when you need to send data across multiple channels at once, instead of running several single triggers. - Deep debugging visibility comes from tools like `get_channel`, letting you query a channel's detailed state—perfect for tracing message flow issues. ## How It Works The bottom line is that your AI acts like a real-time operations console for your messaging system. 1. First, subscribe to this MCP and provide your Pusher App ID, Key, Secret, and Cluster credentials. 2. Next, tell your AI client what action you need—for example, 'List all channels starting with payment-'. 3. The agent executes the command against your live infrastructure and reports the status or data back to you. ## Frequently Asked Questions **How do I check if a specific user is connected using Pusher Channels MCP?** Use `list_channel_users`. This tool fetches a clear list of all user IDs that are currently subscribed to the presence channel, giving you an instant count. **What's the difference between `trigger_event` and `trigger_batch_events`?** `trigger_event` is for sending one specific notification or data packet. Use `trigger_batch_events` when you need to send multiple, related events across several channels at once. **Can I force a user off the channel using Pusher Channels MCP?** Yes. The `terminate_user_connections` tool lets your agent kill all active WebSocket connections for a given user ID, forcing them to reauthenticate. **What if I want to see what channels are available in my app?** Use `list_channels`. This function fetches an overview of all existing communication channels and their current status data for auditing purposes.