Skip to main content
Glama
rubrikinc

Rubrik MCP

Official
by rubrikinc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Rubrik MCP

No user-submitted related servers found.

    Related Servers

    • New Relic MCP Server

      Meet-Bhalodiya
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to New Relic with read-only access to NRQL, logs, metrics, traces, alerts, and more. Offers optional, gated write operations with a dry-run and confirmation workflow.
      32 npm
      Apache 2.0
    • Turbot Guardrails MCP Server by turbot

      Turbot Guardrails MCP Serverofficial

      turbot
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants to Turbot Guardrails for natural language exploration, analysis, and automation of cloud governance.
      11 npm
      4
      Apache 2.0

    • GithubMCP

      Dhananjayrbiraris
      A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to GitHub repositories, pull requests, issues, commits, and code search while enabling repository visibility controls, CI/CD monitoring, sandboxed local filesystem access, and code quality/security analysis.
      13
      1
      MIT
    • Snyk API & Web MCP Server by snyk

      Snyk API & Web MCP Serverofficial

      snyk
      A
      license
      C
      quality
      A
      maintenance
      Connects AI coding assistants to Snyk API & Web for onboarding scan targets, configuring authentication, running DAST scans, and triaging findings through natural language.
      51
      8
      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

    A4.2/5.0

    Scored across 13 tools

    Disambiguation4/5

    The three schema-introspection tools (rsc_search_schema, rsc_describe_type, rsc_describe_operation_full) are closely related but their descriptions clearly delineate search vs. type lookup vs. full operation expansion. The data-fetching tools each target a distinct resource (workloads, events, clusters, SLA domains), and workflow CRUD is unambiguous.

    Naming Consistency5/5

    All tools share a uniform rsc_ prefix followed by a consistent snake_case verb_noun pattern (get_workloads, list_workflows, delete_workflow, search_schema, describe_type, wait_for_job). No mixed conventions or stray casing.

    Tool Count5/5

    13 tools is well within the ideal 3-15 range, with each tool earning its place across introspection, read operations, job polling, and workflow management. No redundancy that would justify trimming.

    Completeness3/5

    Read coverage is solid (workloads, events, clusters, SLAs, help) and raw queries via rsc_execute_operation fill gaps, but mutations are explicitly blocked and there are no built-in write/recovery tools despite descriptions referencing rsc_take_on_demand_snapshot and similar 'built-in tools' that are absent from the surface. This leaves a notable gap for any write/protection workflow.

    Maintenance

    ActivityNo data
    ResponsivenessSlow

    Resources