Slack vs Nworks

In-depth architectural comparison of the Slack 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.

Which MCP Server Should You Choose?

Choose Slack when:

• You need dedicated capabilities in the Communication domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: inbox, messages, estate.

Explore Slack Details

Choose Nworks when:

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

Explore Nworks Details

Feature & Specification Comparison

Specification	Slack Communication	Nworks yjcho9317 Communication
Summary	Read and write Slack with session tokens — no OAuth, no bot, no admin approval.	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

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).

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": [
        "-y",
        "@aaronsb/slack-mcp"
      ]
    }
  }
}

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

Related MCP Server Comparisons