Why Won't AI for Cursor

The Why Won't AI integration for Cursor is a remote MCP server that gives Cursor's agent the same checks as whywontai.com. It can tell you which of 17 search and AI crawlers your robots.txt allows, scan your live site, and list issues next to the code that causes them.

What you can do

• check_robots No key

  Which of 17 search and AI crawlers a site's robots.txt allows, with the rule that decides each one.

• scan_site API key

  Starts a full AI visibility scan of a site on your plan.

• get_scan API key

  Score, category scores, technical health, Domain Rating and top issues. Can wait for the scan to finish.

• list_issues API key

  Every issue from a scan, most severe first, with example URLs.

• list_scans API key

  Your recent scans.

Set it up

Cursor reads MCP servers from mcp.json. Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one project. Leave out headers to use check_robots only.

{
  "mcpServers": {
    "whywontai": {
      "url": "https://mcp.whywontai.com/",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

1. Create a free account, open your dashboard, and choose MCP & API to create a key. The key is shown once, so copy it before you close the box.
2. Add the block above to mcp.json, with your key in place of YOUR_API_KEY.
3. Open Cursor Settings, go to the MCP section, and check that whywontai shows its five tools.

Check that it works

In the agent chat, ask: "Use whywontai to check robots.txt for my site." Then: "Scan my site with whywontai and show me the issues on the pricing page."

Limits

• Without a key, check_robots allows 30 checks a day.
• Scans use your plan's scan and page limits, the same as scans you start on the website.
• A scan takes about 1 to 5 minutes. The tools read your public pages only and do not change your site.

Questions