Nworks

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.