How to Use the Checkmarx MCP in Cursor

Q: Can Cursor read my Checkmarx scan history?

The editor fetches historical data using the listscans tool. It retrieves status updates, branch targets, and timestamps for any active or completed job.

Give Cursor direct access to Checkmarx One so your AI can write patches for security vulnerabilities as you code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Checkmarx MCP to Cursor

Create your Vinkius account to connect Checkmarx to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Checkmarx with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Patch Checkmarx vulnerabilities in Cursor

Fixing security debt usually means toggling between your editor and a PDF report. Cursor changes that by calling `get_scan_results` to pull active vulnerabilities straight into your workspace. The AI reads the exact severity, state, and line numbers where the flaws live. Knowing where to apply the fix is half the battle. The agent triggers `list_bfl` to identify the Best Fix Location for a specific vulnerability node. Cursor then generates the actual code patch right in your active file based on that precise location.

Trigger SAST checks via the MCP Server

You do not need to wait for a CI/CD pipeline to tell you your code is broken. Cursor can execute `run_scan` the moment you finish a major refactor. It queues the job in Checkmarx One and returns the scan ID. Monitoring that job happens entirely in the background. The editor uses `get_scan_details` to check engine execution timings and catch any specific failure reasons. If you realize you made a mistake and push a quick fix, the agent hits `cancel_scan` to drop the old context.

Audit cloud infrastructure files instantly

Infrastructure as code requires a different set of rules than standard application logic. Cursor analyzes your Dockerfiles and Kubernetes manifests by pulling `get_kics_results` via the MCP Server. This keeps cloud misconfigurations separated from your standard SAST findings. Managing multi-repo setups works flawlessly. The AI maps out your workspace by checking `list_applications` to find the overarching product containers. Then it targets the exact codebase context using `get_project` before triggering any new analysis.

Setup guide

Set up Checkmarx MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Checkmarx MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Checkmarx transactions." If the MCP tools are loaded correctly, Cursor will call the Checkmarx tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "checkmarx-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Checkmarx. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Checkmarx now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Checkmarx MCP in Cursor

Create an mcp.json file in your project root directory. Paste the server configuration under the mcpServers key. Switch your chat to Agent mode and the tools will be ready to use.

The editor fetches historical data using the list_scans tool. It retrieves status updates, branch targets, and timestamps for any active or completed job.

Your agent reads the exact Terraform and CloudFormation misconfigurations directly from the API. It then writes the necessary corrections directly into your infrastructure files.

Pushing a new commit while an older job is running wastes engine resources. You just tell the agent to kill the overlapping job so the fresh code gets analyzed faster.

The MCP integration processes your vulnerability descriptions and severity states using a zero-trust model. Vinkius authenticates the endpoint token and immediately destroys the sandbox environment once the editor receives the payload. Nothing is saved.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript