Smithery's MCP Proxy and managed identity shut down on October 31. See what's changing
Add GDPR cookie consent to a website with Kindnod...
Kindnod is a hosted consent banner (17 KB, Google Consent Mode v2, script blocking, consent log, Cookiebot-compatible JS API). It installs with no account: the site is provisioned on first page load from a public domain.
Plain HTML (every page, before </head>):
<script src="https://kindnod.com/kindnod.js" data-owner="OWNER_EMAIL" data-via="claude-code" async></script>
React / Next.js:
npm install @kindnod/consent
import { KindnodConsent } from "@kindnod/consent/react";
// once, in the root layout or _app
<KindnodConsent owner="OWNER_EMAIL" via="claude-code" />
Replace OWNER_EMAIL with the site owner's email if you know it (they get a link to claim the dashboard). Otherwise drop the attribute.
Analytics and pixels must not run before consent. Either:
type="text/javascript" to type="text/plain" and add data-kindnod="statistics" (analytics) or data-kindnod="marketing" (ads, pixels). Kindnod releases them on consent.<Gated category="statistics">ā¦</Gated> from @kindnod/consent/react.Categories: preferences, statistics, marketing.
curl -X POST https://kindnod.com/api/sites/provision -H "content-type: application/json" \
-d '{"domain":"DOMAIN","owner":"OWNER_EMAIL","via":"claude-code"}'
Use the returned snippet and tell the user the claimUrl (private).
Remove the consent.cookiebot.com/uc.js tag. Keep everything else: data-cookieconsent attributes, CookiebotOnAccept listeners, and the CookieConsent cookie all keep working, and returning visitors are not re-asked. The dashboard imports the Cookiebot cookie declaration in one click.
