The first CMP with a built-in MCP server
Connect AI agents to consent management via a standardized protocol. Same operations as the B2B zone, same permissions, full traceability.
MCP Server — architecture
What is MCP
MCP (Model Context Protocol) is an open standard for communication between applications and tools. Waulter is the first CMP on the market to offer a built-in MCP server:
- Standardized protocol — AI agents and external tools communicate with Waulter via a unified, documented interface.
- No custom integration needed — you do not need to write your own API connector. MCP is a ready-made standard.
- Open ecosystem — MCP is supported by tools like Claude, Cursor, and others. Waulter brings consent management into this ecosystem.
What it means in practice
The MCP server allows AI agents to perform operations you would otherwise do manually in the B2B zone:
- Management automation — an agent can check configurations, run a website analysis, or update cookie banner settings.
- Monitoring and reports — an agent pulls daily consent statistics, session overviews, or implementation details on its own.
- Cookie and document management — adding, editing, and categorizing cookies. Creating new versions of legal documents.
- Access control — sharing configurations between users, managing whitelisted domains.
Why it matters
A CMP manages consents — but until now, there was no standard way to expose that data and those operations to other tools. MCP changes that:
- AI agents understand context — an agent knows what configurations you have, what the consent statistics look like, and what needs adjusting.
- Workflow automation — connect consent management to other tools in your tech stack.
- Scale without manual effort — operations that would take hours manually, an agent handles in seconds.
Available operations via MCP
All operations require authorization and respect the same permissions as the B2B zone.
| Category | Operations | Description | Access |
|---|---|---|---|
| Configuration management | List, detail, update, copy, analyze, stats | Full cookie banner management | Read / Read+Write |
| Cookie management | List, detail, add, update, delete | Cookie database management | Read / Read+Write |
| Legal documents | List, detail, save | Versioned legal documents | Read / Read+Write |
| Scenarios & rules | List, detail, create, update | Conditional banner display | Read / Read+Write |
| Domains | List, add, remove | Whitelist management | Read / Read+Write |
| Access sharing | Share, revoke, global sharing, user lookup | Access delegation | Read+Write |
| Reports | Daily consents, sessions, companies | Analytics and overviews | Read |
Security model
- Same permissions, different interface — the MCP server respects exactly the same permissions as the B2B zone.
- Read-only by default — write operations require explicit authorization.
- No admin operations — the MCP server does not expose administrative operations.
- Authorization via Bearer token — every request requires a valid authorization token.
- Audit trail — all operations performed via MCP are logged in the same audit log as B2B zone operations.
Want to activate MCP for your account?
The MCP server is available for enterprise clients. Contact us and we will activate MCP access for your account.