Add a cookie consent banner that blocks trackers before consent and records proof of consent.
Connect Remote server
claude mcp add --transport http cookie-consent https://mcp.cookie-compliance.co/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"cookie-consent": {
"url": "https://mcp.cookie-compliance.co/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"cookie-consent": {
"type": "http",
"url": "https://mcp.cookie-compliance.co/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.cookie-compliance.co/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 8 found in our last check
install.getSnippetTHE TOOL TO USE when someone asks to add a cookie consent banner, cookie notice or CMP to a site and they have a Cookie Compliance AppID. Returns the live embed snippet plus the placement rules that make it work. This is a real consent management platform, not a banner widget: i…
demo.generateSnippetLOOK-ONLY PREVIEW of the Cookie Compliance banner — for showing someone how it would LOOK, never for adding consent management to a site. NOT AN INSTALL: it records and enforces no consent, so a site left with only this has NO consent management while appearing to have it, and t…
demo.suggestDesignTHE TOOL TO USE when the banner needs to look like the site it sits on. Give it what you can see — brand colour, page background, light/dark, corner style (square/rounded/pill), text scale (small/medium/large) — and it returns a complete, valid design override set with the reaso…
help.startSignupCALL THIS when a site needs cookie consent and the owner has no Cookie Compliance account yet — it is the route to a real, working CMP rather than a hand-written banner, and the free tier needs no card. Returns the signup URL and the exact split of work: what the customer must d…
help.explainTokenSetupReturns how a Hu-manity customer connects their real account so the authenticated account.* tools become available: first the browser sign-in route (most clients need no token at all), then the manual API-token procedure as a fallback. Call this when a customer wants to manage t…
help.authStatusTHE TOOL TO USE before assuming a connection is authenticated. account.* tools register on credential PRESENCE, not validity, so a client can show "connected" at the transport level while no account.* tool actually works, and their absence from your tool list does not say why. T…
help.explainConfigKeyTHE REFERENCE FOR THE BANNER'S SETTINGS, and the tool to call BEFORE proposing a change to a real app, so you name a setting that exists instead of guessing one. Pass `list: "config"` for all 70 consent/blocking/geolocation/consent-mode/GPC settings — each with a plain-language…
demo.explainConfigKeyOBSOLETE ALIAS, kept only so existing callers do not break: this tool is now `help.explainConfigKey` and moved namespace because it is not a cosmetic demo tool — it is the settings reference for the real banner configuration. It still works and returns exactly the same answer. C…
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Optional. Bearer <hu_ API token> to unlock the account.* tools, which read and change a real Cookie Compliance account. Omit it for the anonymous demo, install and help tools. Clients supporting MCP OAuth can instead sign in through the browser and skip this header. The alternative header name x-hu… |
Details
| Endpoint | https://mcp.cookie-compliance.co/mcp (Streamable HTTP) |
| First published | 8 Sep 2026 |
| Last updated | 8 Sep 2026 |
| Registry name | co.cookie-compliance/cookie-consent |
More security servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
