Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read-only MCP server for DefectDojo Community Edition: triage findings, grouped across products.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
DEFECTDOJO_URL, DEFECTDOJO_API_KEY, DEFECTDOJO_VERIFY_TLS, DEFECTDOJO_TIMEOUT_SECONDSValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"defectdojo-community": {
"command": "uvx",
"args": [
"defectdojo-community-mcp"
],
"env": {
"DEFECTDOJO_URL": "your-value",
"DEFECTDOJO_API_KEY": "your-value",
"DEFECTDOJO_VERIFY_TLS": "your-value",
"DEFECTDOJO_TIMEOUT_SECONDS": "your-value"
}
}
}
}Run this in your terminal
claude mcp add defectdojo-community --env DEFECTDOJO_URL=your-value --env DEFECTDOJO_API_KEY=your-value --env DEFECTDOJO_VERIFY_TLS=your-value --env DEFECTDOJO_TIMEOUT_SECONDS=your-value -- uvx defectdojo-community-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"defectdojo-community": {
"command": "uvx",
"args": [
"defectdojo-community-mcp"
],
"env": {
"DEFECTDOJO_URL": "your-value",
"DEFECTDOJO_API_KEY": "your-value",
"DEFECTDOJO_VERIFY_TLS": "your-value",
"DEFECTDOJO_TIMEOUT_SECONDS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"defectdojo-community": {
"type": "stdio",
"command": "uvx",
"args": [
"defectdojo-community-mcp"
],
"env": {
"DEFECTDOJO_URL": "your-value",
"DEFECTDOJO_API_KEY": "your-value",
"DEFECTDOJO_VERIFY_TLS": "your-value",
"DEFECTDOJO_TIMEOUT_SECONDS": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
DEFECTDOJO_VERIFY_TLS envDEFECTDOJO_TIMEOUT_SECONDS envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account systechgd, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: DEFECTDOJO_URL, DEFECTDOJO_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 3 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv), Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, dsh-novel-writer — 网文写作体检
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Offline 21-tool Chinese web-novel style, plot and continuity audits, plus per-book cleanup.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
A read-only Model Context Protocol server for DefectDojo Community Edition — so an AI assistant can read your vulnerability findings, group the same vulnerability across every product, and draft issues for whatever tracker you use.
Unofficial. This is an independent open-source project. It is not affiliated
with, endorsed by, or supported by DefectDojo Inc. or OWASP. "DefectDojo" is used
only to describe what this server connects to.
If you run DefectDojo Pro, you probably don't. Pro has a built-in MCP server — use that instead; it is maintained by the vendor and more capable.
| DefectDojo Pro (built-in) | This project | |
|---|---|---|
| Edition | Pro only — AI features are Pro-only | Community Edition (works with Pro too) |
| Requires | DefectDojo v2.51.2+, enabled by a superuser | Any version with API v2 |
| Runs | Inside your instance, at /mcp | On your machine, as a local MCP process |
| Transport | Streamable HTTP | stdio |
| Tools | 18 in the read-only core toolset | 7 |
| Writes | None in core; available in Pro add-on toolsets (hierarchy, reporting, dashboards, psirt) | Never — see Safety model |
This project exists because Community Edition has no MCP server at all. It talks to the ordinary REST API v2 with a normal API token, so it needs nothing enabled server-side and no particular DefectDojo version.
Not to be confused with the unrelated
defectdojo-mcp
package on PyPI, which is a different third-party project. This one is
defectdojo-community-mcp.
| Tool | What it does |
|---|---|
health_check | Verify connectivity and auth; returns the instance URL and product count |
list_products | Every product, with its findings count |
list_critical_findings | Actionable criticals, optionally scoped to one product |
list_findings_by_severity | The same, for any severity |
group_critical_by_vuln | The useful one. Groups criticals across all products by CVE (else CWE+title), widest blast radius first |
list_duplicate_findings | Findings DefectDojo marked as duplicates |
get_finding | Full detail for one finding |
"Actionable" means active and not false-positive, duplicate, risk-accepted, out-of-scope or mitigated — the set actually worth someone's time.
group_critical_by_vuln is the reason this exists. A monorepo-shaped scanner setup reports the same upstream CVE once per product; this collapses them into one group per vulnerability listing every affected product, which maps cleanly onto one tracker issue.
Requires Python 3.10+.
pip install defectdojo-community-mcp
Or as a container:
docker pull ghcr.io/systechgd/defectdojo-community-mcp:latest
Listed on the MCP Registry as io.github.systechgd/defectdojo-community-mcp, so MCP clients that read the registry can install it by name.
Or from source:
git clone https://github.com/systechgd/defectdojo-community-mcp.git
cd defectdojo-community-mcp pip install -e .
Two environment variables are required.
| Variable | Required | Default | Notes |
|---|---|---|---|
DEFECTDOJO_URL | yes | — | Base URL, e.g. https://defectdojo.example.com. No trailing /api/v2. |
DEFECTDOJO_API_KEY | yes | — | API v2 token. See below for scoping it down. |
DEFECTDOJO_VERIFY_TLS | no | true | false disables certificate verification. See SECURITY.md. |
DEFECTDOJO_TIMEOUT_SECONDS | no | 30 | Per-request HTTP timeout. |
Get a token from DefectDojo → your user → API v2 Key.
Create a dedicated read-only user for it. The token inherits that user's permissions, and nothing in this server needs write access. If the token leaks, a read-only one cannot be used to alter your findings.
Check it works before wiring up a client:
defectdojo-community-mcp --check
claude mcp add defectdojo \
--env DEFECTDOJO_URL=https://defectdojo.example.com \ --env DEFECTDOJO_API_KEY=your-token \ -- defectdojo-community-mcp
{
"mcpServers": { "defectdojo": { "command": "defectdojo-community-mcp", "env": { "DEFECTDOJO_URL": "https://defectdojo.example.com", "DEFECTDOJO_API_KEY": "your-token" } } } }
If the console script is not on your PATH, use "command": "python", "args": ["-m", "defectdojo_community_mcp"].
The server speaks MCP over stdio, so run it attached (-i), not detached:
{
"mcpServers": { "defectdojo": { "command": "docker", "args": [ "run", "--rm", "-i", "-e", "DEFECTDOJO_URL", "-e", "DEFECTDOJO_API_KEY", "ghcr.io/systechgd/defectdojo-community-mcp:latest" ] } } }
Group every critical finding by vulnerability and show me the ones affecting
more than three services.
The assistant calls group_critical_by_vuln and gets back, per vulnerability, the CVE, title, affected product list and a direct DefectDojo URL per finding — enough to write one issue covering all of them, instead of twelve near-identical ones.
Read-only is a design invariant, not a default.
POST, PUT, PATCH or DELETE.GET.Adding write support would be a breaking change to this guarantee. If it ever happens it will be a separate server, so operators can keep granting read without granting write.
Findings data is attacker-influenced — scanner output can contain text from dependency metadata, file paths and commit messages. Treat tool results as data, never as instructions. See SECURITY.md for the full threat model and how to report a vulnerability.
git clone https://github.com/systechgd/defectdojo-community-mcp.git
cd defectdojo-community-mcp python -m venv .venv && . .venv/bin/activate # Windows: .venv\Scripts\activate pip install -e ".[dev]"
pytest # 57 tests, no network or live instance needed ruff check .
The test suite runs entirely against httpx.MockTransport. CI additionally runs the suite on Python 3.10–3.13 and against both MCP SDK generations (mcp<2, which has FastMCP, and mcp>=2, which renamed it to MCPServer).
See CONTRIBUTING.md and CODE_OF_CONDUCT.md.
Apache-2.0. See NOTICE.