Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Related Servers

Alternatives to vbr-write-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      AI-powered Veeam Backup & Replication operations MCP server with tools for managing jobs, restores, sessions, and repositories, featuring built-in governance, audit logging, and safety controls.
      27
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables MCP clients to manage a self-hosted backup server through its web API — checking status, starting and stopping backups, browsing and restoring files or disk images, archiving and deleting backups, and reading logs, settings, users, and usage statistics. Destructive operations require explicit confirmation, and it runs over stdio or a Bearer-authenticated streamable HTTP transport.
      31
      1
      GPL 3.0
    • A
      license
      C
      quality
      D
      maintenance
      Enables AI agents to control and monitor Veeam Backup & Replication v13 infrastructure through 328 MCP tools using the official REST API. Supports both stdio mode for local clients like Claude Desktop and streamable HTTP mode for remote integration with platforms like Dify.
      100
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes Zerobyte backup platform's REST API as MCP tools, enabling read-only queries on repositories, backups, snapshots, volumes, and system info.
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Lets MCP clients inspect and change FortiOS configuration through the FortiOS REST API — policies, address and service objects, routes, VIPs, DHCP, VPN, users, security profiles, live sessions and logs — across multiple firewalls from one server. All device-changing tools stay disabled until writes are explicitly enabled, keeping the server read-only by default.
      137
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Enables MCP clients to call VCF Automation 9 REST operations as individual tools across 16 services, including deployments, catalog items, blueprints, policies, and IaaS resources. It also supports service-account setup, automatic token refresh, read-only filtering, and selective service loading.
      500
      559 npm
      MIT

    TDQS

    B3.2/5.0

    Scored across 68 tools

    Disambiguation4/5

    Most tools target clearly distinct resource+action pairs (delete_backup vs delete_backup_object vs delete_object, move_backup vs copy_backups vs move_backup_objects_to_job, start/finish Instant Recovery pairs). A few boundaries blur: stop_session vs stop_task vs stop_automation_session, the generic create_object/update_object/delete_object family vs the dedicated create_* tools, and api_write vs any dedicated write tool. Descriptions largely resolve these by explicitly stating scope (api_write is 'for write endpoints no dedicated tool covers').

    Naming Consistency3/5

    All names are snake_case, but verb conventions vary widely (set_, manage_, rescan_, start_, apply_, mark_, clone_, verify_) and a few tools are noun-only or noun-first (api_read, api_write, security_analyzer, high_availability_cluster, describe_endpoint). Patterns are still readable and mostly verb_noun, but not a single predictable scheme across 68 tools.

    Tool Count2/5

    68 tools is far beyond a well-scoped set, driven by exposing granular operations for a very large VBR domain. While many tools are individually justified, the count creates a heavy selection burden, and generic escape hatches (api_write, create_object/update_object) coexist with numerous dedicated variants, which is exactly the strain that pushes this dimension down.

    Completeness4/5

    Coverage is broad: jobs, repositories, protection groups, backup deletion/move/copy, multiple restore types, malware/IoC handling, licensing, settings, security, sessions, HA and config import/export. Minor gaps remain, notably no dedicated vSphere VM full restore (only Cloud Director and Hyper-V restores) and no dedicated job-run tool (only quick backup), but api_write and companion vbr-mcp tools provide workarounds.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues