An astronaut overseeing a futuristic data hub

Connect Pusher Channels to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage your pub/sub infrastructure through natural language.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 6 capabilities

We ship only the actions that matter.

Capability set01 / 02

01-03

3 capabilities in this set.

Part of 6 available through Pusher.

  1. 01

    List channel users

    This capability retrieves a list of user IDs currently subscribed to a presence channel.

  2. 02

    Terminate user connections

    This capability kills all active WebSocket connections for a specific user ID.

  3. 03

    Get channel

    This capability fetches detailed metadata and state information for a specific channel.

Capability set02 / 02

04-06

3 capabilities in this set.

Part of 6 available through Pusher.

  1. 04

    List channels

    This capability returns a list of all active channels, which you can filter by prefix.

  2. 05

    Trigger batch events

    This capability sends multiple events in a single batch request to your channels.

  3. 06

    Trigger event

    This capability broadcasts a single event with a JSON payload up to 10KB to one or more channels.

Real work

What teams actually run

01

Frontend Testing

Trigger specific events to verify that your UI reacts correctly to real-time data changes.

02

Real-time Debugging

Inspect channel metadata and user lists to find why messages aren't reaching clients.

03

Security Response

Force a logout for a specific user by terminating their active WebSocket connections.

04

System Monitoring

Check active channel counts and presence data to monitor real-time engagement levels.

Automate a task

Put Pusher to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Pusher works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put Pusher to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

1053ms average. Fast in production.

Pusher is checked daily against the live service.

Daily averagePeak 1165ms
Oct 15Today
Fastest day
847ms
Slowest day
1165ms
14-day trend
Slowing+38%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 6 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Pusher, so you can see the experience inside your AI.

It does not authenticate your account with Pusher. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Pusher Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_yRJE9grBoLPiJPp9QRqfgvOF042J4MHGLBDKtu7Z/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Pusher capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "pusher-channels-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_yRJE9grBoLPiJPp9QRqfgvOF042J4MHGLBDKtu7Z/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Pusher in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Pusher owners hand off.

This MCP is built for engineers who manage real-time pub/sub architectures and need to move faster during development and debugging.

  • 01

    Full-stack Developers

    They use the agent to trigger test events and verify webhook payloads directly from their editor.

  • 02

    DevOps Engineers

    They hand off channel monitoring and user count checks to the agent to avoid the Pusher dashboard.

  • 03

    Support Teams

    They use the agent to identify connected users or terminate problematic sessions quickly.

FAQ

Questions Pusher owners ask.

  • 01

    How do I connect this MCP to my AI client?

    You subscribe to the MCP on Vinkius and provide your Pusher credentials. Once connected, you can immediately start using it in any MCP-compatible client like Claude or Cursor.

  • 02

    What credentials do I need to provide?

    You will need your Pusher App ID, Key, Secret, and Cluster information to authenticate the connection.

  • 03

    Can I trigger events with custom data?

    Yes. You can use the trigger_event capability to send JSON payloads up to 10KB to your channels.

  • 04

    Is it possible to kick a user off a channel?

    Yes. You can use the terminate_user_connections capability to end all active WebSocket connections for a specific user ID.

  • 05

    Does this work with any Pusher channel type?

    The MCP supports standard channels and presence channels, allowing you to list users and inspect channel states.

  • 06

    Can I send the same event to multiple channels at once?

    Yes. The trigger_event capability accepts an array of channel names (up to 100) to broadcast your message simultaneously across your infrastructure.

  • 07

    How do I check which users are currently online in a presence channel?

    Use the list_channel_users capability with the specific channel name (must start with presence-). It will return a list of all active user IDs.

  • 08

    Is it possible to force a user to disconnect?

    Yes. The terminate_user_connections capability allows you to close all active WebSocket connections for a specific user ID immediately.

Connect Pusher to Claude, Cursor, ChatGPT & more