# Use Royal MCP with Complianz
> How Claude, ChatGPT and other AI agents use Royal MCP's seven Complianz tools to review your consent setup, find cookies without a description, and change banner texts and cookie descriptions with undo.
- Canonical:
- Last updated: 2026-11-05
- HTML version:
---
Complianz runs the cookie banner and the legal documents on many WordPress sites. With Royal MCP, an AI agent such as Claude or ChatGPT can check that setup for you, find the cookies that still have no description on your cookie policy, and rewrite banner texts or cookie descriptions in plain language. Every change comes with an undo token. This guide explains the seven Complianz tools, what they deliberately leave alone, and how to keep each change under your control.
## Before you start
The Complianz tools are part of the free Royal MCP plugin from version 1.5.11. They appear in your AI client automatically once Complianz is active on the site; there is nothing to switch on in Royal MCP.
- **Complianz must be active**, free or premium. If it is not, every Complianz tool answers “Complianz is not active”.
- **The Complianz wizard should have been completed at least once.** Until it has, Complianz has no cookie banner, and the banner tools say so.
- **The account your AI client signed in with needs Complianz’s own permission**, the `manage_privacy` capability that Complianz checks on its own settings screens. If the account cannot open Complianz in wp-admin, the AI client cannot use these tools either.
- **An AI client connected to Royal MCP.** If you have not done this yet, follow [Connect Claude](https://royalplugins.com/support/royal-mcp/connecting-to-claude/) or [Connect ChatGPT](https://royalplugins.com/support/royal-mcp/connecting-to-chatgpt/) first.
## The seven Complianz tools
Five tools only read, and two make changes. You never need to type these names yourself; ask in plain words and the AI client picks the tool. They are listed here so you know what is possible and what to look for in the client’s tool log.
| Tool | What it does | Changes the site? |
| --- | --- | --- |
| `complianz_status` | Your consent setup at a glance: whether the wizard was completed, the regions and consent type (opt-in or opt-out), whether the banner actually shows to visitors, whether cookie database sync is on, how many cookies and services Complianz knows, how many cookies lack a description, and when the documents, the last cookie scan and the last sync happened. | No |
| `complianz_list_cookies` | The cookies Complianz knows, with their service, purpose, retention, function, the personal data they collect, language and sync state. It can show only cookies without a description, only one service, or a name search, and it pages through 50 cookies at a time (up to 100). | No |
| `complianz_list_services` | The services behind those cookies, such as Google Analytics, with their category, whether they share data with a third party, their privacy statement address and how many cookies each has. | No |
| `complianz_get_banner` | A banner’s texts as visitors see them: the title, the opt-in and opt-out messages, every button and the category labels and descriptions, plus the list of banners on the site. | No |
| `complianz_list_documents` | The legal documents per region (cookie policy, privacy statement, imprint and disclaimer): whether each is required, whether Complianz generates it or it is your own page or an outside address, and where it lives. | No |
| `complianz_update_banner_text` | Changes the texts on a cookie banner. Colours, layout and custom CSS are never touched. | Yes, with undo |
| `complianz_update_cookie_description` | Changes how one cookie is described on the cookie policy: its purpose, retention, function and the personal data it collects. | Yes, with undo |
## Check your consent setup
A good first request is simply: *“Check my Complianz setup and tell me whether anything needs attention.”* The AI client reads the status and usually follows up with the document list. It can then tell you, for example, that the banner is switched off for visitors, that the last cookie scan is months old, or that twelve cookies on your cookie policy have no purpose or retention.
The status answer separates two things that are easy to confuse: whether your site *needs* a cookie banner according to the wizard, and whether the banner *shows* to visitors right now. A banner only shows when the wizard has been completed, a banner is needed, and the banner has not been switched off in Complianz.
## Fill in missing cookie descriptions
Cookies without a purpose or retention period leave gaps on your cookie policy. This is the task the Complianz tools help with most.
#### Ask for the gaps
For example: *“List the Complianz cookies that have no description.”* The AI client lists only the cookies with an empty purpose or retention.
#### Review the suggestions
Ask the client to propose a purpose, retention and function for each cookie, and read them before anything is saved. You know your site’s services better than the AI does; correct anything that is wrong.
#### Apply them one cookie at a time
Tell the client to save the descriptions you approved. Each cookie is changed by its ID, and each change returns its own undo token. Purpose, retention, function and collected personal data each accept up to 2,000 characters.
#### Repeat for each language
Complianz keeps a separate row for every language a cookie is translated into. By default the tools show only the main rows; ask for all languages if your cookie policy is translated, and the client can update each row.
Your text and the cookie database sync
Complianz can keep cookie descriptions in sync with cookiedatabase.org. When you change a cookie through Royal MCP, that cookie stops syncing by default, so the next sync does not replace your text. If you would rather keep it syncing, ask the AI client to keep sync on for that cookie; the next sync may then overwrite your wording.
## Change the cookie banner texts
Ask in plain words, such as *“Change the accept button on the cookie banner to ‘Accept all’ and make the deny button say ‘Necessary only’.”* The client reads the banner first, then changes only the fields you named. Every other text stays as it is.
| Part of the banner | What can be changed |
| --- | --- |
| Title | The text, and whether the title is shown. |
| Message | The opt-in and the opt-out message, up to 5,000 characters each. Links, bold, italic, paragraphs and line breaks are kept; other HTML is removed. |
| Buttons | Accept, accept (informational banners), deny, view preferences, save preferences and the button that reopens the banner later. The deny button can also be shown or hidden. |
| Categories | The labels and descriptions of the functional, preferences, statistics and marketing categories. Most of them can also be shown or hidden. Labels and button texts take up to 500 characters. |
If the site has more than one banner, the client can name the banner by its ID; otherwise it changes the default banner. Visitors see the new text on their next page load. If your site uses a page cache, clear it so cached pages pick up the change.
## What the Complianz tools never do
Some parts of Complianz are left out on purpose, because a mistake there would change your legal position or run code on every page:
- **Script Center scripts** are not offered, because they run JavaScript for every visitor.
- **Wizard answers** other than banner texts are not changed, because they decide what your legal documents say. Change those in the Complianz wizard.
- **Custom CSS, colours and layout** of the banner and documents stay as they are, and settings are never reset.
- **Data requests and consent records** hold personal data about your visitors and are never read.
- **Company contact details and stored credentials** are never returned to the AI client.
Legal documents can be listed but not edited. To change what a document says, use the Complianz wizard or edit your own page.
## Undo and other safety controls
Both Complianz write tools return an undo token. To reverse a change, ask the AI client to undo it; it passes the token to `mcp_undo_last_operation`, and the earlier texts are put back. Tokens work once and last 72 hours by default. If the same banner or cookie was changed again after your change, for example in the Complianz screens, undo refuses rather than overwrite that later edit.
Every change also appears under **Royal MCP > Recent Changes**, where you can open it to see the value before the change, the value it wrote, and the value now.
- **Read-only mode** (Royal MCP > Settings, under “What AI clients may do”) refuses both write tools, while all five reads keep working. It is a safe way to let an AI client audit your consent setup without changing it.
- **Drafts only** also refuses both write tools, because banner texts and cookie descriptions are live on the site the moment they are saved.
- **Per-connection access levels** on Royal MCP > Connected Clients let you give one AI client read-only access while another keeps full access. See [Who can connect AI clients and what they may do](https://royalplugins.com/support/royal-mcp/who-can-connect-ai-clients/).
## Troubleshooting
### “Complianz is not active”
Complianz is deactivated or not installed on this site. Activate it under Plugins, then ask again.
### “You do not have permission to use Complianz tools.”
The account your AI client signed in with does not have the permission Complianz requires. Sign the AI client in again with an account that can open the Complianz screens, usually an administrator.
### “Complianz has no cookie banner yet; finish its wizard first.”
Complianz creates its banner at the end of the wizard. Complete the wizard once in wp-admin, then try again.
### “The cookie banner is switched off in Complianz settings.”
Banner texts can only be changed while the banner is switched on. Switch it on in Complianz first, then change its texts.
### “Complianz has not set up its cookie tables yet”
Complianz creates its cookie tables the first time its admin screens load. Open Complianz in wp-admin once, then ask again.
### A cookie description changed back on its own
The cookie was still syncing with cookiedatabase.org, which happens when it was saved with sync kept on or changed in Complianz afterwards. Ask the AI client to save the description again without keeping sync.
### Visitors still see the old banner text
A page cache is most likely serving pages saved before the change. Clear your caching plugin’s cache, or your host’s, and reload in a private window.
## Frequently asked questions
### Can the AI client change my cookie policy or privacy statement?
No. Royal MCP can list your legal documents and where they live, but it cannot change what they say. It can change cookie descriptions, which appear on the cookie policy, and the texts on the cookie banner.
### Can the AI client turn the cookie banner off or change the consent type?
No. Those are wizard answers that decide your legal setup, and Royal MCP leaves them to the Complianz wizard. The AI client can tell you how they are set, but not change them.
### Does Royal MCP read consent records or data requests?
No. They hold personal data about your visitors, so the Complianz tools never read them.
### How do I undo a banner text change?
Ask the AI client to undo it. It uses the undo token from the change, which works once and lasts 72 hours by default. If the banner was changed again since, undo refuses so that later edit is not lost.
### Which version do I need?
Royal MCP 1.5.11 or later, with Complianz active.
## Related
[Settings
Who Can Connect AI Clients
Roles, access levels, read-only mode and drafts only.](https://royalplugins.com/support/royal-mcp/who-can-connect-ai-clients/)
[Safety
Safety and Recovery
How undo, Recent Changes and the Activity Log fit together.](https://royalplugins.com/support/royal-mcp/safety-and-recovery/)
[Back to Royal MCP Support](https://royalplugins.com/support/royal-mcp/)
[TablePress Tools](https://royalplugins.com/support/royal-mcp/tablepress-tools/)