DefectDojo MCP Server

MCP server for DefectDojo: 24 tools with RBAC, HMAC audit chain, and SIEM forwarding. Exposed over MCP by the defectdojo mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

MCP server for DefectDojo vulnerability management. Exposes 24 tools for managing products, engagements, tests, findings, scan imports, and finding lifecycle through the Model Context Protocol.

Its toolset

Everything the assistant can do here goes through one of these:

• Variable — Description
• DEFECTDOJO_READ_API_KEY — Read-only API key (used for GET requests)
• DEFECTDOJO_WRITE_API_KEY — Write API key (used for POST/PATCH requests)
• health_check — system
• list_products — metadata_read
• get_product — metadata_read
• list_product_types — metadata_read
• list_engagements — metadata_read
• get_engagement — metadata_read
• list_tests — metadata_read
• get_test — metadata_read
• list_test_types — metadata_read

Configuration

You will need 8 environment variables: AUDIT_HMAC_KEY, MCP_ROLE_CI, DEFECTDOJO_URL, DEFECTDOJO_API_KEY, DEFECTDOJO_READ_API_KEY, DEFECTDOJO_WRITE_API_KEY, MCP_AUTH_TOKEN, MCP_READ_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. DefectDojo's toolset — Variable, DEFECTDOJO_READ_API_KEY, DEFECTDOJO_WRITE_API_KEY and 11 more — is a fair guide to whether it matches your workflow. It is maintained by inspicere; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch DefectDojo.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the defectdojo mcp server does with a few real requests.