MCP for Cookies Policy Notification Bar Pro is a Pro add-on for MCP for J that adds 12 tools for the features Web357 sells as Cookies Policy Notification Bar PRO: cookie blocking rules, consent logs with summaries and CSV export, GeoIP checks, texts in every site language, and settings import and export. It needs CPNB PRO itself on the site, which is a separate purchase from Web357. Every tool except one refuses on the free edition. It's the companion to the free MCP for Cookies Policy Notification Bar add-on, which covers the bar, its categories, cookie declarations and default-language texts.
Why this exists
The PRO features are the ones that do the real consent work. Blocking rules decide whether your analytics script waits for a visitor's yes. Consent logs are your record of who agreed to what. GeoIP decides who sees the bar at all. They're also the features that are hardest to check from the dashboard. Is Google Analytics really held back until someone accepts? What share of visitors accept analytics cookies? Would a visitor from Canada see the bar? This add-on lets you ask those questions in a sentence, and it gives you the same tools to roll one site's whole CPNB setup out to the next.
Free, PRO, and which add-on you need
Cookies Policy Notification Bar comes in a free edition and a PRO edition. Web357 describes PRO as adding cookie blocking, consent logs, GeoIP targeting, multilingual texts and settings import/export. Everything else, from the bar itself to the categories, declarations and default-language texts, is in both. The two Cybersalt add-ons split along that same line.
| Cookies Policy Notification Bar feature | Web357 edition | Covered by |
|---|---|---|
| The bar: position, timers, overlay, colours, buttons, consent cookies, Cookies Manager, menu visibility | Free and PRO | The free MCP for Cookies Policy Notification Bar |
| Cookie categories and cookie declarations | Free and PRO | The free add-on |
| Texts in the site's default language | Free and PRO | The free add-on |
| Cookie blocking: scripts, third-party script URLs and page elements held back until consent | PRO only | This Pro add-on |
| Consent logs, with summaries and CSV export | PRO only | This Pro add-on |
| GeoIP targeting | PRO only | This Pro add-on |
| Texts in additional languages | PRO only | This Pro add-on |
| Settings import and export | PRO only | This Pro add-on |
The free add-on works on either edition. On a PRO site, its set_cpnb_config tool also changes the PRO switches and lists, such as turning cookie blocking or consent logging on and setting the GeoIP country lists, and the tools here work with those settings rather than duplicating them. So install the two together. They never share a tool name, so running both is safe. On a free CPNB site, the free add-on refuses those PRO settings and every tool here except the status tool refuses too.
Web357 no longer offers the free edition as a download, so if you're installing Cookies Policy Notification Bar on a new site today, you're buying PRO anyway.
Two gates, and the second one is Web357's
There are two separate things between you and these tools.
The first is ours. This package needs a Cybersalt Pro membership to download, and the catalog enforces that.
The second is Web357's. When Web357 packages the free edition, it strips the PRO code out. But the settings JSON and the consent-log table exist on both editions, so these tools could easily have been written to work on a free site. They weren't. Each one reads the edition the same two ways CPNB's own code does, from the manifest and from the PRO flag its dashboard uses, and refuses on the free build with an explanation and a link to Web357. Paying us for a membership doesn't entitle anyone to someone else's paid features. If you're on the free edition, a Cybersalt membership alone won't make these tools run. You also need CPNB PRO from Web357.
One tool is deliberately not gated. get_cpnb_pro_status exists to tell you why the others are refusing, so gating it would be a trap. On a PRO site it also gives you the lay of the land: whether cookie blocking is switched on and how many rules exist, how many consent-log entries there are and how long they're kept, the GeoIP state and the age of CPNB's bundled GeoIP database, and whether the free add-on is installed alongside.
What Claude can do
There are 12 tools. The free add-on carries the other 14.
| Area | Tools | What you can do |
|---|---|---|
| Status | 1 | What this add-on can and can't do on this site, and why. Never gated. |
| Cookie blocking | 3 | List, add or update, and remove all three kinds of blocking rule: scripts CPNB injects only after consent, third-party script URLs held back until consent, and page elements such as embedded maps or videos removed until consent. |
| Consent logs | 3 | List consent decisions with filters, summarise a period with the acceptance rate for each cookie category, and export the log as CSV in pages. |
| GeoIP targeting | 1 | For any IP address, work out the country and continent the way CPNB does and say whether that visitor would see the bar, naming the rule that decided. |
| Multilingual texts | 2 | See which texts are missing or still untranslated in each active language, and set texts for any active language. |
| Import and export | 2 | Export the whole configuration as JSON and import it into this site or another one, with a dry run by default. |
Installing it
You'll need Joomla 5 or 6, PHP 8.2 or later, MCP for J, the free MCP for Cookies Policy Notification Bar add-on alongside it, and Cookies Policy Notification Bar PRO 5.x, which you buy from Web357. On the free edition of CPNB, every tool here except the status tool refuses by design.
- Subscribe on the sign-up page, or get this and every other Pro add-on with MCP for J Pro โ All Access.
- Download the ZIP and install it through System โ Install โ Extensions, or paste your download URL into Install from URL.
- That's the whole install. The plugin enables itself, and the tools show up in your connected AI client the next time it lists them.
There's no admin screen for this plugin, by design. If the tools come back refusing, run get_cpnb_pro_status first. It tells you which of the two gates you're standing behind.
Using it
Ask for what you want in plain language. "Hold back the Google Analytics snippet until visitors accept analytical cookies" adds a script rule to that category. "What share of visitors accepted analytics cookies last month?" runs the consent summary. "Would a visitor from this IP address see the bar?" runs the GeoIP check. "Which texts are still missing in French?" lists the gaps. "Export this site's cookie bar setup so I can apply it to the new client site" gives you the JSON, and the import on the other site shows you exactly what would change before anything is written.
A few of CPNB's habits are worth knowing about, and the tools tell you about each one when it applies:
- URL and element blocking rules do nothing while CPNB's global Block Cookies switch is off, and a script rule in a disabled category never runs. The rule list reports both.
- CPNB only ever checks the first GeoIP list that has something in it, in the order include continents, exclude continents, include countries, exclude countries. If you set a continent list and a country list, the country list is ignored. None of them apply unless GeoIP is switched on.
- CPNB's bundled GeoIP database dates from November 2018, and CPNB has no way to update it. The status tool reports its age.
- CPNB logs every Decline as "partial" on its Consent Logs screen, because it records the required cookies as accepted on every decision. Its own "declined" filter still counts those rows as declined. The status filter here returns the same rows CPNB's screen does, and each entry's own consent state leaves the locked required category out, so a Decline reads as declined.
- A language with no saved text doesn't fall back to another language's text. It falls back to the plugin's language-file default, which is why the translation status tool lists what's missing.
- CPNB 5's settings import merges, so settings not in the file keep their current values. A list that is in the file, such as categories or blocking rules, replaces the site's list whole. The dry run shows you which.
Its own settings save can wipe the configuration
If CPNB's system plugin is disabled, CPNB's own settings save starts from an empty set of settings and writes back only what you just changed. In testing, one save took the configuration from 434 settings down to 2, and the dashboard still looked normal afterwards. The writes in this add-on use the same protection as the free add-on. They read the stored settings from the database themselves and hand them to CPNB's model, so a save keeps everything you didn't touch, and every result is read back from the database before it's reported.
Permissions and security
Consent logs are personal data, and the tools treat them that way. IP addresses come back masked unless you ask for them in full. The summary returns no personal data at all. The CSV export contains full IP addresses, so it needs the component's Admin permission, exactly as CPNB's own export button does. Everything else needs Manage, the same as CPNB's dashboard. Export your logs before you ever uninstall or reinstall CPNB, because its uninstaller drops the log table.
A script blocking rule runs its JavaScript on every page once a visitor accepts its category, so writing one needs an explicit allow_custom_code confirmation. Importing a settings file that changes custom JavaScript, custom CSS or script rules needs the same confirmation.
How it was tested
This is version 1.0.0. It was tested end to end against Cookies Policy Notification Bar 5.1.2 PRO on Joomla 6.2, including real consent decisions made in a browser and an export and import round trip. It hasn't yet been tested on a site with a second active language, so if you use the multilingual tools on one, I'd like to hear how it goes.
Open source
GPL-2.0-or-later, the same license as Joomla itself. The full source is in the ZIP you download.
Add comment