Add 1Consent with LovableCopy Anchor Link

Availability: the remote MCP is a development pilot verified with Lovable. A public production endpoint and a featured Lovable catalog listing have not launched. Request access to arrange a pilot. The team supplies the correct pilot endpoint; do not guess an endpoint or app ID.

Before connectingCopy Anchor Link

You need an approved 1Consent account, a configured app, and a Lovable workspace that allows custom MCP chat connectors. Each person connects their own account.

1. In Lovable, open Connectors → Add custom → MCP server.
2. Name the connector 1Consent, enter your supplied pilot endpoint, and choose OAuth.
3. Select the intended app in the 1Consent approval screen. For installation, grant context and app-configuration reads. Design-source reads are optional and initially off.
4. Review the permissions and lifetime, then approve the connection.

See Lovable's custom MCP instructions for current workspace controls. The connection is personal and belongs to the builder; it is not included in your published website.

Ask for installation contextCopy Anchor Link

Ask your assistant:

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.

The get_account_context tool identifies the authorized scope. get_installation_context returns the app-specific snippet, delivery mode, readiness blockers, routing validation and desired/deployed revisions. Resolve blockers before installing or publishing; a successful tool call does not establish that a customer website handles every tracker correctly.

Use the returned delivery instructions. See script installation and React integration for the runtime choices. The installed CMP script serves visitors independently of the AI connection. Never place MCP OAuth credentials in browser code.

Work with released designsCopy Anchor Link

For source-based design work, grant design-source reads on a new connection. Ask for 1CL guidance, the theme contract, and the released asset inventory. list_authoring_assets can restrict results to released designs; read_design can pin a published version and return immutable source provenance.

Reading source does not authorize changing it. Theme writes are not yet implemented. Design drafts, assignment, preview and publication are distinct operations. The MCP has no production-publishing tool. Review any design changes separately.

Reports and permissionsCopy Anchor Link

Aggregate consent reports require separate analytics permission. Installation does not require analytics or design-write access. This walkthrough uses an app-scoped connection, revocable from Connected assistants in the 1Consent Dashboard. Check the actual approval screen for its lifetime and access; do not infer permissions from this guide.

Verified behavior and remaining checksCopy Anchor Link

On 23 October 2026, a Lovable development acceptance test retrieved real installation context, matching desired/deployed revisions and an immutable released GDPR template. After the temporary grant was revoked, a subsequent Lovable request returned HTTP 401.

A separate browser fixture loaded the delivered CMP, opened preferences and retained rejection after reload. It contained no third-party trackers. On your own site, verify tracker gating before consent, consent changes, reload behavior and the published delivery revision. An installed banner alone does not establish legal compliance.

Discovery and other AI clientsCopy Anchor Link

For the pilot, add the supplied URL manually. A workspace owner or admin can add an MCP registry so members can browse its servers. Publishing registry metadata does not automatically place a server in Lovable's featured connector catalog.

Other remote MCP clients with OAuth support can use the same server model. Local Git authoring is a separate workflow. See the Lovable integration overview for the guided walkthrough.