Semgrep MCP Server

Created By
semgrepa year ago
A MCP server for using Semgrep to scan code for security vulnerabilities.
Overview

what is Semgrep MCP Server?

Semgrep MCP Server is a tool that allows users to utilize Semgrep for scanning code within the Model Context Protocol (MCP) framework, enabling integration with LLMs and AI agents.

how to use Semgrep MCP Server?

To use the Semgrep MCP Server, you can run it via Docker or command line interface (CLI) after installation. You can scan code snippets or entire directories for security vulnerabilities and create custom rules.

key features of Semgrep MCP Server?

  • Scanning code snippets for security vulnerabilities
  • Performing scans on entire directories
  • Listing and creating custom Semgrep rules
  • Analyzing and filtering scan results
  • Exporting results in various formats (JSON, SARIF, text)
  • Comparing scan results to identify new and fixed issues

use cases of Semgrep MCP Server?

  1. Scanning code for security vulnerabilities in software projects.
  2. Creating custom rules for specific coding standards or security policies.
  3. Analyzing scan results to improve code quality and security.

FAQ from Semgrep MCP Server?

  • Can Semgrep MCP Server scan any programming language?

Yes! Semgrep supports multiple programming languages for scanning.

  • Is Semgrep MCP Server free to use?

Yes! The Semgrep MCP Server is open-source and free to use.

  • How can I contribute to the Semgrep MCP project?

You can contribute by reporting issues, suggesting features, or submitting pull requests on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
semgrep
Star
178
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago