2,500+ MCP servers ready to use
Vinkius

Intruder 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 Intruder 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": {
    "intruder": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Intruder
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 Intruder MCP Server

Empower your AI agents to manage your cybersecurity posture with Intruder.io. This MCP server allows you to list security targets, track vulnerability scans, retrieve identified issues, and monitor cloud integrations directly through the Intruder API. Ideal for automating DevSecOps workflows and security auditing.

Cursor's Agent mode turns Intruder into an in-editor superpower. Ask Cursor to generate code using live data from Intruder 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.

The Intruder 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 Intruder to Cursor via MCP

Follow these steps to integrate the Intruder 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 Intruder

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

Why Use Cursor with the Intruder MCP Server

Cursor AI Code Editor provides unique advantages when paired with Intruder 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

Intruder + Cursor Use Cases

Practical scenarios where Cursor combined with the Intruder 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

Intruder MCP Tools for Cursor (10)

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

01

get_account

Use to verify identity and account settings. Gets your Intruder account details

02

get_issue

Returns detailed descriptions, remediation advice, and affected targets. Essential for investigating and fixing security flaws. Retrieves details for a specific issue

03

get_scan

Returns the list of targets included, scan duration, and a summary of findings. Use this to audit the results of a specific security assessment. Retrieves details for a specific scan

04

get_target

Returns metadata and associated tags. Use this to deep-dive into the security status of a specific asset. Retrieves details for a specific target

05

list_cloud_integrations

Essential for auditing how Intruder discovers new targets in the cloud infrastructure. Lists all configured cloud integrations (AWS, Azure, Google Cloud)

06

list_issues

Returns issue titles, severity levels (Low, Medium, High, Critical), and status. Use this as the primary tool for security posture auditing. Lists all identified vulnerability issues

07

list_licences

Useful for verifying subscription status and capacity. Lists all account licences

08

list_scans

Includes scan types, timestamps, and IDs. Essential for tracking scan frequency and monitoring ongoing security checks. Lists all vulnerability scans

09

list_targets

Returns target names, IDs, and types. Use this to identify which assets are being scanned for vulnerabilities. Lists all infrastructure and application targets

10

list_teams

Useful for understanding organizational access controls. Lists all organization teams

Example Prompts for Intruder in Cursor

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

01

"List all active targets in my Intruder account."

02

"Show me the latest vulnerability issues found."

03

"Check the status of my recent scans."

Troubleshooting Intruder MCP Server with Cursor

Common issues when connecting Intruder 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.

Intruder + Cursor FAQ

Common questions about integrating Intruder 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 Intruder to Cursor

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