Skip to content

docs(ai): add the Claude Code plugin page and correct the MCP tool count - #15682

Open
devGregA wants to merge 1 commit into
bugfixfrom
docs/claude-code-plugin-and-mcp-tools
Open

docs(ai): add the Claude Code plugin page and correct the MCP tool count#15682
devGregA wants to merge 1 commit into
bugfixfrom
docs/claude-code-plugin-and-mcp-tools

Conversation

@devGregA

Copy link
Copy Markdown
Contributor

Two gaps on the AI docs

1. The tool count was wrong

The MCP Server page states the server provides 12 tools. It provides 14. The reference was missing finding_summary and risk_summary, both of which have been registered in the server for some time.

Verified by diffing the documented <summary> blocks against the tool registrations:

MISSING from docs: finding_summary, risk_summary
counts: documented=12  actual=14

Both are now documented in the existing format, under Findings Analysis Tools. The finding_summary entry notes when it should be preferred over get_findings, since one summary call answers "how many" correctly beyond the 100-record page limit instead of paging and counting.

2. There was no Claude Code guidance anywhere

The only configuration example in the docs is the Claude Desktop config file, which is the wrong shape for Claude Code. Anyone using it was left to work it out from the connection parameters.

The new page covers the two-command install, prerequisites and version floors, what each plugin does, how the MCP and REST channels are wired from a single credential entry, CI usage with a service account rather than a personal token, and a troubleshooting table for the four failures that actually occur.

Cross-linking

The two pages now point at each other, so readers land in the right place:

  • The MCP page adds a callout above the provider quick starts sending Claude Code users to the plugin rather than the hand-rolled config.
  • The plugin page points back for administrator setup, and for chat assistants such as Claude Desktop or claude.ai.

Links use the sibling ../page/ form these Doks pages require.

Notes

  • Both pages are audience: pro. The plugin page states plainly that it requires DefectDojo Pro and refuses to run against open source rather than partially working.
  • The plugin page uses weight: 24, directly after the MCP page at 23.
  • No credentials, internal hostnames or customer names; placeholder instance names throughout.
  • The plugin repository referenced by the page is not published yet, so that one link goes live with the repository.

🤖 Generated with Claude Code

Two gaps on the AI docs.

The MCP Server page said the server provides 12 tools. It provides 14: the
reference was missing finding_summary and risk_summary, both of which have been
in the server for some time. Counting the documented <summary> blocks now gives
14 and matches the tool registrations. The two new entries follow the existing
format and note when a summary call is preferable to paging through findings.

There was also no Claude Code guidance anywhere in the docs. The only
configuration example was the Claude Desktop config file, which is the wrong
shape for Claude Code users, so they were left to work it out. The new page
covers the two-command install, prerequisites, what each plugin does, how the
MCP and REST channels are wired, CI usage with a service account, and a
troubleshooting table.

The pages cross-link both ways: the MCP page now points Claude Code users at
the plugin rather than the hand-rolled config, and the plugin page points back
for administrator setup and for chat assistants such as Claude Desktop.

Both pages are audience: pro. The plugin requires DefectDojo Pro and the page
states that it refuses to run against open source rather than partially
working.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@github-actions github-actions Bot added the docs label Aug 16, 2026
@Maffooch Maffooch added this to the 3.2.300 milestone Aug 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants