dakboard-mcp-server
Related Servers
Alternatives to dakboard-mcp-server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceEnables MCP clients holding a control key to create, update, publish, and unpublish dashboards and their charts, plus read-only access to dashboards, view stats, and audit logs. Published dashboards are viewable through public links in a minimal web UI, where viewers can request tweaks that the agent applies via these tools.1MIT- AlicenseNot gradedqualityBmaintenanceEnables AI agents to compose and edit dashboards through MCP tools, allowing them to manage tabs, widgets, layout, and data bindings via a unified control plane.24MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables interaction with Firewalla network security devices for network monitoring, device management, traffic analysis, and security rule configuration through MCP tools.-
- FlicenseNot gradedqualityDmaintenanceProvides MCP tools for Cisco Meraki Dashboard API, enabling management of networks, configuration templates, and health checks via natural language commands.-
- AlicenseNot gradedqualityAmaintenanceEnables 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
- AlicenseNot gradedqualityBmaintenanceEnables managing NetBird network resources through the NetBird REST API, exposing tools for peers, groups, policies, routes, DNS, users, and related operations via MCP.MIT
TDQS
Scored across 18 tools
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.
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.
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.
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.