Is Nworks safe to use?

Nworks has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.

How do I install Nworks?

Nworks can be installed by cloning its GitHub repository and following the setup instructions in the README.

What AI clients work with Nworks?

Nworks is compatible with Claude Desktop, Cursor, Claude Code, and most MCP clients that support stdio transport. It uses stdio transport.

Is Nworks actively maintained?

Nworks is actively maintained — last commit was 14 days ago. It has 8 GitHub stars.

Nworks

Full-featured MCP server and CLI for LINE WORKS (NAVER WORKS) — 26 tools covering messages, calendar, drive, mail, tasks, and boards. Automate with AI agents or scripts.

ActiveNot tested

AI / ML

★ 8GitHub

28DNo CVEsactiveApache-2.0

Quick Install

{
  "mcpServers": {
    "nworks": {
      "command": "<see-readme>",
      "args": []
    }
  }
}

Setup guide

No install config available. Check the server's README for setup instructions.

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/nworks)](https://mcppedia.org/s/nworks)

Should you use this server?

Featured in awesome-mcp-servers

✓

Is it safe?

No package registry to scan.

No authentication — any process on your machine can connect.

Apache-2.0. View license →

✓

Is it maintained?

Last commit 14 days ago. 8 stars.

Will it work with my client?

Transport: stdio. Works with Claude Desktop, Cursor, Claude Code, and most MCP clients.

README

nworks

Featured in awesome-mcp-servers

🇺🇸 English | 🇰🇷 한국어 | 🇯🇵 日本語

Full-featured MCP server for LINE WORKS (NAVER WORKS). CLI + MCP server — 26 tools covering messages, calendar, drive, mail, tasks, and boards.

Quickstart

npm install -g nworks
nworks login --user
nworks calendar list

AI Agents Actually Use It Like This

User: Show me today's schedule

Claude → nworks_calendar_list
  → 3 events: Standup (10:00), Lunch meeting (12:00), Code review (15:00)

User: Send a deploy complete message to the team channel

Claude → nworks_message_send
  { "channel": "C001", "text": "v1.2.0 deploy complete" }
  → Message sent

User: Check my unread emails and summarize them

Claude → nworks_mail_list (unread)
  → 3 unread emails
Claude → nworks_mail_read (each)
  → "3 unread: 1) Deploy approval from CTO, 2) Meeting invite for Friday, 3) Weekly report reminder"

Install

npx nworks             # Run directly
npm install -g nworks  # Global install

Login

# User OAuth (calendar, drive, mail, tasks, boards)
nworks login --user --scope "calendar calendar.read file file.read mail mail.read task task.read board board.read user.read"

# Bot messaging (Service Account)
nworks login

# Check auth status
nworks whoami

# Logout
nworks logout

nworks login --user only requires CLIENT_ID + CLIENT_SECRET. Values already set via environment variables or existing config won't be asked again.

Developer Console: To use User OAuth, register http://localhost:9876/callback as a Redirect URL in the Developer Console.

AI Agent Integration (MCP Server)

Works with Claude Desktop, Cursor, and other MCP-compatible clients.

Setup

nworks login --user --scope "calendar calendar.read file file.read mail mail.read task task.read board board.read user.read"

Then add to your MCP config (~/.config/claude/claude_desktop_config.json):

{
  "mcpServers": {
    "nworks": {
      "command": "nworks",
      "args": ["mcp"]
    }
  }
}

One login enables all 26 tools. No extra env setup needed.

Without CLI login, an AI agent can call nworks_setup → nworks_login_user to authenticate via browser directly. Client Secret and Private Key path must be pre-configured via MCP config env field or system environment variables.

MCP Tools (26)

Tool	Description	Auth
Setup / Auth
`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
`nworks_message_send`	Send message to user/channel	Service Account
`nworks_message_members`	List channel members	Service Account
`nworks_directory_members`	List organization members	Service Account
Calendar
`nworks_calendar_list`	List calendar events	User OAuth (calendar.read)
`nworks_calendar_create`	Create calendar event	User OAuth (calendar + calendar.read)
`nworks_calendar_update`	Update calendar event	User OAuth (calendar + calendar.read)
`nworks_calendar_delete`	Delete calendar event	User OAuth (

... View full README on GitHub

Test This Server

No automated test available for this server. Check the GitHub README for setup instructions.

Score Breakdown

MCPpedia Score

Click each category to see evidence

28D

Last scored 8h ago

How we score →

Security

5/30

No known vulnerabilities.

○

Known CVEs — No package registry to scan

○

Tool safety — No tools to analyze

○

Tool poisoning — No tools to analyze

○

Injection vectors — No tools to analyze

○

Tool stability — First scan — baseline recorded

○

Dependency health — No package to analyze

✓

License — License: Apache-2.0

○

Authentication — No authentication required

○

Repository — active repo

CVEs checked daily via OSV.dev. Score algorithm is open source.

Reviews

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is Nworks safe to use?: Nworks has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.
How do I install Nworks?: Nworks can be installed by cloning its GitHub repository and following the setup instructions in the README.
What AI clients work with Nworks?: Nworks is compatible with Claude Desktop, Cursor, Claude Code, and most MCP clients that support stdio transport. It uses stdio transport.
Is Nworks actively maintained?: Nworks is actively maintained — last commit was 14 days ago. It has 8 GitHub stars.

Similar servers

View all →

Sequential Thinking MCP Server

Official

No CVEs98A

Dynamic problem-solving through sequential thought chains

1 toolsstdio83.8k111.0k/wk1d ago

XcodeBuildMCP

Official

No CVEs97A

A Model Context Protocol (MCP) server and CLI that provides tools for agent use when working on iOS and macOS projects.

2 toolsremote5.2k46.6k/wk1d ago

Python Sdk

Official

No CVEs95A

The official Python SDK for Model Context Protocol servers and clients

1 toolsremote22.6k156.5k/wk21h ago

Gemini Cli

No CVEs95A

An open-source AI agent that brings the power of Gemini directly into your terminal.

8 toolsremote101.3k814.6k/wk12h ago

MCP Security Weekly

Get CVE alerts and security updates for Nworks and similar servers.

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

nworks

Featured in awesome-mcp-servers

🇺🇸 English | 🇰🇷 한국어 | 🇯🇵 日本語

Full-featured MCP server for LINE WORKS (NAVER WORKS). CLI + MCP server — 26 tools covering messages, calendar, drive, mail, tasks, and boards.

Quickstart

npm install -g nworks
nworks login --user
nworks calendar list

AI Agents Actually Use It Like This

User: Show me today's schedule

Claude → nworks_calendar_list
  → 3 events: Standup (10:00), Lunch meeting (12:00), Code review (15:00)

User: Send a deploy complete message to the team channel

Claude → nworks_message_send
  { "channel": "C001", "text": "v1.2.0 deploy complete" }
  → Message sent

User: Check my unread emails and summarize them

Claude → nworks_mail_list (unread)
  → 3 unread emails
Claude → nworks_mail_read (each)
  → "3 unread: 1) Deploy approval from CTO, 2) Meeting invite for Friday, 3) Weekly report reminder"

Install

npx nworks             # Run directly
npm install -g nworks  # Global install

Login

# User OAuth (calendar, drive, mail, tasks, boards)
nworks login --user --scope "calendar calendar.read file file.read mail mail.read task task.read board board.read user.read"

# Bot messaging (Service Account)
nworks login

# Check auth status
nworks whoami

# Logout
nworks logout

nworks login --user only requires CLIENT_ID + CLIENT_SECRET. Values already set via environment variables or existing config won't be asked again.

Developer Console: To use User OAuth, register http://localhost:9876/callback as a Redirect URL in the Developer Console.

AI Agent Integration (MCP Server)

Works with Claude Desktop, Cursor, and other MCP-compatible clients.

Setup

nworks login --user --scope "calendar calendar.read file file.read mail mail.read task task.read board board.read user.read"

Then add to your MCP config (~/.config/claude/claude_desktop_config.json):

{
  "mcpServers": {
    "nworks": {
      "command": "nworks",
      "args": ["mcp"]
    }
  }
}

One login enables all 26 tools. No extra env setup needed.

Without CLI login, an AI agent can call nworks_setup → nworks_login_user to authenticate via browser directly. Client Secret and Private Key path must be pre-configured via MCP config env field or system environment variables.

MCP Tools (26)

Tool	Description	Auth
Setup / Auth
`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
`nworks_message_send`	Send message to user/channel	Service Account
`nworks_message_members`	List channel members	Service Account
`nworks_directory_members`	List organization members	Service Account
Calendar
`nworks_calendar_list`	List calendar events	User OAuth (calendar.read)
`nworks_calendar_create`	Create calendar event	User OAuth (calendar + calendar.read)
`nworks_calendar_update`	Update calendar event	User OAuth (calendar + calendar.read)
`nworks_calendar_delete`	Delete calendar event	User OAuth (

... View full README on GitHub