S

MCP Entry

Semgrep MCP

Connects AI coding agents to Semgrep static analysis rules and findings so security reviews can start from actual scan results. Agents can look up rule definitions, triage findings, and verify fixes without pasting SARIF outputs. Integrates with CI/CD pipelines.

Category Developer Tools
Install npm
Runtime Node.js
securitysastcode

Use cases

  • Security engineer triages findings by understanding rule logic and severity
  • Developer looks up why Semgrep flagged a pattern and how to fix it
  • DevOps compares scan results between branches to catch regressions
  • Auditor reviews historical findings to assess security posture over time
  • Architect evaluates which Semgrep rules to enable for a new project

Key features

  • Claude Code
  • Cursor
  • VS Code

Frequently Asked Questions

What Semgrep products does the MCP support?
The MCP supports Semgrep Code (SAST), Semgrep Supply Chain (dependency scanning), and Semgrep Secrets (secret detection). Each requires appropriate API access.
Can agents run new scans or only view existing findings?
The MCP can trigger new scans via the Semgrep API if you have CI/CD integration configured. It primarily provides read access to findings and rule metadata.
Do agents need Semgrep Cloud or self-hosted access?
Semgrep Cloud (app.semgrep.dev) is the primary integration point. Self-managed Semgrep deployments may work but features vary. Check docs for self-hosted setup.

Related

Related

3 Indexed items