CookieYes MCP Server

Last updated on April 20, 2026

The CookieYes MCP Server lets third-party AI assistants such as Claude securely access your CookieYes account, allowing you to manage cookie consent and compliance workflows using natural language, without needing to navigate the dashboard.

Once connected, you can:

1. Monitor: Check banner status, verify configuration, and retrieve a list of banners across your domains.
2. Implement: Retrieve and validate banner embed codes for any domain.
3. Customise: Update banner colours, position and layout to match your website’s design.
4. Scan: Trigger cookie scans, detect cookies in use and review scan results.
5. Manage: List all domains in your account and perform actions scoped to a specific domain.

---

The CookieYes MCP Server gives Claude a set of tools to interact with your account. Tools are either read-only (retrieve data, no changes made) or write (create, update, or trigger actions). Claude will ask for confirmation before running any write tool.

Category	Tool	Type	Description	Example Prompts
Domains & Setup	list_domains	Read-only	List all websites in your CookieYes account	– Show all my sites. – Which of my sites have an inactive banner?
	get_website_details	Read-only	Get detailed configuration for a specific domain.	– List my website details. – Show me the details for example.com.
	get_embed_code	Read-only	Get the JavaScript install code for your site	– Give me the installation code for my site. – How do I install CookieYes?
Banner Management	list_banners	Read-only	List all consent banners configured on a domain	– Show me all my banners. – Which banners are active on my site?
	get_banner_status	Read-only	Check if your cookie banner is live and active	– Is my banner live? – Is the installation code added to my site?
	update_banner_colours	Write/delete	Update banner theme and colours	– Change my banner on example.com to dark theme. – Set the accept button to navy blue.
	update_banner_layout	Write/delete	Change banner layout, position, and preference center style	– Move my banner to the bottom right – Change my banner position to top left.
Compliance & Scanning	get_scan_results	Read-only	View latest cookie scan results by category	– What cookies are on my site? – Show me all third-party trackers on example.com.
	get_compliance_status	Read-only	Check which privacy laws and geo-targeting are enabled	– Is my site GDPR compliant? – What regulations am I covered for?
	trigger_cookie_scan	Write/delete	Start a new cookie scan on your domain	– Run a new scan on my site – Scan my website for cookies.

---

Follow these steps to connect your CookieYes account to Claude. This includes authentication, permission authorisation and connection confirmation.

Step 1: Open Connector Settings

In your Claude account, click the Customize icon in the left sidebar, then select Connectors.

Step 2: Add a Connector

On the Connectors page, click the + (Add) icon in the top-right corner.

Step 3: Find the CookieYes Connector

Search for “CookieYes” and select the CookieYes connector from the results.

Step 4: Start Connection

Click Connect and you’ll be redirected to the CookieYes authentication flow.

Step 5: Sign In to CookieYes

Log in to your CookieYes account, or sign up if you don’t have one.

Step 6: Review Permissions & Authorise

The CookieYes authorisation screen displays the permissions granted to Claude. Review the access details, then click Allow to complete the authorisation process.

Step 7: Connection Successful

After authorisation, a confirmation modal will appear: “Your CookieYes account is now connected to Claude”.

Step 8: Open Claude to Complete the Connection

If you are using the Claude.ai, you will be redirected back to Claude automatically after completing the connection.

If you are using the Claude desktop app, a confirmation screen will appear. Click Allow to return and start using the connector. Once redirected, the CookieYes connector will be ready to use.

---

After connecting the CookieYes connector, you can manage its tool permissions and configure its behaviour directly from the Claude Settings page. This section walks you through the configuration options available in the connector settings.

You can access the CookieYes connector settings at any time after connecting. The settings page lets you review tool permissions and uninstall the connector if needed.

Step 1: Open Connector

Click the Customize icon in the left sidebar, then select Connectors. You’ll see all connectors in your account.

Step 2: Locate CookieYes

Scroll down to find CookieYes listed as a connector.

Step 3: Set Tool Permissions

On the Connector page, you’ll see all available tools grouped as Read-only tools and Write/delete tools. Use the toggle icons next to each tool to set its permission mode.

Permission Modes

Each tool can be set to one of three modes using the toggle icons on the settings page:

Mode	Behaviour
Always Allow	Claude runs the tool automatically. No confirmation required. Recommended for read-only tools.
Needs approval	Claude will ask for your confirmation before running this tool each time. Recommended for write tools.
Blocked	Claude cannot use this tool at all. Use this to restrict access to tools you do not need.

---

The CookieYes MCP server uses OAuth 2.0 to connect Claude to your CookieYes account. When you connect, CookieYes issues Claude a secure, scoped access token. Claude uses this token for all tool calls. Your CookieYes password is never shared with Claude at any point.

The MCP server is available to all CookieYes account types, including the Free plan. No paid CookieYes subscription is required to connect. However, some tools are subject to usage limits based on your plan; for example, the number of cookie scans you can trigger per domain per month increases on paid plans.

Access is limited to your CookieYes account. Claude cannot access other CookieYes accounts, and the authorisation token cannot be used outside the available MCP server tools. You can revoke access at any time from Settings > Connectors > CookieYes > Disconnect.

---

The following examples show how to perform common CookieYes tasks using natural language prompts and what happens behind the scenes.

1. Check banner status

User prompt: “Is my banner active?”

What happens:

• If multiple domains exist, you’re prompted to select a domain
• The server retrieves the banner installation and display status
• Returns whether the banner is active or inactive
• Suggests retrieving the install code if the banner is not detected.

2. Discover cookies on your site

User prompt: “Scan my site for cookies”

What happens:

• If multiple domains exist, you’re prompted to select a domain
• The server checks scan availability for the selected domain
• Requests confirmation (if required) before starting the scan
• Initiates a cookie scan
• Returns scan status (e.g., queued or in progress)
• Allows you to retrieve results once the scan is complete

3. Update banner appearance

User prompt: “Change my banner to dark theme”

What happens:

• If multiple domains exist, you’re prompted to select a domain
• The server validates the requested change
• Requests confirmation before applying the update
• Updates the banner configuration
• Applies changes immediately and makes them visible on your website

4. Check compliance configuration

User prompt: “Check my GDPR configuration”

What happens:

• If multiple domains exist, you’re prompted to select a domain
• The server retrieves the consent template and geo-targeting settings
• Returns applicable regulations (e.g., GDPR, CCPA)
• Confirms banner installation status
• Includes a note that this is a configuration check, not legal advice

5. Monitor multiple domains

User prompt: “Which of my sites have inactive banners?”

What happens:

• The server retrieves all domains in your account
• Returns banner status for each domain
• Highlights domains with inactive or missing banners
• Allows you to select a domain for further actions

6. Customise banner layout

User prompt: “Make my cookie banner less intrusive”

What happens:

• If multiple domains exist, you’re prompted to select a domain
• The server retrieves the current banner configuration
• Requests confirmation before applying changes
• Updates layout type, position and preference centre style
• Applies changes immediately and makes them visible on your website
• Returns confirmation with updated layout details

---

1. Why can’t I find the CookieYes connector in Claude?

The CookieYes MCP server is listed under Customize > Connectors. If you can’t find it, try the following:

1. Make sure you’re searching for “CookieYes” the connector may not appear in the default list without searching.
2. Check that your Claude plan supports connectors. Connectors are available on Pro and above.
3. If you’re on a Team or Enterprise plan, your admin may have restricted connector access. Contact your workspace admin to confirm.
4. Try refreshing the page and searching again.

2. I clicked Connect, but nothing happened. What do I do?

This is usually a browser or pop-up issue. Try the following:

• Check if your browser blocked a pop-up. The CookieYes login screen opens in a new window; allow pop-ups for claude.ai and try again.
• If you are on the desktop app, check if a confirmation alert appeared behind the main window.
• Try a different browser or disable any browser extensions that may be interfering.
• Clear your browser cache and cookies, then try connecting again.

3. I’m getting an authentication error when using the CookieYes MCP server. How do I fix it?

An authentication error means Claude’s access token for your CookieYes account is no longer valid. To fix it:

1. Go to Customize > Connectors > CookieYes.
2. Click Disconnect to remove the existing connection.
3. Go back to Connectors, find CookieYes and click Connect.
4. Complete the OAuth flow again and log in to CookieYes.

This generates a fresh access token and restores the connection.

4. My session expired. Do I need to reconnect?

Yes. The OAuth access token Claude uses to communicate with CookieYes has an expiry. When it expires, Claude can no longer make tool calls on your behalf.
To reconnect:

1. Go to Customize > Connectors > CookieYes.
2. Click Disconnect, then reconnect by following the setup steps.

Your CookieYes data, banners and configurations are not affected by the session expiry.

5. I disconnected and reconnected but my data isn’t showing. Why?

After reconnecting, Claude starts a fresh session with no prior context. Try the following:

• Ask Claude to list your domains first . for example, “Show all my domains” , so it can re-establish context.
• If you have multiple domains, you will be prompted to select one before any tool calls are made.
• If a specific tool is returning no data, check that it is not set to blocked in the connector page under Customize > Connectors > CookieYes.

6. The Configure button is not visible. What do I do?

The Configure button only appears for MCP server that are already connected. If you cannot see it, the connector may not have been set up yet. To check:

• Go to Customize > Connectors and look for CookieYes in the list.
• If it is not there, the connector has not been connected yet. Click + (Add) icon, search for CookieYes and follow the setup steps to connect.
• If CookieYes appears in the list but shows no Configure button, try refreshing the page.
• If the issue persists, disconnect any partial connection and reconnect from scratch.

7. Claude said my request failed or an action is not permitted. Why?

A request may fail or be blocked for several reasons. Claude usually indicates the cause in its response. Details are outlined below:

• Your email is not verified on CookieYes: Some actions require a verified email address before they can be executed. If your email is not verified, log in to your CookieYes account, go to your profile settings, and complete the verification. Then return to Claude and try again.
  
• You are on the Free plan and the feature requires a paid plan: Certain CookieYes features are only available on paid plans and cannot be accessed through the MCP server on a Free account. For example, colour customisation for your banner is not available on the Free plan. Claude will display an upgrade prompt when a paid plan is required.
  
• You have reached the usage limit for your current plan: Some tools, such as trigger_cookie_scan, are subject to usage limits based on your plan. If the limit is reached, the request will fail until it resets or you upgrade your plan. Claude will display the reset date and provide upgrade options.
  
• The feature is not available through the connector: Not all CookieYes features are available through Claude. Features such as consent logs, team management, billing, and banner legal text can only be managed in the CookieYes dashboard. This is intentional and ensures data security and compliance.

8. What should I do if I’m not redirected back to Claude automatically?

After authorisation, Claude should open automatically. If it doesn’t:

• Close the browser window.
• Return to Claude manually: open Claude on the web (claude.ai), desktop app or Claude Code, whichever you were using.
• Confirm the connection is active: In Claude, go to Customize > Connectors and check that CookieYes appears as connected.

---

1. What CookieYes data does the MCP server have access to?

The CookieYes MCP server is granted secure, limited access to specific configuration data from your account, only what is required to support the integration.

What Claude can access:

• Domain-level configuration: banner status and settings for your connected domains.
• Your domains and banner configurations: layout, position, colour settings, and compliance template.
• Cookie scan metadata and results: Pages scanned, total number of cookies and total scripts identified in your last scan.

What Claude cannot access or process:

• Personal data (PII), consent logs, or visitor data: individual consent records are never exposed through Claude.
• Cookie values, session data, or user identifiers: only metadata is returned, never the actual cookie values.
• Legal content: your cookie policy text, banner heading, or any legal copy is blocked from flowing through Claude.
• Billing information, account credentials, or team data: payment details, passwords, and team member information are never accessible.

2. Is the CookieYes MCP server for Claude available on the desktop, web, and mobile versions of Claude?

Yes, the CookieYes MCP server is available on the web, desktop and mobile versions of Claude.

3. Does the CookieYes MCP server for Claude support multiple languages?

No, the CookieYes MCP server for Claude does not currently support multiple languages. The connector interface and all tool responses are in English only.

4. How do I disconnect the CookieYes MCP server from Claude?

1. Go to Customize > Connectors > CookieYes.
2. Click Disconnect in the top-right corner.

This immediately revokes Claude’s access to your CookieYes account.

---

The CookieYes MCP Server follows strict data security and privacy standards. Access is managed using OAuth 2.0, and only limited configuration data is available to the connector. Sensitive data such as personal information, consent logs, and cookie values is never exposed.

For more details, refer to the privacy policy:
👉 Privacy Policy – CookieYes

If you need help with setup or troubleshooting, contact CookieYes support:
👉 Contact – CookieYes