Feature requests

It is 2026, so an official MCP server is required, instead of the API. Please set up your MCP server to use it with AI agents. Thank you!

Hi CookieScript Support, We use CookieScript in CCPA mode and would like the banner to: Remain visible until the user clicks the X, including when navigating between pages. Stay closed after clicking the X, including on subsequent pages and visits. Preserve the user’s current cookie preferences, without treating the X as “Accept all” or “Reject all.” Is this possible through the existing settings, or would it require custom code? Please advise on the recommended setup and how long the dismissal can be remembered. Thanks, Dan

When coping existing container, besides Privacy Policy URL also allow to change the Banner name and Parent domain settings

Currently, the “Apply to all websites with this item” feature only affects items that already exist at the time the action is performed. Newly discovered matches added later do not inherit the applied configuration, resulting in inconsistent behavior and additional manual maintenance. Expected behavior: The applied configuration should persist as a rule for this item and automatically apply to both: existing matches future matches discovered later This would make the feature behavior more intuitive and ensure consistency over time.

Safari blocks CookieScript when Content Blockers setting is enabled on iPhone 15

CookieScript is blocked on Safari when Content blocking (a setting that disables ads for example) is enabled. I see cookie banners from other providers on different websites. The device is an iPhone 15 with iOS 26.6.1 You should probably investigate the issue and maybe contact Apple - maybe they are overextending the blocking behavior to CookieScript.

For security reasons I would like 2FA added to my account.

Request to extend the API to add/edit/delete cookie vendors and manage translations - this will simplify deployment automation and synchronization across projects.

Safari blocks CookieScript when Content Blockers setting is enabled on iPhone 15

When a banner has several languages, the language picker shows a flag next to each one. Portuguese gets Portugal's flag, with no way to change it. Our site serves Brazilian Portuguese. The page declares lang="pt-BR", the copy is Brazilian, and CookieScript's auto-detect resolves pt-BR to the Portuguese banner correctly. But the flag it then draws is Portugal's, so detection and display disagree: the tool reads the region code to pick the language and then ignores it when picking the flag. CookieScript support confirmed on 21 September 2026: "there are no settings available for customizing the flag displayed for specific language-region codes (like pt-BR)", and that the only route is custom CSS or script modification. Request, either would solve it: (a) a per-language flag field in the account, or (b) support language-region codes as distinct banner languages (pt-BR and pt-PT, es-419 and es-ES, en-US and en-GB), each with its own flag and text. Why it matters beyond aesthetics: a flag is an identity claim about who the text is for. Showing Portugal's flag to a Brazilian audience says the content is European Portuguese, which is a different market and a different variety. The same applies to Spanish shown on Spain's flag to Latin American readers. On a site with regulatory exposure the wrong market signal is not only a cosmetic problem.