Skip to main content
Glama

Related Servers

Alternatives to nworks

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      AI-powered MCP server for managing LINE Official Accounts. Send broadcasts, push messages, check analytics, manage rich menus — all through natural language via Claude, ChatGPT, or Cursor. 10 tools included: * Account info, friend count, message quota * Broadcast, push message, multicast * Delivery stats, user profiles, follower list * Rich menu management Supports 95M+ LINE users across Jap
      10
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server that integrates the LINE Messaging API to enable AI agents to send messages and manage LINE Official Accounts.
      12
      1,063 npm
      785
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Self-hosted MCP server that exposes Synology Drive, Spreadsheet, MailPlus, and Calendar as structured tools for AI agents, enabling file, spreadsheet, email, and calendar management via natural language.
      39
      17 npm
      11
      MIT
    • F
      license
      C
      quality
      D
      maintenance
      MCP server that enables AI agents to control all DingTalk features (messaging, calendar, tasks, approvals, etc.) via natural language using the DingTalk Workspace CLI.
      83
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Feishu/Lark API integration, enabling AI agents to send messages, manage groups, create and edit documents and spreadsheets, and search knowledge bases.
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Unofficial MCP server for NAVER WORKS Drive admin tasks, enabling shared-drive governance, permission management, and file operations via service-account delegation.
      16
      MIT

    TDQS

    A4/5.0

    Scored across 36 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action pair (e.g., calendar_list vs calendar_create, mail_send vs mail_list). No two tools have overlapping purposes; even similar-sounding drive vs sharedrive tools are clearly separated by domain and description.

    Naming Consistency5/5

    All tools follow the pattern nworks_<domain>_<action> (e.g., nworks_calendar_list, nworks_mail_read, nworks_task_update). This is perfectly consistent across all 36 tools, with no mixed conventions or vague verbs.

    Tool Count4/5

    36 tools is high, but the server integrates a wide range of NAVER WORKS domains (calendar, mail, drive, task, board, contact, message, directory, auth). Each tool serves a clear purpose within its domain, so the count feels justified rather than bloated, though it borders on heavy.

    Completeness4/5

    CRUD coverage is solid for most domains: calendar, tasks, contacts all have list/create/update/delete; mail has send/list/read/download; drive has list/upload/download; boards have list/posts/read/create. Minor gaps exist (e.g., no mail delete, board update/delete, drive delete), but these are non-core and agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow