Log inSubmit server
Nworks logo

Nworks

by yjcho9317

Connects AI clients to NAVER WORKS for messaging, calendars, files, mail, tasks, boards, and organization data.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Nworks

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "yjcho9317-nworks": {
      "command": "npx",
      "args": [
        "-y",
        "nworks"
      ],
      "env": {
        "CLIENT_ID": "YOUR_VALUE_HERE",
        "CLIENT_SECRET": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y nworks

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.

Overview

yjcho9317/nworks MCP server lets MCP-compatible AI clients operate NAVER WORKS from outside the service. It exposes tools for messages, calendars, Drive files, mail, tasks, boards, contacts, and authentication diagnostics through a local CLI-backed server. User OAuth covers most productivity features, while messaging and directory operations use a service account. Reach for it when an agent needs to read or update NAVER WORKS data, after configuring a Developer Console app and the required credentials.

Use cases

  • Send team messages from an AI workflow
  • Create and update NAVER WORKS calendar events
  • Search and summarize mailbox messages
  • Upload or download workplace Drive files
  • Track tasks and read board content

Key features

  • NAVER WORKS messaging and directory tools
  • Calendar event management
  • Drive file transfer and listing
  • Mailbox reading and sending
  • Task and board operations
  • OAuth setup and connection diagnostics

Tools44

What Nworks lets your agent do. Expand a tool for its parameters.

Self-reported~397 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

5/6 checks healthy over the last 79d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 9d ago via OSV.dev · nworks (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars28Stargazers on the source repository.
npm downloads526Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Tools exposed44Callable tools this server registers over MCP.
Directory activity5 viewsConfig copies, upvotes, and views on AllMCPs.

How Nworks works

What yjcho9317/nworks MCP server does

yjcho9317/nworks MCP server connects external AI agents and terminal workflows to NAVER WORKS, also referred to in the project as LINE WORKS. Its tools cover common workplace operations rather than a single narrow resource. Agents can send messages, inspect channel or organization members, manage calendar events, browse and transfer Drive files, read and send mail, maintain tasks, and work with boards and contacts.

The project also includes authentication and troubleshooting tools. An agent can configure credentials, start user login, remove stored credentials, check the active identity, and run a connection diagnosis. This makes the server usable both from an existing CLI login and from an MCP client that needs to guide setup.

How it works

The package runs locally and exposes its MCP interface through the nworks mcp command. MCP clients such as Claude Desktop and Cursor can launch that command as a stdio server. The same package also provides terminal commands for login and direct NAVER WORKS operations, with JSON output available for scripting and agent workflows.

Most calendar, Drive, mail, task, board, and contact operations use NAVER WORKS user OAuth scopes. Messaging and organization or channel member operations use the service-account-based bot API. User login opens a browser flow and can request the supported scopes together. A single successful login makes the available authorized tools usable by the client, subject to the scopes and account permissions granted.

Setup and configuration

Before using yjcho9317/nworks MCP server, create an application in the NAVER WORKS Developer Console. The documented user OAuth flow requires a client ID, client secret, and the redirect URL http://localhost:9876/callback registered in that console. Bot messaging may also require administrator approval.

Install the npm package globally or run it directly with npx. After installation, authenticate with nworks login --user for user features, or use the bot login flow for messaging. The MCP configuration starts nworks with the mcp argument. Credentials can also be prepared through nworks_setup and nworks_login_user; the client secret and private-key path must be supplied through the MCP environment configuration or the system environment when required.

Tools and capabilities

  • Send messages to users or channels and list channel members.
  • List organization members through the directory tools.
  • List, create, update, and delete calendar events.
  • List, upload, and download Drive files and folders.
  • Send mail, list a mailbox, read messages, and download attachments.
  • List, create, update, complete, and delete tasks.
  • List boards and work with board posts where the corresponding tools and scopes are available.
  • List, read, create, update, delete, and tag contacts.
  • Check authentication state and diagnose API connectivity.

Limitations and notes

yjcho9317/nworks MCP server is unofficial and community-maintained, and the repository states that it is not affiliated with LINE WORKS or NAVER WORKS. Access depends on a correctly configured Developer Console application, OAuth scopes, service-account permissions, and any required administrator approval. File and attachment downloads larger than 5 MB are saved locally according to the project documentation. The material identifies Claude Desktop and Cursor as compatible clients, while other MCP-compatible clients may require their own stdio configuration.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Nworks

Run `npx nworks` directly or install it globally with `npm install -g nworks`.

Yes.

Create a NAVER WORKS Developer Console app, configure its client credentials and redirect URL, then run `nworks login --user` or use the MCP setup and user-login tools.

It provides tools for NAVER WORKS messages, calendars, Drive, mail, tasks, boards, contacts, directory data, authentication, and connection diagnostics.

Related MCP servers

All in Workplace & Productivity All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNworks AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/yjcho9317-nworks?style=directory)](https://allmcps.com/mcp/yjcho9317-nworks)
HTML Embed
<a href="https://allmcps.com/mcp/yjcho9317-nworks"><img src="https://allmcps.com/api/badge/yjcho9317-nworks?style=directory" alt="Nworks on AllMCPs" /></a>