Skip to content

ConsentAlly works with AI assistants. A merchant can have their assistant set up, sign in to or check their ConsentAlly account from the chat: the assistant needs only the merchant's email address, and the merchant approves it on one ConsentAlly page with a code. Nothing is created or connected before that approval. How it works: https://consentally.com/auth.md

Docs pages

ConsentAlly for AI agents

An AI assistant can set up and run a person's ConsentAlly cookie banner from the chat. It connects through an MCP connector or through auth.md, the person approves the connection on ConsentAlly's own page, and every change visitors would see asks the person first. These pages answer what an assistant needs to know before it starts, for the people who use one and for the models that read them.

The short answers

Can an assistant sign a person up? Yes. It registers with the person's email address, the person opens one ConsentAlly link, signs in or creates their account and types a 6-digit code the assistant gives them, and nothing is created or connected until they approve. See How an assistant signs a person up.

What can it do? Add websites, set the privacy rules from where the business sells, change and publish the banner, give the install tag, check the install, classify scripts, and read consent figures and records, each through a named tool that is the same at the MCP server and the HTTP API. See What an agent can and cannot do.

What happens before visitors see a change? The assistant gets a preview and a confirmation token instead of the change, shows the person the preview and confirms only after they say yes; the account owner then gets an email with a link that undoes the change. See Confirmation and undo.

Does it work on Shopify? Yes, and on any other website. A Shopify store installs the ConsentAlly app from the Shopify App Store and chooses its plan in Shopify's admin; any other website gets one script tag. See Shopify and other platforms.

What an assistant can never do

  • Approve its own connection. Only the person, signed in on ConsentAlly's page, approves it.
  • Delete or unpublish anything. No tool deletes a website, a banner version, a consent record or an account, and none takes a banner down.
  • Pay, choose a plan or accept terms. billing_link gives a link the person opens themselves.
  • See the person's password. They sign in on ConsentAlly's page, never in the chat.
  • Go beyond what the person granted. Read only, or read and change (an organisation admin only), on all of the organisation's websites or one.
  • Go beyond the plan. Every call is checked against the plan as the dashboard checks the same action.

The files assistants read

  • auth.md: how an assistant that is not an MCP client connects without any form.
  • The MCP server, https://app.consentally.com/api/mcp: what Claude, ChatGPT, Cursor or VS Code add as a connector. Setup for each app is in Connect an AI assistant.
  • llms.txt and the AI Catalog: the same entry points and every tool, and in llms.txt the plans too, generated from ConsentAlly's code. The AI Catalog and llms.txt are conventions still being drafted, not standards; the MCP server's own tool list is the source of truth.

What ConsentAlly itself does not do is on Limitations.