CookieYes manages website cookie consent and privacy compliance across GDPR, CCPA, and other regulations. Scan websites for cookies and trackers, configure consent banners, customize cookie categories and policies, manage consent records, and monitor compliance settings across websites.
Codex is OpenAI's coding agent for the terminal. It reads MCP servers from its config and signs in to remote ones with OAuth.
This guide connects CookieYes MCP to Codex through MewCP, so Codex can use CookieYes MCP's 10 tools, like list_domains, get_website_details and list_banners, without your CookieYes MCP credentials ever reaching the app.
CookieYes MCP signs in through managed OAuth. MewCP stores the token encrypted, refreshes it before it expires and injects it only at call time. Your agent never holds it, so it can never leak it.
More apps
CourtListener provides searchable access to U.S. case law, court opinions, dockets, judicial decisions, and legal filings. Find cases by citation, keyword, court, or judge; retrieve opinion texts and docket records; and research legal precedents using data from federal and state courts.
Ask your AI whether you're owed money from a class action. Redra is a free, read-only remote MCP server that searches current class-action settlements.
ConsentStack automates website cookie consent management by creating and publishing consent banners, configuring privacy settings, detecting and categorizing tracking scripts, running compliance scans, and reviewing consent analytics and logs for GDPR and other privacy regulations.
SecondAppraisal helps AI agents assist vehicle owners with total-loss insurance claims by estimating fair market value, comparing similar vehicle listings against insurer offers, uploading valuation reports, checking state-specific appraisal rules, and submitting appraisal consultation requests.
Other clients
CookieYes MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact CookieYes MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
Run this and approve access in the browser window.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
Returns all domains registered under the account with their banner and compliance status. When presenting results, refer to websites by their URL, not by internal ID. Never expose organisation IDs or website IDs to the user — these are for internal tool use only.
Get details for a specific website by ID.
Get all cookie consent banners configured for a website. Returns banner ID, name, law, status, layout type, position, and theme. Use this to find banner IDs before updating colours or position. When presenting results, refer to banners by their applicable law (GDPR/CCPA), not by internal ID.
Check whether the CookieYes cookie consent banner is live and active on a website. Use this when the user asks 'Is my banner live?', 'Is my banner active?', 'Is my banner working?', 'Why is my banner not showing?', or any question about whether the banner is currently deployed and detected on their site. Returns the banner deployment status, when it was last detected, and whether it has been manually disabled or disabled due to pageview limits. When presenting results, refer to the website by URL, not ID.
Get the JavaScript embed code (script tag) to install the CookieYes cookie consent banner on a website. Use this when the user asks how to install CookieYes, what code to add, or needs their embed snippet. When presenting results, refer to the website by URL.
Update the theme or colour scheme of the CookieYes cookie consent banner for a website. Changes are automatically published live. If the user wants a full theme change, present FOUR options: Light, Dark, Auto-generated, or manual custom colours. Use 'theme=light' or 'theme=dark' for preset themes, and use 'theme=recommended' for the Auto-generated option from the dashboard. If the user chooses manual custom colours, do NOT offer only a short generic list. Offer the actual colourable elements for that law. GDPR manual-colour options: banner background, banner border, title text, body text, Accept button, Reject button, Customise button, Cookie Policy link, Preference Center toggle enabled, Preference Center toggle disabled, Save My Preferences button, Google Privacy link, Revisit Consent button, Blocked Content background, Blocked Content border, Blocked Content text. CCPA manual-colour options: banner background, banner border, title text, body text, Do Not Sell link, opt-out checkbox enabled, opt-out checkbox disabled, Cancel button, Save My Preferences button, Revisit Consent button, Blocked Content background, Blocked Content border, Blocked Content text. When the user picks a button or link, ask which parts to change if needed: background, border, text. Any individual colour edit automatically saves the banner theme as custom. When presenting results, refer to the banner by its law (GDPR/CCPA), not by ID. All colour values sent to this tool must be in hex format: #fff or #ffffff. If the user provides a colour in any other format (name, rgb, rgba, hsl), convert it to hex before calling this tool. PLAN CHECK: Before offering theme or colour options, check the website's plan from list_domains. If the website is on a Free plan, only offer Light and Dark themes — do NOT offer Auto-generated or manual custom colours, as these require a paid plan. Inform the user that custom colours are available on paid plans. IMPORTANT: Before making any changes, ALWAYS ask the user to confirm: (1) which website if they have multiple domains, (2) which banner (GDPR, CCPA, or both) they want to update. NEVER assume or auto-select banners. Even if there is only one website or one banner, confirm with the user before proceeding. NEVER update multiple banners in a single action without explicit user approval for each one.
Update the layout, position, and preference center style of the CookieYes cookie consent banner. Changes are automatically published live. Layout options: Box (small corner widget), Banner (full-width strip), Popup (centered modal, GDPR only, requires Pro plan). Position: for Box ask user to pick a corner, for Banner ask top or bottom, for Popup do not ask (always center). Preference center: for Box or Popup offer Center and Sidebar only. For Banner offer Center, Sidebar, AND Push down. If user selects Banner with Push down, the banner uses a special full-width layout where the preference center pushes page content down (GDPR only). When presenting results, refer to the banner by its law (GDPR/CCPA), not by ID. IMPORTANT: Before making any changes, ALWAYS ask the user to confirm: (1) which website if they have multiple domains, (2) which banner (GDPR, CCPA, or both) they want to update. NEVER assume or auto-select banners. Even if there is only one website or one banner, confirm with the user before proceeding.
Get the results of the most recent completed cookie scan for a website. Returns scan status, pages scanned, and cookies found grouped by category. Use this to answer questions about what cookies a site uses or scan history. When presenting results, refer to the website by URL.
Get the compliance configuration status for a website. Returns which privacy laws are enabled (GDPR, CCPA, etc.), geo-targeting settings, and IAB framework status. Use this to answer questions about a website's compliance setup. When presenting results, refer to the website by URL.
Starts a new cookie scan for a website and returns a compact scan-start summary (scan ID, scan type, page limit, and any include/exclude URLs applied). The scan runs asynchronously — use get_scan_results to read the outcome once it completes. Two scan types are supported: 'normal' crawls the site up to the plan's scan limit, and 'custom' scans only an explicit list of URLs. The plan's scan limit comes from get_website_details, so that tool must be called first to obtain the pageLimit value for a normal scan. A custom scan fails if includeUrls is empty.
