Bitdefender GravityZone

● Active

io.github.WYRE-AI/bitdefender-mcp

MCP server for Bitdefender GravityZone's JSON-RPC API.

Connect this server

One click to install, or copy the config below. Suits: Claude Desktop · Cursor.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "bitdefender-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/wyre-ai/bitdefender-mcp:v1.1.1"
      ],
      "env": {
        "BITDEFENDER_API_KEY": "<your BITDEFENDER_API_KEY>",
        "BITDEFENDER_ACCESS_URL": "<your BITDEFENDER_ACCESS_URL>",
        "MCP_TRANSPORT": "stdio",
        "AUTH_MODE": "env",
        "LOG_LEVEL": "info"
      }
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --env BITDEFENDER_API_KEY='<your BITDEFENDER_API_KEY>' --env BITDEFENDER_ACCESS_URL='<your BITDEFENDER_ACCESS_URL>' --env MCP_TRANSPORT=stdio --env AUTH_MODE=env --env LOG_LEVEL=info --transport stdio bitdefender-mcp -- docker run -i --rm ghcr.io/wyre-ai/bitdefender-mcp:v1.1.1
OpenAI Codex CLI
codex mcp add bitdefender-mcp --env BITDEFENDER_API_KEY='<your BITDEFENDER_API_KEY>' --env BITDEFENDER_ACCESS_URL='<your BITDEFENDER_ACCESS_URL>' --env MCP_TRANSPORT=stdio --env AUTH_MODE=env --env LOG_LEVEL=info -- docker run -i --rm ghcr.io/wyre-ai/bitdefender-mcp:v1.1.1
VS Code
code --add-mcp '{"name":"bitdefender-mcp","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/wyre-ai/bitdefender-mcp:v1.1.1"],"env":{"BITDEFENDER_API_KEY":"<your BITDEFENDER_API_KEY>","BITDEFENDER_ACCESS_URL":"<your BITDEFENDER_ACCESS_URL>","MCP_TRANSPORT":"stdio","AUTH_MODE":"env","LOG_LEVEL":"info"}}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.

Environment variables
  • BITDEFENDER_API_KEYrequiredsecretBitdefender GravityZone API key, generated in Control Center -> My Account -> API keys, with the Network/Policies/Reports/Incidents APIs selected.
  • BITDEFENDER_ACCESS_URLrequiredThe Control Center Access URL (My Account -> Control Center API), e.g. https://cloud.gravityzone.bitdefender.com.
  • MCP_TRANSPORTTransport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.
  • AUTH_MODECredential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.
  • LOG_LEVELLog verbosity: debug, info, warn, error

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Other
Version
1.1.1
Registry
active
Published
11/20/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Mostly fine: Bitdefender GravityZone is maintained.

Maintained
Active
Last commit 9 days ago (Nov 12, 2026), 3 open issues.
Official registry
Active
Published as io.github.WYRE-AI/bitdefender-mcp in the official MCP registry, version 1.1.1.
Source
No licence found
Public repository, but GitHub reports no recognised licence (1 stars). Check the README before shipping it in a product.
Runs
On your machine
A local Docker package started by your client; it can reach whatever your user account can.
Credentials
2 required
Declared environment variables: BITDEFENDER_API_KEY, BITDEFENDER_ACCESS_URL. They stay on your machine; the config on this page shows where each goes.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself.

On GitHub

read Nov 17, 2026
Stars
1
Forks
1
Last push
Nov 12, 2026
License
Other

TypeScript

From the README

Bitdefender GravityZone MCP Server MCP server for Bitdefender GravityZone's Control Center API - endpoint/network inventory, security policies, the account-wide malware-hash Blocklist, and scheduled/instant reports - for AI assistants and the WYRE Conduit gateway. New call shape for this catalog: GravityZone's API is JSON-RPC 2.0, not REST - every other Conduit sidecar (Cork, CyberQP, Slide, UniFi, Cisco Duo) calls a conventional REST API. See Authentication and JSON-RPC shape below. Authentication GravityZone authenticates with HTTP Basic Authentication (RFC 2617): the API key is sent as the username, with an empty password - Authorization: Basic base64(apiKey + ":"). This is also a new shape for this catalog - every other static-key connector here (Cork, CyberQP, Slide, UniFi) sends a custom X-Vendor-Api-Key header that the sidecar turns into a Bearer token; GravityZone has no bearer-token concept at all. API keys are generated in Control Center under My Account -> API keys, and each key is scoped, at generation time, to a checklist of API areas (Network, Policies, Reports, Incidents, Companies, Licensing, Accounts, Packages, Integrations, Push, Quarantine). This connector's key needs the Network, Policies, Reports, Incidents, and Quarantine areas selected - the other six are never called and do not need to be enabled. If the current key was generated without Quarantine, the quarantine tool returns HTTP 403 until a key with it is in place.…

Read the full README on GitHub →

The most-starred Other servers in the index, with their live-check result.

ServerStarsLast pushLive check
Labelhead Artist Momentum114,594Nov 2026Working
World Monitor91,002Nov 2026Needs sign-in
Tldraw51,470Nov 2026Working
OpenSEO28,515Nov 2026Needs sign-in
Windows MCP11,833Nov 2026Local / not checked

Bitdefender GravityZone: questions people ask

Is Bitdefender GravityZone a remote or a local MCP server?
According to its entry in the official MCP registry, Bitdefender GravityZone ships as a local package (Docker) that your client starts on your machine.
Does Bitdefender GravityZone need an API key?
Its registry entry declares 2 required environment variables: BITDEFENDER_API_KEY, BITDEFENDER_ACCESS_URL. The config on this page shows where each goes.
Is Bitdefender GravityZone safe to use?
Mostly fine: Bitdefender GravityZone is maintained. In detail — maintained: Active; official registry: Active; source: No licence found; runs: On your machine; credentials: 2 required. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
Is Bitdefender GravityZone still maintained?
Active: the repository's last commit 9 days ago. Last push Nov 12, 2026, 1 GitHub stars, Other licence. Read from GitHub on Nov 17, 2026.
How do I add Bitdefender GravityZone to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
  1. AutotaskMCP server for Kaseya Autotask PSA — companies, tickets, projects, time entries, and more.★ 64
  2. ConnectWise ManageMCP server for ConnectWise Manage PSA — companies, tickets, projects, time entries, and more.★ 32
  3. NinjaOneMCP server for NinjaOne RMM — devices, organizations, alerts, and tickets.★ 32
  4. IT GlueMCP server for IT Glue — organizations, configurations, passwords, flexible assets, and documents.★ 18
Browse all Other →

Add the badge to your site

Show visitors that Bitdefender GravityZone is listed here — it’s also the link we check for a free listing.

Bitdefender GravityZone — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-wyre-ai-bitdefender-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Bitdefender GravityZone — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Bitdefender GravityZone — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-wyre-ai-bitdefender-mcp?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-wyre-ai-bitdefender-mcp) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-wyre-ai-bitdefender-mcp) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-wyre-ai-bitdefender-mcp)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-wyre-ai-bitdefender-mcp"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-wyre-ai-bitdefender-mcp"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-wyre-ai-bitdefender-mcp"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).