# Rubrik Security Cloud [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/rubrikinc/rubrik-mcp  
**GitHub Stars:** 2  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/rubrik-security-cloud

## Description
Connect AI assistants to the Rubrik Security Cloud GraphQL API to discover, query, and automate.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `uvx` (confidence: high):

```json
"mcpServers": {
  "rubrik-security-cloud": {
    "command": "uvx",
    "args": ["rubrik-mcp"],
    "env": {
      "RSC_SERVICE_ACCOUNT_FILE": ""
    }
  }
}
```

**Requires environment variables:** `RSC_SERVICE_ACCOUNT_FILE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What the Rubrik Security Cloud MCP server does

The Rubrik Security Cloud MCP server gives an AI assistant access to the Rubrik Security Cloud GraphQL API through MCP. It is intended for Rubrik administrators and teams building automation around RSC, and runs locally on a workstation or agent host alongside the client.

Its discovery layer contains a prebuilt index of the RSC GraphQL API. An agent can search operations, inspect complete argument signatures, and examine GraphQL input and return types. Discovery does not require RSC credentials and works offline, making it suitable for API evaluation, integration prototyping, and generating code before access to a production environment is available.

With a configured service account, the server can perform read operations against an RSC environment. Available data includes workload protection and compliance details, backup history, recent events, cluster status, SLA Domain settings, and support content. It also includes tools for selected operational actions and workflow management.

## How it works

The server communicates with an MCP client over standard input/output. Clients launch it with the `rubrik-mcp` command, commonly through `uvx`, or through an installed Python package. The assistant uses discovery tools to identify the appropriate GraphQL operation and its schema, then calls execution tools when credentials are available.

Raw GraphQL execution is read-only. For unsupported mutations, the server returns the attempted mutation so the assistant can produce runnable code rather than execute it directly. Three write operations have dedicated tools: taking an on-demand snapshot, onboarding a host, and assigning an SLA. These tools remain hidden unless `writes_enabled` is set to `true` in the gating policy.

A completed multi-step interaction can be saved as a named workflow. Workflow definitions are stored as editable JSON files, allowing teams to review, version, and share them. Saved workflows become available as tools after the next server restart.

## Setup and configuration

The standard prerequisites are `uv` or Python 3.10 and later with pip. Install with `uvx rubrik-mcp`, or install the `rubrik-mcp` package with pip and configure the resulting executable. The package can be pinned to a release when using `uvx`. An optional hashed requirements file supports install-time dependency hash verification.

Discovery-only use needs no credentials. Execution tools require a Rubrik Security Cloud service account, configured through `RSC_SERVICE_ACCOUNT_FILE` with the path to its JSON file. The same environment setting can be added to Claude Code, Claude Desktop, or another generic stdio MCP client configuration.

## Tools and capabilities

Discovery tools include `rsc_search_schema`, `rsc_describe_operation_full`, and `rsc_describe_type`. Credentialed tools include `rsc_execute_operation`, `rsc_get_workloads`, `rsc_get_events`, `rsc_get_clusters`, `rsc_get_sla_domains`, and `rsc_search_help`.

Operational tools cover `rsc_take_on_demand_snapshot`, `rsc_wait_for_job`, `rsc_onboard_host`, and `rsc_assign_sla`. Workflow tools save, list, and delete reusable flows. Snapshot execution returns a job ID, which can be checked with the job polling tool.

## Limitations and notes

The Rubrik Security Cloud MCP server does not make arbitrary GraphQL mutations directly through raw execution; unsupported writes produce code for the assistant to run separately. Dedicated write tools can change the Rubrik environment, so they are disabled by default. Enabling them allows the model to decide when they are called, and the documentation recommends a least-privilege, read-only service account as the durable permission boundary.

The server’s discovery features function without an RSC connection, but live data and execution require a service account. Destructive operations should also use Quorum Authorization according to the project guidance.

_Full upstream README: https://allmcps.com/mcp/rubrik-security-cloud/readme_