Step 1: Start the connection from Claude
- Open Claude and go to Customize → Browse Connectors
- Locate CookieYes and click Connect
- You'll be redirected to a CookieYes authentication page in your browser
Step 2: Log in
On the login screen, select Log in & connect to Claude, then enter the following credentials:
These are shared test credentials provisioned for this review. Do not share externally.
Step 3: Review permissions and allow access
You'll be taken to a permissions screen outlining what Claude can and cannot access.
| Access | Details |
|---|
| ✓ Can access | Domain-level configuration (banner status, settings); banner configuration and compliance settings; cookie scan results (categories, counts, detected scripts) |
| ✕ Cannot access | Visitor data, consent logs, and personal information; cookie values, session data, and user identifiers; legal content (cookie policies, banner text); billing details, account credentials, and team data |
| Security & control | Secure OAuth 2.0 connection limited to your account; you can disconnect anytime |
Final action
- Click Allow to complete the connection
- Click Cancel to stop the connection
Step 4: Connection status
If you clicked Allow
You will get a Connection Successful confirmation.
- You'll be automatically redirected back to Claude within 3 seconds
- If not, close the browser tab and return to Claude manually
If you clicked Cancel
You will get a Connection Cancelled message.
- Claude has no access to the account
- No data was shared
Options:
- Close the window
- Click Review permissions again to restart
Need to try again?
To retry the connection anytime, go to Claude → Connector Settings and start from Step 1.
Step 5: Using CookieYes with Claude
Once connected, you can manage your cookie consent setup directly in Claude.
Use cases
The six use cases below cover the full functional scope (text prompts, expected output, and tools used) of the CookieYes MCP integration.
Use case 1: Check banner status
Prompt: "Is my banner active?"
Expected output:
- If multiple domains exist, Claude prompts the user to select one
- Retrieves banner installation and display status for the selected domain
- Returns whether the banner is active or inactive
- If not installed, Claude suggests retrieving the embed code
Tools used:
list_domains → get_banner_status → get_embed_code
Use case 2: Discover cookies on your site
Prompt: "Scan my site for cookies"
Expected output:
- If multiple domains exist, Claude prompts the user to select one
- Checks scan availability for the selected domain
- Initiates a cookie scan; requests confirmation if required
- Returns scan status (queued or in progress)
- Allows the user to retrieve results once the scan is complete
Tools used:
list_domains → get_website_details → trigger_cookie_scan → get_scan_results
Use case 3: Update banner theme
Prompt: "Change my banner to dark theme"
Expected output:
- If multiple domains exist, Claude prompts the user to select a domain and banner type (GDPR/CCPA)
- Validates the requested change
- Requests confirmation before applying the update
- Updates the banner configuration for the selected domain
Themes available:
- Paid plans: Light, Dark, Auto-generated, Custom colours
- Free plans: Light, Dark
Tools used:
list_domains → list_banners → update_banner_colours
Use case 4: Check compliance configuration
Prompt: "Check my GDPR configuration"
Expected output:
- If multiple domains exist, Claude prompts the user to select one
- Retrieves the consent template and geo-target settings for the user-selected domain
- Returns regulations covered (e.g., GDPR and CCPA)
- Includes a disclaimer that this is a configuration check, not legal advice
Tools used:
list_domains → get_compliance_status
Use case 5: Monitor multiple domains
Prompt: "Which of my sites have inactive banners?"
Expected output:
- Retrieves all domains linked to the account
- Returns banner status for each domain
- Highlights domains with inactive banners or missing setup
- Allows the user to select a domain for further actions
Tools used:
list_domains
Use case 6: Customise banner layout
Prompt: "Make my cookie banner less intrusive"
Expected output:
- If multiple domains exist, Claude prompts the user to select one
- Retrieves the current banner configuration
- Requests confirmation before applying any changes
- Updates banner layout type, position, and preference centre style
- Publishes changes to the live banner and returns confirmation of the updated settings
Tools used:
list_domains → list_banners → update_banner_layout