What is the key difference between Pusher Channels and Nworks?

Pusher Channels belongs to the Communication category with cloud HTTP/SSE execution, while Nworks belongs to the Communication category with local stdio execution.

How do I install Pusher Channels or Nworks in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Pusher Channels and Nworks free or paid?

Pusher Channels operates under a Free / Open Source model (No auth required). Nworks operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Pusher Channels lists 7 tools with 0 views and 3 GitHub stars. Nworks lists 33 tools with 2 views and 23 GitHub stars.

Can I use both Pusher Channels and Nworks together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

How do I install Pusher Channels or Nworks in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Pusher Channels and Nworks free to use, or do they require API keys?

Pusher Channels is listed under a Free / Open Source model with No auth required . Nworks operates under a Free / Open Source model with API Key required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Pusher Channels and Nworks at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both pusher-channels and yjcho9317-nworks as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Pusher Channels has a Quality Score of 52 /100 ( Good ) with 0 views, 0 installs, and 3 GitHub stars. Nworks holds a Quality Score of 60 /100 ( Good ) with 2 views, 0 installs, and 23 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Pusher Channels vs Nworks

In-depth architectural comparison of the Pusher Channels and Nworks MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Pusher Channels

Communication · Remote HTTP/SSE

Quality: 52/100 (Good) | Auth: No auth required

Nworks

Communication · Local stdio

Quality: 60/100 (Good) | Auth: API Key required

Verdict Summary: Choose Pusher Channels if you need specialized Communication tools running via a hosted cloud SSE transport. Choose Nworks if your workspace requires Communication integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Pusher Channels when:

You need dedicated capabilities in the Communication domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: trigger_event, trigger_batch_events, list_channels.

Explore Pusher Channels Details

Choose Nworks when:

You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: CLIENT_ID, CLIENT_SECRET, PRIVATE_KEY_PATH.
Primary tools included: Setup, nworks_setup, nworks_login_user.

Explore Nworks Details

Feature & Specification Comparison

Specification	P Pusher Channels Communication	Nworks yjcho9317 Communication
Summary	Trigger events, query channels, and manage realtime messaging on Pusher Channels.	NAVER WORKS CLI + MCP server. 26 tools for messages, calendar, drive, mail, tasks, and boards. AI agents can manage NAVER WORKS directly.
Category & Scope	Communication	Communication

Tools & Capabilities Breakdown

Pusher Channels Tools (7)

trigger_event

Send an event to one or more channels

trigger_batch_events

Send up to 10 events in a single API call

list_channels

List active channels with optional prefix filter

get_channel_info

Get subscription/user count for a channel

get_presence_users

List users connected to a presence channel

authorize_channel

Generate auth tokens for private/presence channels

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Pusher Channels Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "pusher-channels": {
      "url": "https://modelcontextprotocol.io"
    }
  }
}

Nworks Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "yjcho9317-nworks": {
      "command": "npx",
      "args": [
        "-y",
        "nworks"
      ],
      "env": {
        "CLIENT_ID": "YOUR_CLIENT_ID_HERE",
        "CLIENT_SECRET": "YOUR_CLIENT_SECRET_HERE",
        "PRIVATE_KEY_PATH": "YOUR_PRIVATE_KEY_PATH_HERE"
      }
    }
  }
}

Frequently Asked Questions

Pusher Channels is categorized under Communication and uses a remote streaming HTTP/SSE transport. In contrast, Nworks belongs to Communication using local stdio subprocess. Select Pusher Channels when you need capabilities focused on communication and Nworks when you require tools for communication.

More alternatives to Pusher Channels More alternatives to Nworks Communication category hub