nworks is a full-featured MCP server for LINE WORKS (NAVER WORKS) providing 26 tools across messaging, calendar, drive, mail, tasks, and boards β accessible via CLI and AI agent interfaces (Claude Desktop, Cursor, etc.).
Setup & Authentication
Configure API credentials (Client ID/Secret, Service Account, Bot ID)
Perform User OAuth browser login, check auth status, logout, and diagnose connection issues
Messages (Service Account)
Send text, button, or list messages to users or channels
List channel members and retrieve all organization directory members
Calendar (User OAuth)
List, create, update, and delete calendar events with attendees, location, descriptions, and notifications
Drive (User OAuth)
List files/folders, upload files (base64 or local path), and download files (returns content or saves locally)
Mail (User OAuth)
Send emails with CC/BCC support, list inbox (with unread filtering), and read full email details
Tasks (User OAuth)
List (filter by status), create (with due dates and assignees), update (including completion status), and delete tasks
Boards (User OAuth)
List boards, view and read board posts, and create new posts with notification and comment options
Supports environment variable configuration for CI/CD and automation.
Provides a suite of tools for interacting with NAVER WORKS, enabling automation of messages, calendar management, file operations in Drive, email communication, task tracking, and board interactions.
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 listAI 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 installLogin
# 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 --useronly 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/callbackas a Redirect URL in the Developer Console.
AI Agent Integration (MCP Server)
Works with Claude Desktop, Cursor, and other MCP-compatible clients.
Setup
Login first:
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_userto authenticate via browser directly. Client Secret and Private Key path must be pre-configured via MCP configenvfield or system environment variables.
MCP Tools (26)
Tool | Description | Auth |
Setup / Auth | ||
| Configure API credentials (Client ID, etc.). Client Secret is set via env | β |
| User OAuth browser login (all scopes included) | β |
| Delete credentials and tokens | β |
| Check auth status | β |
| Diagnose connection (auth, tokens, API health) | β |
Messages | ||
| Send message to user/channel | Service Account |
| List channel members | Service Account |
| List organization members | Service Account |
Calendar | ||
| List calendar events | User OAuth (calendar.read) |
| Create calendar event | User OAuth (calendar + calendar.read) |
| Update calendar event | User OAuth (calendar + calendar.read) |
| Delete calendar event | User OAuth (calendar + calendar.read) |
Drive | ||
| List drive files/folders | User OAuth (file.read) |
| Upload file to drive | User OAuth (file) |
| Download file (saves locally if >5MB) | User OAuth (file.read) |
| Send mail | User OAuth (mail) |
| List mailbox | User OAuth (mail.read) |
| Read mail detail | User OAuth (mail.read) |
Tasks | ||
| List tasks | User OAuth (task.read) |
| Create task | User OAuth (task + user.read) |
| Update/complete task | User OAuth (task + user.read) |
| Delete task | User OAuth (task + user.read) |
Boards | ||
| List boards | User OAuth (board.read) |
| List board posts | User OAuth (board.read) |
| Read board post detail | User OAuth (board.read) |
| Create board post | User OAuth (board) |
AI Agent Usage Example
User: Schedule a meeting tomorrow at 2pm and notify the team channel
Claude β nworks_calendar_create
{ "summary": "Meeting", "start": "2026-03-15T14:00:00", "end": "2026-03-15T15:00:00" }
β Event created
Claude β nworks_message_send
{ "channel": "C001", "text": "Meeting scheduled tomorrow at 14:00" }
β 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"CLI Usage
All commands support
--jsonfor pipe/script/agent parsing.message send,mail send, anddrive uploadsupport--dry-runfor testing without sending.
Messages (Bot API)
# Send text to user
nworks message send --to <userId> --text "Hello"
# Send text to channel
nworks message send --channel <channelId> --text "Announcement"
# Button message
nworks message send --to <userId> --type button --text "PR review request" \
--actions '[{"type":"message","label":"Approve","postback":"approve"}]'
# List message
nworks message send --to <userId> --type list --text "Today's tasks" \
--elements '[{"title":"Code review","subtitle":"PR #382"}]'
# List channel members
nworks message members --channel <channelId>Directory
nworks directory members # List organization membersCalendar (User OAuth)
# List today's events
nworks calendar list
# Specify date range
nworks calendar list --from "2026-03-14T00:00:00+09:00" --until "2026-03-14T23:59:59+09:00"
# Create event
nworks calendar create --title "Meeting" --start "2026-03-14T14:00+09:00" --end "2026-03-14T15:00+09:00"
# With location/description
nworks calendar create --title "Lunch" --start "2026-03-14T12:00+09:00" --end "2026-03-14T13:00+09:00" \
--location "Conference Room" --description "Quarterly review"
# With attendees + notification
nworks calendar create --title "Team meeting" --start "2026-03-14T10:00+09:00" --end "2026-03-14T11:00+09:00" \
--attendees "user1@example.com,user2@example.com" --notify
# Update event
nworks calendar update --id <eventId> --title "Updated title"
# Delete event
nworks calendar delete --id <eventId>Drive (User OAuth)
# List files/folders
nworks drive list
# Upload file
nworks drive upload --file ./report.pdf
# Upload to specific folder
nworks drive upload --file ./report.pdf --folder <folderId>
# Download file
nworks drive download --file-id <fileId>
# Specify output path/name
nworks drive download --file-id <fileId> --out ./downloads --name report.pdfMail (User OAuth)
# Send mail
nworks mail send --to "user@example.com" --subject "Subject" --body "Body"
# With CC/BCC
nworks mail send --to "user@example.com" --cc "cc@example.com" --subject "Subject" --body "Body"
# List inbox
nworks mail list
# Unread only
nworks mail list --unread
# Read mail detail
nworks mail read --id <mailId>Tasks (User OAuth)
# List tasks
nworks task list
# Incomplete only
nworks task list --status TODO
# Create task
nworks task create --title "Code review" --body "Review PR #382"
# With due date
nworks task create --title "Deploy" --due 2026-03-20
# Mark as done
nworks task update --id <taskId> --status done
# Delete task
nworks task delete --id <taskId>Boards (User OAuth)
# List boards
nworks board list
# List posts
nworks board posts --board <boardId>
# Read post detail
nworks board read --board <boardId> --post <postId>
# Create post
nworks board create --board <boardId> --title "Announcement" --body "Content"
# With notification + disable comments
nworks board create --board <boardId> --title "Notice" --body "Content" --notify --no-commentCI/CD Deploy Notification
# Notify team channel after deployment in GitHub Actions
nworks message send --channel $CHANNEL_ID --text "v${VERSION} deployed"Team Automation Script
# Send daily standup reminder to all members
for userId in $(nworks directory members --json | jq -r '.users[].userId'); do
nworks message send --to "$userId" --text "Standup at 10:00 today"
doneOAuth Scopes
Add the required scopes in the LINE WORKS Developer Console.
Scope | Purpose | Auth | Required For |
| Bot messaging | Service Account |
|
| Bot channel/member read | Service Account |
|
| Calendar write | User OAuth |
|
| Calendar read | User OAuth |
|
| Drive read/write | User OAuth |
|
| Drive read-only | User OAuth |
|
| Mail read/write | User OAuth |
|
| Mail read-only | User OAuth |
|
| Tasks read/write | User OAuth |
|
| Tasks read-only | User OAuth |
|
| User info read | Service Account / User OAuth |
|
| Boards read/write | User OAuth |
|
| Boards read-only | User OAuth |
|
Tip: After changing scopes, reissue your token:
nworks logout && nworks login --user --scope "..."
Environment Variables
Set environment variables to use nworks without nworks login (useful for CI/agents).
# Required
NWORKS_CLIENT_ID=
NWORKS_CLIENT_SECRET=
# Bot messaging only (not needed for User OAuth)
NWORKS_SERVICE_ACCOUNT=
NWORKS_PRIVATE_KEY_PATH=
NWORKS_BOT_ID=
# Optional
NWORKS_DOMAIN_ID=
NWORKS_SCOPE= # default: bot bot.read user.read
NWORKS_VERBOSE=1 # debug loggingMCP Server with Environment Variables
Sensitive values (Client Secret, Private Key path) must be set via MCP config env field. Non-sensitive values like Client ID can be configured by the AI agent through the nworks_setup tool.
{
"mcpServers": {
"nworks": {
"command": "npx",
"args": ["-y", "nworks", "mcp"],
"env": {
"NWORKS_CLIENT_SECRET": "<Client Secret>",
"NWORKS_PRIVATE_KEY_PATH": "<Private Key file absolute path (for Service Account)>"
}
}
}
}License
Apache-2.0