Commvault

You can integrate Commvault environments with the MCP Server to give AI agents secure access to job details, commcell metrics, client and storage information, user permissions, plan configurations, and backup schedules. This MCP Server lets you monitor, manage, and automate key Commvault tasks from a unified interface.

How to use

You will connect an MCP client to the Commvault MCP Server to access data and control actions such as viewing job details, suspending or resuming jobs, and checking storage usage. Use the provided MCP connection configurations to add remote servers or run a local MCP instance. Once connected, your AI agents can request job, commcell, client, storage, user, plan, and schedule information and perform actions according to your configured permissions.

Typical usage patterns include: 1) retrieving real-time job status and history, 2) managing backup schedules and plan configurations, 3) monitoring storage pools and utilization, 4) listing users and security associations, and 5) backing up DocuSign envelopes to an S3 vault if you enable DocuSign tooling.

How to install

# Prerequisites
python --version 2>/dev/null || echo "Python 3.11+ is required"
uv --version 2>/dev/null || echo "uv (uvx) is required for dependency management and running the server"

# 1) Clone the MCP Server repository
git clone https://github.com/Commvault/commvault-mcp-server.git
cd commvault-mcp-server

# 2) Run the setup script to configure options
uv run setup.py

# 3) Start the MCP Server
uv run -m src.server

Additional configuration and notes

The server supports two authentication methods: OAuth Authentication (for supported CommServe versions) and traditional token-based authentication. OAuth requires configuring a discovery endpoint, client ID/secret, scopes, and a base URL. For token-based authentication, you provide an access token, a refresh token, and a secret used in the Authorization header for tool requests. Secure storage is required for token-based credentials, using a platform-specific keyring backend.

When deploying in production, use a reverse proxy with TLS/HTTPS and secure headers. Bind the MCP Server to localhost (127.0.0.1) to prevent direct public access. For localhost setup, configure MCP_HOST in your environment and use a domain with TLS certificates for external access.

DocuSign backup integration allows backing up completed envelopes to a Commvault S3 vault. Enable this feature with the environment variable ENABLE_DOCUSIGN_TOOLS=true, provide DocuSign integration credentials, and place the DocuSign configuration files under a config/ directory as shown in the example sections.

Configuring clients and local/server connections

You can configure both remote HTTP connections and local stdio connections. Remote connections are defined with a URL; local connections specify the exact Python command to run the MCP server locally.

Available tools

Job Management

View, monitor, and control backup jobs including suspending, resuming, resubmitting, and killing jobs; monitor job status and performance.

Commcell Management

Retrieve SLA status and compliance, view security posture, access storage utilization metrics, and gather commcell details and counts.

Client Management

Access client groups and information, manage subclients and client properties, and view client associations.

Storage Management

View storage policies and configurations, access storage pools, and monitor storage resources.

User Management

List users, user groups, and security associations.

Plan Management

View plan configurations and details, access plan components and settings.

Schedule Management

Access backup schedules, view configurations, and monitor performance.

DocuSign Integration

Set up DocuSign Vault and Workflow, backup envelopes to Commvault S3 vault, and list/restore DocuSign envelope backups.