F
licenseNot graded
qualityC
maintenanceProvides read-only access to Dooray collaboration services through REST, CalDAV, and LDAP, enabling queries for projects, tasks, calendar events, and directory information via 18 MCP tools.
-
NAVER WORKS MCP
by QriumJ
Related Servers
Alternatives to NAVER WORKS MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceNAVER WORKS CLI + MCP server. 26 tools for messages, calendar, drive, mail, tasks, and boards. AI agents can manage NAVER WORKS directly.3656 npm25Apache 2.0
- AlicenseNot gradedqualityCmaintenanceProvides calendar, email, meeting transcription and summarization, and weather tools via MCP, enabling users to manage schedules, handle correspondence, capture meeting insights, and check conditions through natural language.MIT
- FlicenseNot gradedqualityCmaintenanceEnables natural language interaction with enterprise tools including file, database, GitHub, Slack, browser, calendar, email, vector search, and Python calculation through OpenAI and MCP Client.-
- AlicenseBqualityCmaintenanceEnables MCP clients such as Claude Code and Claude Desktop to retrieve Naver Search Ads campaigns, ad groups, keywords, ads, extensions, business channels, customer links, and performance metrics through read-only tools.15MIT
- FlicenseNot gradedqualityDmaintenanceEnables querying HR data like recent hires, employee details, departments, and PTO balances through natural language in an MCP client.-
TDQS
C2.9/5.0
Scored across 8 tools
Disambiguation3/5
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.
Naming Consistency3/5
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.
Tool Count4/5
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.
Completeness2/5
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.
Maintenance
ActivitySlowing
ResponsivenessNo issues