mcpField
C

Cookie Compliance

Remote
cookie-compliance.coLegal & Government

About Cookie Compliance

Add a cookie consent banner that blocks trackers before consent and records proof of consent

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.cookie-compliance.co/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://mcp.cookie-compliance.co/mcpAuth required

Tools

8
ParameterTypeRequiredDescription
appIDstringYesThe customer's registered Cookie Compliance AppID, e.g. `examplecom-1a2b3c4`. Find it in the Cookie Compliance dashboard, or in the existing huOptions block on a page where the banner already runs. If the customer does not have one yet, call help.startSignup instead — do not invent one.
blockingbooleanNoWhether the widget blocks non-essential scripts and iframes, or ones you mark, before consent (a held file may download but does not run). Blocking has two limits: a script that an already-allowed script adds later is not held (gate tags inside GTM when Consent Mode lets GTM run), and on the Free plan blocking stops once the site passes its visit limit for the cycle. Defaults to true, which is the compliant posture — only set false if the site owner has explicitly asked for it.
globalCookiebooleanNoShare the consent cookie across subdomains. Defaults to false.
currentLanguagestringNoTwo-letter language code for the banner's initial render. Defaults to `en`.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.