What is the CookieYes MCP server?
The CookieYes MCP server from AcrossAI lets Claude, ChatGPT, Cursor and any other MCP client declare cookies, manage consent categories and banner languages, and configure Google Consent Mode on your WordPress site. It runs inside WordPress through the free Abilities Manager and MCP Manager plugins, and works through CookieYes itself — with no third-party relay in between.
Looking for another plugin? Browse all WordPress MCP integrations or the Privacy and Compliance integrations.
What your AI can do with CookieYes
CookieYes decides what your cookie banner says and which consent categories visitors can choose. These abilities let an AI assistant declare and describe cookies, manage consent categories and banner languages, configure Google Consent Mode, and read consent statistics — without ever returning your CookieYes account credentials.
Declare every cookie
List, add and update the cookies shown in the preference centre, with descriptions in every banner language.
Manage consent categories
Rename, describe, reorder and show or hide categories. Strictly-necessary status cannot be changed here.
Configure Google Consent Mode
Switch it on, set defaults and check that the status actually reaches Google.
See consent results
Read accept, reject and partial-consent counts, pageviews and the last cookie scan.
Troubleshooting
Cookie banner not showing what you changed? Three reasons it happens quietly.
Each of these leaves the setting saved while visitors keep seeing the old banner.
The banner needs rebuilding
Changes written straight to the consent tables don’t reach visitors until the banner is rebuilt. get-banner-status shows when it’s waiting.
Consent Mode isn’t reaching Google
A saved setting isn’t proof. get-google-consent-mode-status shows what the consent service actually reports.
A language was removed
Removing a banner language discards its text. set-languages asks for confirm for exactly that reason.
Try asking
Paste one into Claude, ChatGPT or Cursor once your site is connected.
“Which cookies does our banner declare under Analytics?”
“Add the _clck cookie from Microsoft Clarity under Analytics.”
“Is Google Consent Mode on, and is it reaching Google?”
“How many visitors rejected cookies this month?”
“Add Hindi to the cookie banner.”
“When did CookieYes last scan this site?”
AcrossAI vs WPVibe vs Novamira for CookieYes
Three ways to connect an AI assistant to CookieYes. The difference is where the MCP server runs and what sits between your AI and your site.
| AcrossAI | WPVibe | Novamira | |
|---|---|---|---|
| Where the MCP server runs | On your WordPress site | Hosted gateway at mcp.wpvibe.ai | On your WordPress site |
| Third-party relay | None | Every call passes through WPVibe’s cloud | None |
| How it works with CookieYes | Dedicated CookieYes abilities, each labelled read-only, write or destructive | Plugin abilities, REST API and WP-CLI | General PHP access; no dedicated CookieYes specialization listed |
| Designed for | Production sites, with risky changes gated behind confirm | Any host reachable over HTTPS | Dev and staging environments with backups |
| Price | Free, including every CookieYes ability | Free plan with a daily action allowance; paid tiers | Free core; specializations in Novamira Pro |
Based on each product’s own published documentation, September 2026.
CookieYes + AI questions
Is there an MCP server for CookieYes?
Yes. AcrossAI turns your WordPress site into an MCP server with dedicated CookieYes abilities, so Claude, ChatGPT, Cursor or a local model can work with CookieYes directly. It’s free on WordPress.org.
Can ChatGPT or Claude manage CookieYes?
Yes, once your site is connected over MCP. Ask in plain English and your AI calls the CookieYes abilities on this page, with risky changes gated behind an explicit confirm.
Is the CookieYes integration free?
Yes. All of its abilities ship in Abilities Manager, which is free on WordPress.org.
Can the AI see my CookieYes account credentials?
No. Credentials are never returned, and the settings ability only writes a named list of safe settings.
Does declaring a cookie block or allow it?
No. Declaring records what the site uses and shows it in the preference centre. Blocking still depends on the visitor’s consent and CookieYes’s own script handling.
Which AI assistants work with it?
Any MCP client: Claude, ChatGPT, Gemini, Grok, Cursor, Claude Code, and local runtimes such as Ollama, LM Studio and Open WebUI.
Does my site data pass through AcrossAI’s servers?
No. Your WordPress site runs the MCP server and your AI client connects to it directly. There is no hosted gateway in the middle.
Is AcrossAI affiliated with CookieYes?
No. AcrossAI built and maintains this integration independently, using CookieYes’s public APIs.