Claude iubenda connectorWhat Claude can do in your iubenda account.
The Claude iubenda connector exposes 28 tools. 12 of them read your sites and documents, 16 change them, and 0 are left undocumented. Below: what Claude can set up for you, the steps that cannot be undone, and the 5 tools where iubenda says Claude confirms first.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can work in iubenda
Website compliance usually means forms, catalogs and a lot of clicking. With this connector, you tell Claude what your site does and which services it uses, and it works in your iubenda account itself: registering the site, scanning it for trackers, generating the privacy and cookie policy, setting up the cookie banner and declaring each third-party service, all from one conversation.
Set up a new site end to end. A founder launching a shop asks Claude to handle compliance: it registers the site with create_site, reads the account owner details with get_user, then produces the policy with create_privacy_cookie_policy and the banner with create_cookie_solution.
Scan first, then declare what is really running. start_scan checks the live site in the background and get_scan reports the trackers and third-party services found; Claude then adds each one from the catalog with create_site_pcp_service.
Keep the policy in step with the site. When you drop a tool, delete_site_pcp_service takes it off your policy; when you add one, the catalog lookup finds it first.
What to know before you ask: saving the owner details finalizes any draft policy, and that cannot be undone. Deleting a site takes its documents with it. Some actions depend on your iubenda plan. And nothing fires by itself when your site changes: re-running a scan on a schedule is an automation tool's job, a different trade covered by the Integrations hub.
Five words before you connect
The vocabulary Claude uses around this connector, quickly.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in that account while it answers.
- Tool
- One named action a connector lets Claude take. Claude chooses the tools it needs by itself, and the directory lists each one by name.
- Authorization
- The login screen of the service itself, where you give Claude the access it will use. Granted once per person, and revocable.
- Approval
- The confirmation Claude waits for before doing something that changes your account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on, which is what lets an assistant such as Claude talk to an outside service like iubenda.
Connect iubenda to Claude in three steps
- 01
Find iubenda in Claude
Open Claude's settings, go to Customize and then Connectors, and look for iubenda in the list. On a Team or Enterprise workspace, an Owner or Primary Owner switches the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in with your existing iubenda account in the window iubenda opens. If the sign-in does not stick, use Disconnect and add it again.
- 03
Review the authorization screen
Read the authorization screen before you accept. It belongs to iubenda, not to Claude, and it sets what the access covers. iubenda suggests a first test afterwards: ask Claude to list your iubenda sites.
The 28 tools, split by what they do
iubenda gives Claude 28 tools: 12 that read your account, 16 that change something in it.
Two groups: what Claude reads in iubenda and what it changes there. Tool names stay exactly as Claude displays them.
- 12 read
- 16 write
What Claude reads (12)
12 toolsTwelve tools that look at sites, scans, documents and the service catalog, and leave them untouched.
get_cookie_solution
Shows how the cookie banner of a site is currently configured: its position, colours and consent behaviour as iubenda stores them.
get_pcp_service
Opens one service from iubenda's catalog and explains the personal data it handles and where that data is processed.
get_pricing_package
Checks which iubenda plan and limits apply to a given site, so Claude can tell you why a feature is not there.
get_privacy_cookie_policy
Reads the privacy and cookie policy of a site along with its display settings, the combined document iubenda keeps, one per site, which covers both the privacy notice and the cookie disclosure.
get_scan
Retrieves the outcome of a scan: trackers, third-party services, and which iubenda documents were detected and installed on the live site.
get_site
Displays the details and current setup of one site registered in your account, as iubenda holds it.
get_site_pcp_service
Looks at one service as it is declared on your site, with the data types and processing places currently attached to it in the policy.
get_terms_conditions
Reads the terms and conditions of a site and their display settings, so Claude can answer questions about them without you opening the iubenda dashboard yourself.
get_user
Looks up your account name and email, which iubenda uses to fill in the owner details on your documents.
list_pcp_services
Searches iubenda's catalog of services by name, from analytics to payments and chat, so Claude can find the exact entry for a tool you use.
list_site_pcp_services
Lists the services currently declared on a site's policy, which gives Claude the baseline to compare against a fresh scan of the live site.
list_sites
Returns every site or app registered in your iubenda account. iubenda suggests it as the first check after connecting.
What Claude changes (16)
16 toolsSixteen tools that alter your iubenda account. For five of them, iubenda says Claude confirms first; the others follow the general rule below.
create_cookie_solution
Approval: see the ruleSets up the cookie banner for a site, the piece that collects consent on your visitors' pages.
create_privacy_cookie_policy
Approval: see the ruleGenerates the combined privacy and cookie policy of a site, one per site. It stays a draft until the owner details are confirmed.
create_site
Approval: see the ruleRegisters a new website or app with its business type, country and where its users are. It is registration only: no document goes live at this stage.
create_site_pcp_service
Approval: see the ruleAdds a service from the catalog to a site's policy, so the tool is declared with the data it collects and where it processes it.
create_terms_conditions
Approval: see the ruleProduces terms and conditions for a site. Like the policy, they remain a draft until you confirm the owner details.
delete_cookie_solution
Asks you firstRemoves the cookie banner of a site, which stops consent collection there. iubenda marks it as destructive.
delete_privacy_cookie_policy
Asks you firstDeletes the privacy and cookie policy of a site. iubenda flags it as destructive and notes that updating is usually the better choice.
delete_site
Asks you firstDeletes a site from your account and removes its documents along with it. iubenda classes it as destructive.
delete_site_pcp_service
Approval: see the ruleTakes a service off a site's policy once you no longer use it, so the policy stops declaring it.
delete_terms_conditions
Asks you firstDeletes the terms and conditions of a site, a step iubenda labels as destructive.
start_scan
Approval: see the ruleLaunches a scan of your live site in the background. It usually takes a minute or two, and iubenda also emails you when it is done.
update_cookie_solution
Approval: see the ruleConfigures the cookie banner: position, colours and consent behaviour, following iubenda's configuration options.
update_privacy_cookie_policy
Approval: see the ruleChanges display settings of the privacy policy, such as the badge style. It does not rewrite the legal text, which comes from your site setup and declared services.
update_site
Asks you firstEdits a site's details. Saving the owner information finalizes any draft policy on that site, and that cannot be undone.
update_site_pcp_service
Approval: see the ruleUpdates the data types and processing places declared for one service on your site, when a provider starts collecting more or moves its hosting.
update_terms_conditions
Approval: see the ruleModifies how the terms and conditions display, for instance the badge style, without touching their substance.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account on someone's behalf. iubenda adds its own promise for permanent steps.
iubenda states that its assistant always confirms before anything is finalized or deleted, and marks four deletion tools as destructive. On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked every time, and they can restrict what a connector does for the whole organization, for example keeping reading and closing writing. Claude also acts with the rights of the person who signed in. Removing the connector from Claude's settings stops all access at once.
Which plans include it
None of the 819 sheets in the official directory shows plan availability, so the answer for iubenda is published nowhere.
Anthropic publishes the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector before members connect one by one. For the live state of iubenda on your account, open its sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so no scan reruns and no policy refreshes on its own when your site changes.
This connector is documented by its publisher only: no page of Claude's help center covers it. The tool list is an observed floor, not a promise, since an administrator can open actions that no public sheet shows. The partner badge is not a security audit, and Anthropic says on every sheet that it does not choose the tools a publisher exposes nor guarantee how they behave. The Claude bamboohr connector page reads another account through the same grid.
Need help connecting iubenda to Claude?
A person reads every message.
