What is the key difference between Nworks and Local MCP?

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

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

Nworks operates under a Free / Open Source model (OAuth 2.0). Local MCP operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Nworks lists 33 tools with 4 views and 25 GitHub stars. Local MCP lists 6 tools with 3 views and 52 GitHub stars.

Can I use both Nworks and Local MCP 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

Nworks vs Local MCP

In-depth architectural comparison of the Nworks and Local MCP 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

Nworks

Communication · Local stdio

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

Local MCP

Communication · Remote HTTP/SSE

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

Verdict Summary: Choose Nworks if you need specialized Communication tools running via a local process. Choose Local MCP if your workspace requires Communication integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

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

Choose Local MCP 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: Local MCP access to macOS apps, Native Mail, Calendar, Contacts, Notes, and Messages tools, File, PDF, Office document, and Finder operations.

Feature & Specification Comparison

Specification	Nworks yjcho9317 Communication	Local MCP lanchuske Communication
Summary	NAVER WORKS CLI + MCP server. 26 tools for messages, calendar, drive, mail, tasks, and boards. AI agents can manage NAVER WORKS directly.	Connect Claude, Cursor, Windsurf and other AI agents to macOS native apps: Mail, Calendar, Contacts, Reminders, Notes, iMessage, Finder, Safari, OmniFocus, Microsoft Teams, Outlook, OneDrive, and Office documents. 82 tools. Runs entirely on your Mac — no cloud, no tokens, no API keys.
Category & Scope

Tools & Capabilities Breakdown

Nworks Tools (33)

Setup

nworks_setup

Configure API credentials (Client ID, etc.). Client Secret is set via env

nworks_login_user

User OAuth browser login (all scopes included)

nworks_logout

Delete credentials and tokens

nworks_whoami

Check auth status

nworks_doctor

Diagnose connection (auth, tokens, API health)

Messages

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

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

Local MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "lanchuske-local-mcp": {
      "url": "https://www.local-mcp.com/mcp"
    }
  }
}

Frequently Asked Questions

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

More alternatives to Nworks More alternatives to Local MCP Communication category hub Canonical compare URL