#077Tutorial3 min

Use Hackaiz with Cursor

Choose the editor extension or an MCP connection, and check your Cursor version before setting up assistant access.

Hackaiz team · updated 21/11/2026

Illustration: a developer uses an editor and a terminal.
Illustration: a developer uses an editor and a terminal. Illustrative photo, not a screenshot.

01Choose between the extension and the assistant

Cursor can approach Hackaiz in two distinct ways described in the project: through the editor extension, or through a remote MCP server used by its assistant. MCP is a protocol that lets an assistant call named tools. The extension gives you views, source annotations and explicit scan commands. The MCP connection lets the assistant read authorized platform information and request approved operations in a conversation. Installing one does not silently configure the other.

The preparation guide at /docs/integration-cursor explicitly says no end-to-end test with Cursor is confirmed there. Remote HTTP servers and OAuth sign-in may vary with your version, plan and Cursor policies. Treat the guide as a configuration starting point, not a native partnership announcement or a guarantee that every Cursor installation supports the connection. If the required capabilities are absent, use the Hackaiz web application instead.

02Prepare the remote MCP connection

The documented example uses .cursor/mcp.json with this configuration: {"mcpServers":{"hackaiz":{"url":"https://hackaiz.com/mcp"}}}. Check Cursor’s documentation for the configuration location supported by your installed version. The server address is an HTTP MCP endpoint over HTTPS, not an ordinary web page to paste into a code file. Use the normal Hackaiz browser sign-in and consent flow when Cursor offers it.

Do not paste a personal API key, browser session or access token into the assistant chat to get past an authentication error. The remote MCP connection uses OAuth, which delegates access through sign-in and consent. Start with a request such as “List my Hackaiz platforms”, then ask for one finding from the expected platform. Confirm that the returned names belong to your account before attempting a paid operation.

03Approve the exact operation in the conversation

Once reading works, ask about a specific saved platform or finding rather than “scan everything”. The registered tools include list_platforms, list_verified_sites, list_findings, read_analysis and explain_finding. For a new analysis, run_analysis requires your explicit approval in the conversation and uses account credits. The assistant must identify the intended platform before setting user_approved to true; connecting the account is not blanket approval for future launches.

A website or API must already have current domain ownership proof. Complete that in Connect with the _hackaiz DNS TXT record, the HTTPS file /.well-known/hackaiz-verification.txt, or your project AI creating that file from the supplied instruction. Cursor access to source code does not replace this requirement. Returned findings omit raw evidence and secrets; do not add sensitive values to the conversation to compensate for that protection.

04Use editor views when source navigation matters

For a source-oriented workflow, the extension provides “Hackaiz: Connect personal key”, “Hackaiz: Scan this workspace” and “Hackaiz: Scan current file”. Unlike MCP OAuth, it stores a personal key in the editor’s SecretStorage. Review eligible files and exclusions before confirming a credit-using scan. Findings can then appear in the sidebar, as underlines and in Problems, which is useful when you want to investigate a local path rather than discuss a saved platform.

Neither route authorizes automatic code publication. The extension does not edit or commit code, and the assistant does not write or merge changes on GitHub. Continue correction review in Hackaiz; fixes are draft GitHub pull requests reviewed and approved by a human, never automatically merged. Keep the selected platform, the local checkout and any eventual deployment distinct when deciding whether a finding applies to the change you are making.

Frequently asked questions

Was this article helpful?

Related articles