CookieYes alternative
CookieYes is, by a real margin, the best-executed SMB CMP we've audited: top-tier G2 and Trustpilot ratings, over a million WordPress installs, and the first CMP in this segment with a real MCP server in production — we say that openly, it's not a gap we're inventing. The difference isn't "who had MCP first," it's what sits behind it: a plugin with a volume surcharge versus an API with a cryptographically verifiable receipt.
| CookieYes | Tripticonsent | |
|---|---|---|
| Developer surface | WordPress plugin; no documented API/SDK of its own | REST API + SDKs (JS, iOS, Android, Flutter, WordPress, Shopify) |
| Proof of consent | A record in their platform | Append-only vault + Ed25519 signed receipt, offline-verifiable |
| AI-agent access | MCP server with OAuth 2.1 — manages banner configuration | MCP connector with OAuth 2.1 — scoped like a teammate, over the same data model as the public API |
| Volume surcharge | $0.30 / 1,000 pageviews | $0.25 / 1,000 consent events |
| Multi-domain | Per site | Quota pooled per organization, unlimited sites |
Pricing. CookieYes: Free · Basic $10/mo · Pro $25/mo · Ultimate $55/mo, + $0.30 per additional 1,000 pageviews. Tripticonsent: free up to 1,000 events/month, then $19/mo + $0.25 per additional 1,000 events — same kind of surcharge, lower rate. See full pricing.
What it does well
- A genuinely functional free tier (not just a trial), with over a million WordPress installs
- The first CMP in this segment with an MCP server in production, listed in the Claude connector directory
- Consistent support and ratings across every review platform
Real user complaints
- No developer-first API or SDK beyond the WordPress plugin
- A $0.30 surcharge per additional 1,000 pageviews
- Changing your billing currency requires deleting and recreating your account
“This is called EXTORTION and should be PUNISH by LAW!”
CookieYes was genuinely the first in this segment to ship an MCP server in production, and we say so without hedging. The difference is what that connector exposes: on Tripticonsent, every MCP action goes through the same append-only vault and the same signed receipt as the public API — it's not a separate surface just for the banner.
Yes — there is a WordPress plugin (tripticonsent-consent) that wraps the same SDK the public API uses, so the web integration and the API share exactly the same data model.
Migrate the consent layer, don't rewrite your banner.
The SDK speaks the same purpose/GRANTED-DENIED state model you already use. Integration is one API call.