iubenda automates website privacy compliance by creating and managing privacy policies, cookie policies, terms and conditions, consent banners, and third-party service disclosures. Scan websites for trackers and update legal documents to support GDPR, ePrivacy, and US privacy law compliance.
Visual Studio Code runs MCP servers for Copilot Chat in agent mode, so the model can use external tools while it works on your code.
This guide connects Iubenda MCP to VS Code through MewCP, so VS Code can use Iubenda MCP's 28 tools, like get_user, list_sites and get_site, without your Iubenda MCP credentials ever reaching the app.
Iubenda MCP signs in through managed OAuth. MewCP stores the token encrypted, refreshes it before it expires and injects it only at call time. Your agent never holds it, so it can never leak it.
More apps
Clerk enables AI agents to manage application authentication, user accounts, organizations, sessions, and access permissions, including inspecting user profiles and configuring authentication workflows.
OnChainDiligence helps AI agents evaluate autonomous payment proposals against caller-defined policies, retrieve signed payment receipts, and independently verify receipt integrity and authenticity. Provides evidence for auditing agent payment decisions without holding funds, signing transactions, or executing payments.
ConsentStack automates website cookie consent management by creating and publishing consent banners, configuring privacy settings, detecting and categorizing tracking scripts, running compliance scans, and reviewing consent analytics and logs for GDPR and other privacy regulations.
CourtListener provides searchable access to U.S. case law, court opinions, dockets, judicial decisions, and legal filings. Find cases by citation, keyword, court, or judge; retrieve opinion texts and docket records; and research legal precedents using data from federal and state courts.
Other clients
Iubenda MCP works the same way in every client below. Pick yours for its own guide.
Free to start.
Scope access to the exact Iubenda MCP tools and accounts you allow, work and personal side by side. Anything outside that scope is refused at call time, even when the model asks for it.
Each call is logged: what ran, on which account, and whether it worked. Failures come back structured, so the agent knows whether to retry instead of guessing.
Every app sits behind one secure MCP URL, and there is no server for you to deploy or keep running. Add an integration in the dashboard and it is live on the next call, with no config to change and no new credentials to wire up. Tools load only when a task needs them, so your agent stays fast and focused however many apps you connect.
A browser window opens the first time the client connects. Sign in and approve access. No API key needed.
Start a new chat and ask: "List the tools you can use from MewCP." You should see your connected apps.
Retrieve the authenticated user's account details. The `updated_at` field reflects internal account record changes and does not indicate user-initiated activity.
List all iubenda sites. Sites represent websites or apps that need privacy and consent tooling.
Retrieve a single iubenda site by ID.
Create a new iubenda site. Legislation flags (gdpr, fadp, ccpa_only_california, gdpr_only_eu, lgpd_only_brazil) are enabled by default. No Privacy Policy, Cookie Solution, or Terms & Conditions is active until explicitly created. The response includes a dashboard_url field linking to the new site on iubenda.com. If the response includes a `business_details_warning` field, surface it to the user.
Update an existing iubenda site.
Delete an iubenda site by ID.
Get the Privacy & Cookie Policy document for a site.
Create a Privacy & Cookie Policy document for a site. Only one per site; the site must exist first. The document is created as a draft (shown as "resume generation" in the dashboard) until owner info is set via `update_site`. Optionally use `create_site_pcp_service` to add services.
Update the Privacy & Cookie Policy document for a site.
Delete the Privacy & Cookie Policy document for a site.
Get the Terms & Conditions document for a site.
Create a Terms & Conditions document for a site. Only one per site; the site must exist first. The document is created as a draft (shown as "resume generation" in the dashboard) until owner info is set via `update_site`.
Update the Terms & Conditions document for a site.
Delete the Terms & Conditions document for a site.
Get the Cookie Solution for a site.
Create a Cookie Solution for a site. Only one per site; the site must exist first.
Update the Cookie Solution for a site.
Delete the Cookie Solution for a site.
Browse the catalog of available Privacy Controls and Cookie Policy (PCP) services. Use to discover services available to add to a site. Pass `query` to filter services by a keyword in the service name (e.g. "google").
Get a PCP catalog service by ID, including available personal data types and processing places.
List PCP services added to a site. Requires an active Privacy & Cookie Policy on the site.
Get a PCP service added to a site by its catalog service_id. Use list_site_pcp_services to find the primary key for update/delete operations.
Add a PCP catalog service to a site. Use list_pcp_services to find available service IDs. Requires an active Privacy & Cookie Policy on the site.
Update a PCP service added to a site. Use the primary key returned by list_site_pcp_services or create_site_pcp_service.
Remove a PCP service from a site. Use the primary key returned by list_site_pcp_services or create_site_pcp_service.
Get the current pricing package for a site.
Schedule a Radar compliance scan for an iubenda site. Returns immediately with an empty envelope; the scan runs asynchronously and typically takes 1–2 minutes. iubenda emails the site owner when the scan finishes. Ask the user whether they prefer to wait for that email or to check back in the chat in a couple of minutes; when ready, use get_scan(site_id) to retrieve the results.
Retrieve the current Radar compliance scan for an iubenda site. Poll this after start_scan until `status` is `completed` — `status` is the authoritative signal. Also returns `ready` (boolean alias for `status == "completed"`), detected services (perfect_matches, other_matches), trackers, document detection (detected_pp/cp/tc/impressum), and installation state (pp_installed, cp_installed, tc_installed).
