2,500+ MCP servers ready to use
Vinkius

Semgrep MCP Server for Cursor 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Semgrep and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "semgrep": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Semgrep
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Semgrep MCP Server

Connect the Semgrep AppSec platform directly to your AI agent to radically accelerate code security triaging. Instead of forcing developers to jump between their IDE and the Semgrep dashboard, empower your AI to pull 'Findings', analyze the vulnerable syntax, and instantly close false positives.

Cursor's Agent mode turns Semgrep into an in-editor superpower. Ask Cursor to generate code using live data from Semgrep and it fetches, processes, and writes — all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

  • Triage Findings (Bugs) — Instruct the agent to grab the latest CI vulnerability findings and immediately push a status update to mark it as fixed, ignored, or mitigated (update_finding_status)
  • Rule Management — Request the AI to look at a newly discovered bad coding pattern and command it to write and deploy a matching custom semantic rule (create_rule) to your organizational deployment
  • Project & Deployment Scoping — Map out all repositories running Semgrep actions and check their overarching security health scores in milliseconds
  • Comprehensive Forensics — Fetch granular SCA and SAST semantic flaw definitions, including exact snippets, CVE links, and the specific bad lines causing the trigger

The Semgrep MCP Server exposes 10 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Semgrep to Cursor via MCP

Follow these steps to integrate the Semgrep MCP Server with Cursor.

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

03

Save the file

Cursor will automatically detect the new MCP server

04

Start using Semgrep

Open Agent mode in chat and ask: "Using Semgrep, help me..."10 tools available

Why Use Cursor with the Semgrep MCP Server

Cursor AI Code Editor provides unique advantages when paired with Semgrep through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP — no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Semgrep + Cursor Use Cases

Practical scenarios where Cursor combined with the Semgrep MCP Server delivers measurable value.

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Semgrep MCP Tools for Cursor (10)

These 10 tools become available when you connect Semgrep to Cursor via MCP:

01

create_rule

Allows developers to forbid project-specific bad patterns securely and continuously across the enterprise repositories. Create a customized Semgrep security rule within the platform

02

delete_rule

Delete a custom Semgrep security rule from the deployment

03

get_finding_details

Explains the exact malicious code block, suggests semantic fixes, states whether it is blocking PRs in CI, and links to CVE data (if an SCA supply chain defect). Get atomic details for a specific Semgrep flaw

04

get_metrics

Typically consumed to render executive security dashboards. Get AppSec metrics and compliance stats for Semgrep

05

get_project

Search for a precise Semgrep project by exact repository name

06

list_deployments

The primary key is the deployment slug identifier. Almost all subsequent API operations targeting rules, projects, or findings will require this deployment slug to define the scope. List Semgrep organizational deployments

07

list_findings

Findings provide snippet details, file line numbers, severity, and rule types. Fetch global static analysis security findings for a deployment

08

list_projects

Projects maintain a link between developers and static security scan outputs over time. List Semgrep projects (repositories) monitored in a deployment

09

list_rules

The rules are structured YAML definitions that search for semantic anti-patterns in codebases (e.g., unparameterized SQL queries, hardcoded AWS keys). List Semgrep semantic rules deployed globally

10

update_finding_status

Valid states generally include active, fixed, false_positive, ignored, mitigated. Resolving findings through this API cleans up the developer experience when managing compliance queues. Mark a Semgrep finding state (e.g., fixed, false positive)

Example Prompts for Semgrep in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Semgrep immediately.

01

"List the most severe unmitigated findings currently breaking our CI/CD pipeline on the 'vinkius/cloud' repository."

02

"Mark vulnerability issue ID #58032 as a 'false_positive' using the update finding tool."

03

"Review the company's Semgrep performance metrics focusing on fix rate."

Troubleshooting Semgrep MCP Server with Cursor

Common issues when connecting Semgrep to Cursor through the Vinkius, and how to resolve them.

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Semgrep + Cursor FAQ

Common questions about integrating Semgrep MCP Server with Cursor.

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design — tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Connect Semgrep to Cursor

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.