Skip to main content
Glama
veeemlab

Datto BCDR MCP Server

by veeemlab

Related Servers

Alternatives to Datto BCDR MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server that allows AI assistants to query and monitor KVM Fleet devices, audit logs, and console sessions through the official REST API.
      5
      12 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude to check current uptime status, inspect monitors and incidents, trigger fresh checks, and retrieve status summaries from a self-hosted monitoring service.
      6 npm
      2
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only Proxmox cluster oversight and configuration compliance checks through MCP, covering health, inventory, storage, backups, snapshots, and updates.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables operators and MCP clients to perform read-only, multi-cluster Kubernetes diagnostics by correlating deployment inventory, approved Prometheus metrics, firing alerts, and reusable troubleshooting skills without executing cluster commands or modifying workloads. It exposes tools, resources, and prompts for deployment health checks, metric queries, alert inspection, and skill discovery.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query Zabbix monitoring data through MCP, including host briefs and problem reports, with read-only access and whitelist controls.
      -

    TDQS

    A3.9/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct scopes, but get-backup-health-summary, get-client-overview, get-screenshot-failures, and list-device-assets overlap around backup health and screenshot verification. The descriptions clarify fleet-wide problems vs client rollup vs per-device asset status, so confusion is limited but not impossible.

    Naming Consistency5/5

    All tool names use snake_case and consistently start with get, list, or find followed by a resource/action phrase. There are no mixed conventions such as camelCase or vague standalone verbs.

    Tool Count5/5

    Ten tools is well-scoped for a BCDR monitoring server, covering devices, assets, alerts, restores, health summaries, screenshots, and client overviews. Each tool appears to earn its place without obvious redundancy.

    Completeness4/5

    The read-only monitoring surface is strong, with device, asset, alert, restore, health, and screenshot views. Minor gaps exist for operational follow-up, such as alert acknowledgement/resolution, restore start/cancel, alert detail, and a client-list tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues