Veeam VSPC MCP — Claude Code MCP server: what it does, how to install
Mirrors Veeam Service Provider Console tenant records into local SQLite. Helps service providers inspect backup health across multiple companies without constant API roundtrips.
Open on GitHubWhat Veeam VSPC MCP does
This MCP server bridges language models with the Veeam Service Provider Console API. It replicates tenant metadata into a local SQLite database, establishing a unified cross-company mirror. The agent queries backup status and catches configuration drift without waiting on remote endpoints.
Under the hood, veeam-mcp coordinates with the companion veeam-cli binary. Do not enable HTTP transport mode. The current build lacks authentication and binds to every network interface, allowing local websites to intercept credentials. Stick strictly to standard input and output (stdio).
Prebuilt binaries run on macOS, Linux, and Windows. Engineers run the tool directly on workstations. No custom scripting is required.
What it helps with
- mirror multi-tenant backup records into local SQLite storage
- identify configuration drift across client organizations
- audit backup statuses without live API latency
- generate cross-company backup summaries for service teams
Example prompts for the agent
- Check overall backup status across all tenants using
veeam-cli. - Identify backup configuration drift across client companies in the local database.
- Find stale backups across all organizations registered in Veeam Service Provider Console.
How to install Veeam VSPC MCP
Install
The MCP registry has no launch command for it: see the repository README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Veeam VSPC MCP
How do I install Veeam VSPC MCP in Claude Code?
Add the repository marketplace with /plugin marketplace add Servosity/msp-skills, then run /plugin install veeam@msp-skills inside Claude Code.
What does Veeam VSPC MCP do?
It synchronizes tenant data from Veeam Service Provider Console into a local SQLite file. This lets AI agents evaluate backup status across multiple clients without repeated API calls.
Why should HTTP transport mode be avoided?
HTTP transport lacks password protection and binds across all local network interfaces in this build. To prevent unauthorized credential access from local browser sessions, run it only via stdio.