A Model Context Protocol (MCP) server for interacting with Commvault software.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"Commvault": {
"args": [
"mcp-remote",
"HOST:PORT/mcp",
"--header",
"Authorization: <secret stored in server keyring>"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
A Model Context Protocol (MCP) server for seamless integration with Commvault environments. This server enables AI agents to securely access and manage job details, commcell metrics, client and storage information, user permissions, plan configurations, and backup schedules.
This server supports HTTP transport. Be the first to test it — help the community know if it works.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in devops / data
Manage Supabase projects — databases, auth, storage, and edge functions
MCP server for using the GitLab API
Query and manage PostgreSQL databases directly from AI assistants
Zero-dependency, token-efficient database MCP server for Postgres, MySQL, SQL Server, MariaDB, SQLite.
MCP Security Weekly
Get CVE alerts and security updates for Commvault Mcp Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
A Model Context Protocol (MCP) server for seamless integration with Commvault environments. This server enables AI agents to securely access and manage job details, commcell metrics, client and storage information, user permissions, plan configurations, and backup schedules.
The Commvault MCP Server enables seamless integration with Commvault environments, offering the following:
| Category | Features |
|---|---|
| Job Management | • View job details and history • Control jobs (suspend, resume, resubmit, kill) • Monitor job status and performance |
| Commcell Management | • Retrieve SLA status and compliance • View security posture and scores • Access storage space utilization metrics • Get commcell details and entity counts |
| Client Management | • Access client groups and client information • Manage subclients and client properties • View client associations |
| Storage Management | • View storage policies and configurations • Access storage pool information • Monitor storage resources |
| User Management | • List users and user groups • Access security associations |
| Plan Management | • View plan configurations and details • Access plan components and settings |
| Schedule Management | • Access backup schedules • View schedule configurations • Monitor schedule performance |
| DocuSign Integration | • Setup Docusign Vault & Workflow • Backup envelopes to Commvault S3 vault • List & restore DocuSign envelope backups |
| Salesforce Integration | • Resolve Salesforce org ID to Commvault client • Browse backed-up Salesforce object records from latest snapshot • Filter records with optional WHERE-clause queries • Paginated access to large record sets |
Before running the Commvault MCP Server, ensure the following requirements are met:
uv package manager (used for dependency management and running the server)The Commvault MCP Server supports two authentication methods:
Note: OAuth authentication is only supported for Commvault environments running SP42 CU 27 and above. OAuth must be properly configured in the CommServe before using this option.
When using OAuth authentication, you'll need:
Important: The redirect URI must be set to
OAUTH_BASE_URL/auth/callbackin your OAuth provider's app/client configuration.
The following values will be collected during the setup process:
Commvault Access Credentials:
You need a valid access_token and refresh_token to authenticate with the Commvault API.
Learn how to generate these tokens here: Creating an Access Token – Commvault Docs
Secret Key:
This secret must be included by the MCP Client in the Authorization header of all tool requests.
It acts as a security layer for tool access in remote server. You can set your own.
Important: When using traditional token-based authentication, the setup script requires a secure, OS-native keyrin