NAVER WORKS MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | Host interface for HTTP transport. | 127.0.0.1 |
| MCP_PORT | No | Port for HTTP transport. | 8787 |
| MCP_TRANSPORT | No | Transport mode: 'stdio' (default) or 'http'. | stdio |
| NAVER_WORKS_MOCK | No | Set to 'true' to use mock data instead of real NAVER WORKS API. Required when no access token is provided. | false |
| MCP_ALLOWED_HOSTS | No | Comma-separated list of allowed Host headers for HTTP transport. | |
| MCP_SHARED_SECRET | No | Shared secret for securing HTTP MCP endpoint (min 32 characters). Required for remote HTTP. | |
| NAVER_WORKS_SCOPES | No | Comma-separated list of required scopes, e.g., 'calendar.read,contact.read,directory.read,user.profile.read'. | |
| NAVER_WORKS_USER_ID | No | The userId of the NAVER WORKS user whose data will be queried. | |
| NAVER_WORKS_API_BASE | No | Base URL for NAVER WORKS API. | https://www.worksapis.com/v1.0 |
| NAVER_WORKS_AUTH_MODE | No | Authentication mode. Only 'user_oauth' is supported. | user_oauth |
| NAVER_WORKS_ACCESS_TOKEN | No | OAuth access token for NAVER WORKS API. Required when NAVER_WORKS_MOCK is not 'true'. | |
| NAVER_WORKS_ENFORCE_SCOPES | No | Whether to enforce required scopes. Set to 'true' or 'false'. | true |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| works_healthA | 서버 버전, 무상태 MCP 전송, 인증 모드, Scope 정책을 비밀값 없이 확인합니다. |
| works_calendar_default_propertiesC | 구성원의 기본 캘린더 속성을 조회합니다. 일정 설명·참석자 등 원문은 반환하지 않습니다. |
| works_calendar_personals_listC | 사용자가 접근 가능한 캘린더의 개인 속성을 커서 기반으로 조회합니다. |
| works_calendar_default_events_listB | 최대 31일 범위의 기본 캘린더 일정을 읽기 전용으로 조회합니다. 설명·참석자·외부 지시는 제거합니다. |
| works_calendar_events_listC | calendarId가 명시된 캘린더의 일정을 최대 31일 범위로 조회합니다. |
| works_contact_search_minimalB | 연락처를 검색하고 이메일·전화번호는 마스킹된 최소 필드만 반환합니다. memo·주소·커스텀 속성은 제외합니다. |
| works_directory_users_listC | 구성원 목록을 커서 기반으로 조회하고 개인 이메일·전화·생년월일 등 민감 필드는 반환하지 않습니다. |
| works_directory_user_profile_getB | 이미 알고 있는 userId의 최소 프로필을 조회합니다. Service Account의 userId=me는 차단합니다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
The tools are mostly distinct by domain (health, directory, calendar, contact), but there are two calendar event listing tools (works_calendar_default_events_list and works_calendar_events_list) that overlap significantly—both list events, differing only in whether a calendarId is specified. Similarly, directory tools for user profile vs user list are distinct enough, but the event tool overlap creates some misselection risk.
The tools follow a consistent works_<domain>_<resource>_<action> pattern (e.g., works_calendar_events_list, works_directory_users_list). However, the verbs are inconsistent: some use action suffixes like 'get', 'list', 'search', 'properties', but the server name prefix 'works_' is consistently applied and the overall structure is predictable.
8 tools is a reasonable count for a Naver Works integration server covering health, directory, calendar, and contacts. Each tool earns its place for core workflows, though the surface is slightly narrow for the breadth of domains it touches.
The server covers health checks, directory lookups, calendar event reading, and contact search, but all operations are read-only. There are no create/update/delete operations for any resource, meaning agents can only query data and cannot perform any lifecycle management. Calendar event creation, contact management, and user administration are all absent, leaving notable gaps for a 'works integration' server.