Skip to main content
Glama

Related Servers

Alternatives to vcf-orchestrator-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables Claude to read and control Veeam Backup & Replication infrastructure through natural language, supporting full operator capabilities like starting/stopping jobs, creating backups, and monitoring threat detection via the VBR REST API.
      34
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables Claude Desktop to interact with enterprise REST APIs such as Jira, Zoho CRM, Salesforce, SharePoint, Procore, HxGN EAM, and Primavera P6 using OpenAPI/Swagger definitions, with support for various authentication workflows.
      12
      14 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to discover and call any REST API from an OpenAPI/Swagger spec or Postman collection at runtime, with authentication, workflows, and prebuilt registry support.
      13 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude.ai and Claude Desktop to securely connect to self-hosted OpenClaw AI assistants via OAuth 2.1, sending chat messages, checking gateway health, and queuing, polling, or cancelling long-running tasks. Supports orchestrating multiple OpenClaw gateway instances (such as prod, staging, and dev) from a single authenticated bridge.
      139 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Connects Claude Code to any ObjectStack deployment, enabling discovery, querying, and updating of objects and records, plus running business actions, all under user permissions and row-level security.
      Apache 2.0

    TDQS

    A3.6/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action targets (find/get/save/run for workflows and actions, executions, API spec). Minor overlap between vro_run_workflow (which waits and returns state) and vro_get_execution, and between vro_run_action and vro_run_script, but descriptions clarify the intended use of each.

    Naming Consistency5/5

    Every tool follows the same vro_<verb>_<noun> snake_case pattern (vro_api_search, vro_find_workflows, vro_save_action, vro_run_execution-style verbs). No mixed conventions or vague verbs, making the set highly predictable.

    Tool Count4/5

    17 tools for a broad platform (workflows, actions, executions, versions, and full REST API access) is reasonable and each tool earns its place. It leans slightly heavy, but the scope (full Orchestrator domain) justifies it.

    Completeness4/5

    Strong lifecycle coverage: find/get/save/run/delete for workflows, find/get/save/run for actions, plus execution inspection, version management, and a raw vro_api_call escape hatch for anything missing. Minor gaps exist (no delete action, no cancel/delete execution tool), workable via the generic API call.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues