Fix site-audit issues in Cursor

• Copy Project DataFetch the same project JSON the app copies from the header. Use it so Cursor can rank fixes by impact.
• List audit issuesGet open issues with page URLs and recommendations so Cursor can find the right files.
• Fresh site auditStart a new crawl from Cursor when you need current scores. It counts toward your plan, just like the dashboard.

Before you connect

• Cool Web Tool accountSign up or log in at coolwebtool.com. Create a project and run a site audit.
• API tokenCreate a token from the dashboard MCP setup sheet. It is shown once. Treat it like a password. Do not clone the Cool Web Tool GitHub repo.

Add a remote MCP server using the hosted URL below. Do not point Cursor at a local cool-web-tool-mcp folder. That path is for Cool Web Tool engineers.

https://mcp.coolwebtool.com/mcp

{
  "mcpServers": {
    "cool-web-tool": {
      "url": "https://mcp.coolwebtool.com/mcp",
      "headers": {
        "Authorization": "Bearer REPLACE_WITH_API_TOKEN"
      }
    }
  }
}

1. In Cursor, open Settings, then MCP, and add a new server (or edit mcp.json).
2. Paste the snippet. Replace REPLACE_WITH_API_TOKEN with the token from the dashboard.
3. Reload MCP. Confirm the tools include get_project_copy_data and list_audit_issues.
4. Open your website repo (not Cool Web Tool). Ask Cursor to list audit issues for your project UUID and patch the matching files.

Privacy and safety tips

• The token can read your audits. Do not paste it into untrusted chats or public gists.
• Revoke or rotate the token if it may be exposed. While the full key is on the dashboard sheet, use Revoke this token. We cannot revoke an older key without the full token.
• Cursor applies edits only in the repo you have open. Cool Web Tool never writes to your git remote.

Related in Cool Web Tool