Feature Request: Add support for GitHub Security APIs (Dependabot, Code Scanning, Secret Scanning)

[brandonganem]

Summary

The MCP server currently lacks tools to interact with GitHub's security features. Adding support for the Security APIs would enable AI agents to help users identify, triage, and remediate security vulnerabilities in their repositories.

Use Case

When a user asks an AI agent to "fix the issues in the security tab" of a repository, the agent currently cannot:

1. List security alerts - No way to retrieve Dependabot alerts, Code Scanning alerts, or Secret Scanning alerts
2. View alert details - Cannot get specifics about a vulnerability (CVE, severity, affected package/file, remediation guidance)
3. Dismiss or resolve alerts - Cannot mark alerts as fixed, dismissed, or false positives
4. Update vulnerable dependencies - While file editing is possible, understanding what needs to change requires alert data

Requested Tools

Dependabot Alerts

• list_dependabot_alerts - List Dependabot alerts for a repository
• get_dependabot_alert - Get details of a specific Dependabot alert
• update_dependabot_alert - Dismiss or reopen a Dependabot alert

Code Scanning (CodeQL)

• list_code_scanning_alerts - List code scanning alerts for a repository
• get_code_scanning_alert - Get details of a specific code scanning alert
• update_code_scanning_alert - Dismiss or reopen a code scanning alert

Secret Scanning

• list_secret_scanning_alerts - List secret scanning alerts for a repository
• get_secret_scanning_alert - Get details of a specific secret scanning alert
• update_secret_scanning_alert - Update the state of a secret scanning alert (resolve, reopen, etc.)

API References

• Dependabot Alerts API
• Code Scanning API
• Secret Scanning API

Impact

These tools would enable AI agents to:

• Automatically identify and fix vulnerable dependencies by updating Gemfile, package.json, etc.
• Review and help remediate code scanning findings
• Assist with secret rotation workflows when credentials are exposed
• Provide security posture summaries for repositories

Thank you for considering this enhancement!

[brandonganem]

[SamMorrowDrums]

@brandonganem this is only partially true, you can enable the code_security, dependabot, secret_protection and security_advisories toolsets to get related tools.

But we only have get and list tools. We don't have write tools, so some of your request still stands.

We don't enable all tools by default because we have users with context issues if we do, so we used usage data to determine what is in default toolset but you can use the all toolset or /mcp/x/all (as remote server URL) to see the full list of tools available.

The documentation does mention all this so have a hunt, and perhaps update the ticket with what you think we should do to improve what's already there.