Skip to main content
Glama
jordanburke

dakboard-mcp-server

by jordanburke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to dakboard-mcp-server

No user-submitted related servers found.

    Related Servers

    • Firewalla MCP Server

      drewrad8
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables interaction with Firewalla network security devices for network monitoring, device management, traffic analysis, and security rule configuration through MCP tools.
      -

    • Technitium DNS MCP

      X1pheR
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing and observing Technitium DNS Server through MCP, including read-only or read-write tool surfaces, scoped bearer authentication, audit logging, and confirmation gates for destructive operations.
      MIT

    • Sakura-MCP-Server

      Guyao146
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables secure remote control of Home Assistant and Life Dashboard/DSH via MCP, supporting entity state queries, whitelisted entity/scene control, lifecycle overview reading, DSH workspace summaries, and follow-up sending.
      1
      GNU Lesser General Public v2.1 only

    • ringcentral-mcp

      MSPbotsAI
      A
      license
      A
      quality
      C
      maintenance
      Enables interaction with RingCentral phone system data, including account info, extensions, presence, call queues, contacts, and call logs/recordings, through MCP tools.
      13
      Apache 2.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

    A3.6/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: list/get/update for screens, blocks, devices, and loops, plus metric-specific operations. The visual layout and connection test tools are clearly separate. No two tools appear to do the same thing.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., list_screens, get_block, update_device, create_metric_data_points). The naming is uniform and predictable across all resources.

    Tool Count4/5

    18 tools is slightly above the ideal range but justified by the multiple resource types (screens, blocks, loops, devices, metrics) and auxiliary operations like visualization and connection testing. It is not excessive and each tool has a clear role.

    Completeness2/5

    The surface has significant gaps: there are no create operations for screens, blocks, loops, or devices, and no delete operations for screens, blocks, loops, or devices. Metrics have delete and data-point management but lack a create_metric tool, leaving no way to create a metric initially.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources