What is the key difference between Joinly and Nworks?

Joinly belongs to the Communication category with local stdio execution, while Nworks belongs to the Communication category with local stdio execution.

How do I install Joinly 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 Joinly and Nworks free or paid?

Joinly operates under a BYOK (Pay Provider Direct) model (API Key required). Nworks operates under a Free / Open Source model (OAuth 2.0).

Which MCP server has more tools and community activity?

Joinly lists 12 tools with 2 views and 565 GitHub stars. Nworks lists 33 tools with 4 views and 25 GitHub stars.

Can I use both Joinly 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.

Side-by-Side Model Context Protocol Comparison

Joinly vs Nworks

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

Joinly

Communication · Local stdio

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

Nworks

Communication · Local stdio

Quality: 60/100 (Good) | Auth: OAuth 2.0

Verdict Summary: Choose Joinly if you need specialized Communication tools running via a local process. 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 Joinly when:

You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: JOINLY_LLM_MODEL, JOINLY_LLM_PROVIDER, OPENAI_API_KEY.
Primary tools included: join_meeting, leave_meeting, speak_text.

Explore Joinly 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.

Feature & Specification Comparison

Specification	Joinly joinly-ai Communication	Nworks yjcho9317 Communication
Summary	MCP server to interact with browser-based meeting platforms (Zoom, Teams, Google Meet). Enables AI agents to send bots to online meetings, gather live transcripts, speak text, and send messages in the meeting chat.	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

Tools & Capabilities Breakdown

Joinly Tools (12)

join_meeting

leave_meeting

speak_text

text

send_chat_message

message

mute_yourself

unmute_yourself

get_chat_history

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

Joinly Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "joinly-ai-joinly": {
      "command": "uvx",
      "args": [
        "joinly-client"
      ],
      "env": {
        "JOINLY_LLM_MODEL": "YOUR_JOINLY_LLM_MODEL_HERE",
        "JOINLY_LLM_PROVIDER": "YOUR_JOINLY_LLM_PROVIDER_HERE",
        "OPENAI_API_KEY": "YOUR_OPENAI_API_KEY_HERE"
      }
    }
  }
}

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"
      }
    }
  }
}

Frequently Asked Questions

Joinly is categorized under Communication and uses a local stdio subprocess. In contrast, Nworks belongs to Communication using local stdio subprocess. Select Joinly when you need capabilities focused on communication and Nworks when you require tools for communication.

More alternatives to Joinly More alternatives to Nworks Communication category hub