How to Use the HCL AppScan MCP in Cursor

Q: How do I connect HCL AppScan to my Cursor editor?

Create a .cursor/mcp.json file in your project's root. Add the HCL AppScan MCP server configuration there. The agent automatically picks up the tools when you restart Cursor.

Inject live HCL AppScan vulnerability data directly into your code with the Cursor agent.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect HCL AppScan MCP to Cursor

Create your Vinkius account to connect HCL AppScan 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 HCL AppScan with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Code with Real Vulnerability Data

You're fixing a bug and need to know if it's security-related. Ask the Cursor agent, "what are the current high-severity issues for this service?" It uses `list_issues` to get live data from HCL AppScan. The agent doesn't just show you a list. It can use the detailed report from `get_issue` to help you write the actual fix. Highlight a function and ask, "refactor this to avoid the SQL injection vulnerability in issue #5678." You're coding with real-time security context.

Trigger Scans, Get Results in Cursor

You're about to merge a feature branch. Instead of waiting for the CI pipeline, tell the agent in Cursor, "kick off a DAST scan for the 'auth-service' app." It runs `start_dast_scan` and gives you back the scan ID. You can then ask it to check the status using `get_scan`. Once the scan is done, tell the agent to fetch all new issues with `list_issues` and generate a markdown report for you in a new file. You never have to leave your editor.

Map AppScan Apps to Your Repo with this MCP Server

It's easy to lose track of which AppScan application maps to which microservice in a big monorepo. This MCP server solves that. Ask the Cursor agent, "show me the details for the 'frontend-web' app in AppScan." It uses `get_app` to pull the configuration, confirming the scan target URL and other settings. This check ensures you're about to run `start_dast_scan` on the correct asset, closing the gap between your code and your security tools.

Setup guide

Set up HCL AppScan 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 HCL AppScan 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 HCL AppScan transactions." If the MCP tools are loaded correctly, Cursor will call the HCL AppScan tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "hcl-appscan-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 HCL AppScan. 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 HCL AppScan 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 HCL AppScan MCP in Cursor

Activate the agent and ask it to find the issue. For example, "get me the details for HCL AppScan issue #9901." The agent uses the `get_issue` tool and can even help you write a test case based on the findings.

Absolutely. Just tell the agent which app to scan, like "start a DAST scan for the 'user-profile-api'." It uses the `start_dast_scan` tool from this MCP integration to get it done.

Create a `.cursor/mcp.json` file in your project's root. Add the HCL AppScan MCP server configuration there. The agent automatically picks up the tools when you restart Cursor.

Ask the agent, "list all my recent scans in AppScan." It will call the `list_scans` tool and format the output for you, showing IDs, statuses, and timestamps in a clean table.

It only interacts with your HCL AppScan account data—application lists, scan IDs, and vulnerability reports. Your code is never sent to the MCP server. Vinkius runs the server in an ephemeral container and all API calls are encrypted.

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