Skip to main content
Glama
sdadaniel

dooray-mcp-js

by sdadaniel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to dooray-mcp-js

No user-submitted related servers found.

    Related Servers

    • worksmobile-mcp

      z0nam
      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
    • dartpoint-mcp by dartpointai

      dartpoint-mcpofficial

      dartpointai
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP Server for public disclosure information of Korean companies, powered by the dartpoint.ai API.
      3
      Apache 2.0

    • postiz-mcp

      antoniolg
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for managing social media posts across multiple platforms using the Postiz API. Supports creating, updating, deleting posts, and generating videos.
      38 npm
      2
      MIT

    • gdoc-comments

      gxozer
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for reading/editing Google Docs content and managing comments, including listing, creating, replying, resolving, and reopening comments via the Docs API and Drive API.
      GPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have clear resource-action boundaries (e.g., account member lookup vs. calendar events), but a few pairs like dooray_post_logs and dooray_post_log could confuse agents without careful reading. The plural/singular distinction helps, and the 'os' tool is clearly separate.

    Naming Consistency4/5

    The naming is mostly consistent with a dooray_<domain>_<resource> pattern for queries and dooray_<domain>_<resource>_<verb> for actions. However, 'dooray_messenger' (a send action without a verb) and the standalone 'os' tool break the pattern, along with redundant 'dooray_calendar_calendars'.

    Tool Count4/5

    15 tools is within a reasonable range for a multi-domain integration (account, messenger, calendar, posts, logs, files). The inclusion of an unrelated 'os' tool slightly detracts from the overall scope, but the count is not excessive.

    Completeness2/5

    Critical CRUD operations are missing across resources: no way to create or update posts, no update/delete for calendar events, no read for messenger, and no upload for files. While some actions exist (create calendar event, add comment, download file), the surface is incomplete for full lifecycle management, leading to dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources