Connect AI

Your agent captures the cookies. CookieComply writes the report.

One access token. The agent opens the live page in its browser tool, grabs cookies before the banner, after Accept, and after Reject, then calls CookieComply for the report. We don't run a browser on our servers.

MCP or plain REST. Cursor, Claude, ChatGPT, Codex, Copilot, Windsurf, and homegrown agents all work the same way.

Already scanning in Chrome? Point the same agent at those scans with a view-only token.

  • Hosted MCP at one URL with a Bearer token
  • Before / Accept / Reject on the page itself
  • Chrome add-on if you'd rather click through yourself

From token to report

Create a token, wire hosted MCP plus a browser tool, capture the three consent states, then validate and analyze.

Access token

cc_live_••••••••••••

Settings → Connect AI

Step 1 · Before · Accept · Reject

Got Cursor or Claude open already?

The connect guide walks hosted MCP, Skills, and a starter prompt. Most people finish the first tool call in under ten minutes.