Add a cookie consent banner to your Lovable website

Start with an approved 1Consent account, a configured app and a Lovable workspace that allows custom MCP servers. Each developer connects their own account.

1. 1

   Connect your selected app

   In Lovable, open Connectors → Add custom → MCP server. Use the endpoint supplied for your pilot, choose OAuth, then review the app and requested permissions in 1Consent.

2. 2

   Ask Lovable to check the real configuration

   With app-configuration read access, Lovable can retrieve the exact installation snippet, delivery mode, routing checks and deployed revision. Optional design-source access lets it inspect immutable released templates and the theme contract.

3. 3

   Review the change and test the CMP

   Ask Lovable to add the returned snippet in the correct document location. Review the diff and test consent on the actual website before publishing. Resolve any reported delivery or configuration blockers first.

After connecting with context and app-configuration reads, paste this into your Lovable project chat:

Use the 1Consent connector to inspect my selected app and retrieve its installation context. Report delivery readiness, blockers and the desired versus deployed revision. If it is ready, add the exact returned installation snippet once, in the documented location, and show me the diff. Do not invent an app ID, endpoint or configuration. Keep optional trackers gated until consent. Test opening preferences, rejecting optional services, reloading and changing the saved choice. Ask before any design write or publishing.

For source-based design work, enable design-source reads on a fresh connection and ask for the 1CL guidance, theme contract and immutable released template source. Theme changes still need a separately reviewed workflow.

The installation workflow needs context and app-configuration reads. Design-source reads are optional and initially off. The approval screen shows the selected app and lifetime; you can revoke the connection from Connected assistants in the 1Consent Dashboard.

The prompt above does not require analytics or design-write permissions. Aggregate consent reports need separate analytics access. Our MCP does not offer a production-publishing tool, and theme writes are not yet implemented.

The MCP connection belongs to the builder. It is not shipped to your visitors. The installed 1Consent script runs the CMP on your published website; never put OAuth credentials in browser code.

In a development acceptance test on 23 October 2026, Lovable read the selected app, returned its live installation instructions and matching desired/deployed revisions, and retrieved an immutable released GDPR template with source provenance. Revoking that temporary connection caused the next Lovable request to return HTTP 401.

A separate browser test loaded the real delivered script, opened preferences and preserved rejection after a reload. That fixture had no third-party trackers: each customer site still needs its own tracker-gating, consent-change and deployment checks. A banner installation alone does not establish legal compliance.

For the pilot, add 1Consent by its supplied URL. A registry can help your team discover servers after a workspace admin adds that registry. Neither an MCP registry entry nor this guide means 1Consent is featured in Lovable’s default connector catalog.

The same MCP is designed for other AI development tools with remote MCP and OAuth support. Local Git authoring is a separate workflow; use the integration guides to choose the right runtime installation.