Bitdefender MCP

Bitdefender + AI - for Claude, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, and any agent that speaks MCP

Unofficial. Community-built Claude Code Skill and MCP server for the Bitdefender

API. Not affiliated with, endorsed by, or sponsored by Bitdefender SRL.

▶ Watch the 30-second demo - demo data is simulated; every command shown exists in the real CLI.

140 GravityZone API methods, plus fleet health, billing and incident views across child companies. Works with the AI you already use - ChatGPT (desktop app), Claude Desktop, Codex, Claude Code, Claude Cowork, and GitHub Copilot - plus Gemini CLI. Free, open source, runs on your laptop. Built for MSP owners. No code required.

Works with your agent

Security note (until this connector is reprinted). Do not run HTTP mode

(--transport http), not even on localhost. This build checks a token, but it

predates the fix release's request size and time limits. The MCP tools can

also make changes with your credentials. Use the default stdio transport. If

you set up a tunnel for a remote agent, shut it down. A fix is on the way.

The six agents MSP owners actually use (self-serve, works today):

The ChatGPT desktop app runs bitdefender-mcp locally and shares MCP configuration with Codex (OpenAI). ChatGPT on the web needs a remote (HTTP) server, and this connector's HTTP mode is paused until it is reprinted (see the security note in mcp-install.md), so msp-skills does not support it yet. If your team works there, a hosted gateway is the better pick; check that your AI app is on the gateway's setup list.

Also for the Microsoft and Google stacks

Big install base, but an honest heads-up: Gemini CLI runs the local binary you just installed, while Microsoft 365 Copilot and the Gemini app need a remote server, which msp-skills does not support yet.

Skill-native agents (also covered): Hermes and OpenClaw read this skill's SKILL.md directly *and* speak MCP - see their install sections below. Also works with Cursor, Windsurf, Cline, Continue.dev, and Zed via MCP. Full per-tool wire-up: [docs/which-agent.md](../../docs/which-agent.md).

Run more than one agent? Install across all 51+ supported agents in one command: npx skills add Servosity/msp-skills@latest (requires Node.js, then run the per-skill installer for the CLI/MCP binaries). See docs/which-agent.md.

Install in 60 seconds

Fastest for Claude Desktop - one-click .mcpb

Download Bitdefender MCP (.mcpb) - then open Claude Desktop > Settings > Extensions and select the file. One click, no JSON, no shell. (Browse every Bitdefender release on the releases page.)

Prefer the Claude Code plugin? Add the marketplace once, then install - works immediately, no directory listing required:

/plugin marketplace add Servosity/msp-skills

/plugin install bitdefender@msp-skills

Path A - paste one prompt into your AI agent (recommended)

Copy this into Claude Code, Codex CLI, or Claude Cowork:

Install the Bitdefender Skill and MCP server from Servosity/msp-skills in this agent workspace. If this workspace uses a POSIX shell (macOS, Linux, WSL, or Bash), run bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/bitdefender/install.sh). If it uses Windows PowerShell, run iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/bitdefender/install.ps1 | iex. Then authenticate per the README and run bitdefender-cli --help to explore.

The same prompt works in any agent that can run shell.

Path B - run the installer yourself

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/bitdefender/install.ps1 | iex

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/bitdefender/install.sh)

The installer drops both bitdefender-cli (the CLI) and bitdefender-mcp (the MCP server) into your user bin path. Claude Code, Codex, and Cowork discover the Skill via SKILL.md in this directory.

Verify:

bitdefender-cli --version

Upgrade to the latest version

The installer always fetches the current release - re-run it to upgrade:

macOS / Linux:

bash <(curl -fsSL https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/bitdefender/install.sh)

Windows (PowerShell):

iwr -useb https://raw.githubusercontent.com/Servosity/msp-skills/main/skills/bitdefender/install.ps1 | iex

Claude Desktop .mcpb users: download the latest .mcpb (top of this section) and re-select it in Settings > Extensions. Claude Code plugin users: /plugin update bitdefender@msp-skills.

Add to Claude Desktop, the ChatGPT desktop app, GitHub Copilot, Gemini CLI, or another MCP client

After the installer runs, see [mcp-install.md](./mcp-install.md) and [docs/which-agent.md](../../docs/which-agent.md) for the per-agent wire-up - one section per agent, including the GitHub Copilot servers key and the ChatGPT desktop app. Claude Desktop's Settings > Extensions panel is the simplest path; the MCP config block (for users who prefer editing JSON) is documented in mcp-install.md.

Install for Hermes

From the Hermes CLI:

hermes skills install servosity/msp-skills/skills/bitdefender --force

Inside a Hermes chat session:

/skills install servosity/msp-skills/skills/bitdefender --force

Hermes speaks MCP natively, so it can also use the bitdefender-mcp server directly - same install path, same env vars.

Install for OpenClaw

Tell your OpenClaw agent (copy this):

Install the bitdefender skill from https://github.com/servosity/msp-skills/tree/main/skills/bitdefender. The skill defines how its required CLI (bitdefender-cli) can be installed via the openclaw: frontmatter block.

OpenClaw isn't generally available yet; the frontmatter wiring is pre-shipped and will activate the moment OpenClaw launches.

Authenticate

Set the API key from GravityZone Control Center (user icon > My Account > Control Center API). BITDEFENDER_BASE_URL is only needed when your Access URL is not https://cloud.gravityzone.bitdefender.com/api:

BITDEFENDER_API_KEY=<value> bitdefender-cli doctor

On Windows (PowerShell):

$env:BITDEFENDER_API_KEY = "<value>"

bitdefender-cli doctor

doctor checks config, paths and API reachability, and sends the key to GravityZone's getApiKeyDetails method, so a rejected or deleted key shows up as a Credentials: ERROR row and a wrong base URL as an API: ERROR row. It exits 0 even then, so scripts should add --fail-on error. bitdefender-cli api-key --json shows which API areas the key has.

What this skill does

Full command reference: guide.md. For the AI-agent operating contract (--agent, --dry-run, when to confirm before mutating), see AGENTS.md.

What makes this different

Most Bitdefender GravityZone integrations and MCP servers proxy each question into a live API call. That's fine for one record. It dies at scale, when you're asking "which of my 60 customers have unmanaged machines or agents that went out of date since last week".

GravityZone's Public API is JSON-RPC, one method per call, and the company tree comes back one level per getCompaniesList call. This skill walks the whole partner tree for you and fans each question out across every child company. fleet health saves each run as a dated local snapshot (SQLite), so fleet changes diffs two runs, and fleet locate and fleet rmm-gap answer from the latest one without another fan-out. A company it could not read completely is listed in fetch_failures, never counted as clean.

Integrations such as Liongard's GravityZone inspector and Sumo Logic's GravityZone automation integration bring GravityZone data into their own platforms. This one puts the cross-customer answers in whichever AI agent you already use. It complements GravityZone Control Center rather than replacing it: the console stays the place for policy authoring, investigations and day-to-day response.

The pain this closes

The GravityZone Public API is JSON-RPC, and getCompaniesList answers one level of the company tree at a time, so every MSP script walks sub-partners and folders itself, then pages getEndpointsList per company. A Bitdefender Expert Community thread shows a hand-built PowerShell paging loop th