cv-mcp
OfficialProvides tooling to resolve Salesforce org IDs to Commvault clients and browse backed-up Salesforce object records from latest snapshots, including filtering records with optional WHERE-clause queries.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
cv-mcp
MCP server for Commvault Command Center. It lets Claude Code, Claude Desktop and other MCP clients query a CommCell (jobs, clients, storage, plans, schedules, users, security posture) through the Command Center REST API, and operate it only when writes are explicitly enabled.
Origin
This repository is a clone of the open-source
Commvault/commvault-mcp-server project on GitHub, which is
published under the Apache 2.0 license and is open to community development. Issues, feature requests and pull
requests for the upstream project go through its GitHub repository. This copy is maintained by the Product
Experience team for lab work and demos; see Credits for what was ported and NOTICE for attribution.
Related MCP server: GatewayMCP
Status
Working against the lab today: project scaffold, async API client with token renewal, token store, the cv-mcp check
CLI, and the first three tool areas (jobs, CommCell, clients) with 17 read tools and 6 write tools gated behind
CV_MCP_ALLOW_WRITES. Storage, plans, schedules and users tools are next, followed by an offline replay mode for demos.
Tools
Area | Read tools | Write tools (flag required) |
CommCell | get_commcell_details, get_sla_status, get_security_posture, get_security_score, get_storage_space_utilization | send_logs_for_commcell |
Jobs | get_jobs_list, get_failed_jobs, get_job_detail, get_job_task_details, get_job_retention, get_job_events | suspend_job, resume_job, resubmit_job, kill_job, send_logs_for_job |
Clients | get_client_list, get_client_id, get_client_group_list, get_client_group_properties, get_subclient_list, get_subclient_properties | run_backup_for_subclient |
Times are epoch seconds and sizes are bytes unless a tool says otherwise. Responses are slimmed for the model;
*_properties tools return the raw CommServe payload.
Feature areas
The upstream project organizes its tools into the categories below. Job, Commcell and Client Management are
implemented in this repository today (see Tools); the remaining areas are on the roadmap in PLAN.md
or are upstream-only integrations.
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 |
Requirements
Python 3.12 and uv
Commvault 11.38 or later for access tokens (the dev lab runs 11.46)
Network access to the Command Center URL
Install
git clone https://pe-ai-l01.eastus2.cloudapp.azure.com:8443/product-experience/cv-mcp.git
cd cv-mcp
uv syncuv sync installs Python 3.12 from .python-version if it is not already present.
Configuration
All settings come from CV_* environment variables. Keep them in a file outside the repo, for example
~/.config/cv-mcp/lab.env with mode 600, and pass it with --env-file. See .env.example.
Variable | Meaning |
| Command Center base URL, e.g. |
| Access token from Profile > Access tokens |
| Matching refresh token; single-use, rotated by the server on renew |
| Optional JSON file where rotated tokens are persisted; seeded from the two variables above |
|
|
| Path to a CA bundle or exported server certificate; takes precedence over |
| Local IP to bind outgoing connections to, e.g. a VPN adapter address |
|
|
|
|
| Request timeout in seconds (default 60) |
Verify the connection
uv run --env-file ~/.config/cv-mcp/lab.env cv-mcp checkCalls v2/whoami and CommServ and prints the user, CommCell name and version.
Run with Claude Code
.mcp.json in this repo registers the server over stdio:
{
"mcpServers": {
"cv-mcp": {
"command": "uv",
"args": ["run", "--env-file", "C:/Users/zwkru/.config/cv-mcp/lab.env", "cv-mcp", "serve"]
}
}
}The --env-file path is absolute and machine-specific. After cloning on another machine, change it to the
location of your own env file before opening the project in Claude Code or the Claude desktop app.
cv-mcp serve --transport http --host 127.0.0.1 --port 8080 exposes Streamable HTTP on /mcp for remote
clients; protocol-level authentication for that mode arrives in phase 4.
Deploy on a Windows lab VM
These steps set up a second copy of the server on a Windows Server 2025 VM that sits on the lab network, for example to develop and test without the VPN. The Claude desktop app is assumed to be installed already.
Install git and uv in PowerShell. Python is not needed separately;
uv syncfetches 3.12.winget install --id Git.Git -e winget install --id astral-sh.uv -eClone and sync as in Install.
Create a new token pair for the VM in Command Center under Profile > Access tokens. Never copy
lab.envfrom another machine: the refresh token is single-use, so two servers sharing one pair invalidate each other on the first renewal.Create
%USERPROFILE%\.config\cv-mcp\lab.envfrom.env.example:CV_SERVER_URLis the Command Center URL, e.g.https://commvaultlab.lab.localthe new
CV_ACCESS_TOKENandCV_REFRESH_TOKENCV_TOKEN_FILE=C:/Users/<you>/.config/cv-mcp/tokens.jsonso renewals survive restartsCV_SSL_VERIFY=false, or export the server certificate and pointCV_CA_BUNDLEat itleave
CV_LOCAL_ADDRESSempty; the VM reaches the lab directly
Restrict the file to your account (the Windows equivalent of
chmod 600):icacls "$env:USERPROFILE\.config\cv-mcp\lab.env" /inheritance:r /grant:r "$env:USERNAME:F"If the VM cannot resolve the Command Center hostname, add it to
C:\Windows\System32\drivers\etc\hosts.Verify the connection:
uv run --env-file $env:USERPROFILE\.config\cv-mcp\lab.env cv-mcp checkEdit the
--env-filepath in.mcp.jsonto match step 4, then open the repo folder as a project in the Claude desktop app. Runget_jobs_listonce to confirm the server is registered and reachable.Run
uv run pytestfor the offline suite anduv run pytest -m livefor the lab smoke tests.
Keep CV_MCP_ALLOW_WRITES=false until you deliberately want the suspend, kill and run-backup tools registered.
Development
uv run pytest # unit tests with respx mocks, no CommServe needed
uv run pytest -m live # smoke tests against the lab (load the env file first)
uv run ruff check . && uv run ruff format --check .Working agreements for Claude Code are in CLAUDE.md; the roadmap and open questions are in PLAN.md.
Credits
The API client, path sanitizer, response shaping and endpoint map are ported from
Commvault/commvault-mcp-server (Apache 2.0). See NOTICE
and LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Remote MCP for 1,500+ APIs. Vault-managed credentials; OAuth or API key. Search, load, and execute.
Unified MCP Server is a remote MCP connector for AI agents and vertical AI products that provides access to 22,000+ authorized SaaS tools across 400+ integrations and 24 categories directly inside LLMs (Claude, GPT, Gemini, Cohere). Tools operate only on explicitly authorized customer connections, enabling agents to safely read and write against live third-party systems.
Related MCP Servers
- AlicenseAqualityFmaintenanceEnables Claude or any MCP client to drive the GitHub Copilot cloud agent via its REST API, allowing it to research, edit, and open pull requests on repositories without manual intervention.11MIT

GatewayMCPofficial
AlicenseCqualityFmaintenanceEnables AI coding and operational assistants to securely access company systems through a single MCP endpoint, with OAuth authentication, scoped resource grants, audit logging, secret isolation, and corporate memory.94Apache 2.0
ZopDev MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to query and, when scoped writes are enabled, manage cloud estate data—inventory, costs, recommendations, schedules, governance, and deployments—across AWS, Azure, and GCP through a hosted remote MCP endpoint.Apache 2.0
magicsword-mcpofficial
AlicenseAqualityBmaintenanceEnables Claude Desktop, Cursor, and other MCP-aware clients to conversationally manage endpoints, query and triage alerts, inspect events, manage policies and intel feeds, mint enrollment tokens, and preview or commit fleet changes.2683 npmApache 2.0