CLI and MCP server for NAVER WORKS / LINE WORKS — control messages, calendar, drive, mail, tasks, and boards from terminal or AI agents (Claude
Most planning and project tracking work still happens through a UI a human drives. Nworks MCP server moves it into the conversation instead. CLI and MCP server for NAVER WORKS / LINE WORKS — control messages, calendar, drive, mail, tasks, and boards from terminal or AI agents (Claude, Cursor).
nworks on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The server publishes 14 tools. What each one is for:
nworks_setup — Configure API credentials (Client ID, etc.). Client Secret is set via envnworks_login_user — User OAuth browser login (all scopes included)nworks_logout — Delete credentials and tokensnworks_whoami — Check auth statusnworks_doctor — Diagnose connection (auth, tokens, API health)Messages — The Messages tool exposed by this servernworks_message_send — Send message to user/channelnworks_message_members — List channel membersnworks_directory_members — List organization membersCalendar — The Calendar tool exposed by this servernworks_calendar_list — List calendar eventsnworks_calendar_create — Create calendar eventConfiguration is passed through the environment: NWORKS_CLIENT_SECRET, NWORKS_PRIVATE_KEY_PATH, CLIENT_ID, CLIENT_SECRET, CHANNEL_ID, NWORKS_CLIENT_ID, NWORKS_BOT_ID, NWORKS_DOMAIN_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Nworks's toolset — nworks_setup, nworks_login_user, nworks_logout and 11 more — is a fair guide to whether it matches your workflow. It is maintained by yjcho9317; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| 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 | The Messages tool exposed by this server. |
| nworks_message_send | Send message to user/channel |
| nworks_message_members | List channel members |
| nworks_directory_members | List organization members |
| Calendar | The Calendar tool exposed by this server. |
| nworks_calendar_list | List calendar events |
| nworks_calendar_create | Create calendar event |
| nworks_calendar_update | Update calendar event |
| nworks_calendar_delete | Delete calendar event |
{
"mcpServers": {
"nworks": {
"command": "npx",
"args": ["-y", "nworks"],
"env": {
"NWORKS_CLIENT_SECRET": "your-value",
"NWORKS_PRIVATE_KEY_PATH": "your-value",
"CLIENT_ID": "your-value",
"CLIENT_SECRET": "your-value",
"CHANNEL_ID": "your-value",
"NWORKS_CLIENT_ID": "your-value",
"NWORKS_BOT_ID": "your-value",
"NWORKS_DOMAIN_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| NWORKS_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| NWORKS_PRIVATE_KEY_PATH | Credential the server authenticates with. | Yes |
| CLIENT_ID | Configuration value read at startup. | Optional |
| CLIENT_SECRET | Credential the server authenticates with. | Yes |
| CHANNEL_ID | Configuration value read at startup. | Optional |
| NWORKS_CLIENT_ID | Configuration value read at startup. | Optional |
| NWORKS_BOT_ID | Configuration value read at startup. | Optional |
| NWORKS_DOMAIN_ID | Configuration value read at startup. | Optional |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.