Connect an AI assistant
ConsentAlly's MCP server lets an AI assistant set up and check your ConsentAlly account from the chat. You add one address to your assistant, approve it on ConsentAlly's own page, and anything visitors would see asks you first.
The address every app takes:
https://app.consentally.com/api/mcpClaude
- In Claude, open Customize, then Connectors.
- Click + Add, then Add custom connector.
- Name it ConsentAlly, paste the address above and click Continue, then Add.
- Sign in to ConsentAlly when Claude asks, and approve it there.
- In a chat, click + in the lower left, choose Connectors and switch ConsentAlly on.
Custom connectors work on every Claude plan, in Claude on the web and in Claude Desktop; Free allows one. On Team and Enterprise an Owner adds it first, under Organization settings, Connectors: Add, then Custom, then Web. Members then find it under Customize, Connectors and click Connect.
ChatGPT
Custom MCP servers are for ChatGPT Business, Enterprise and Edu, on the web. On Business, only admins and owners can add one; on Enterprise and Edu, admins can let other members do it too.
- Open chatgpt.com/plugins.
- Click +, then Add custom MCP server.
- Name it ConsentAlly and paste the address above under Connection.
- Choose OAuth for authentication, tick I understand and want to continue and click Create as a plugin.
- Install the plugin, start a new chat, type @ and pick ConsentAlly.
Claude Code
Run this in your terminal:
claude mcp add --transport http consentally https://app.consentally.com/api/mcpThen run /mcp in Claude Code and follow the sign-in in your browser. The command adds ConsentAlly to the current project; add --scope user to have it in every project.
Cursor
Add ConsentAlly to Cursor opens Cursor with the server filled in. Or add it to ~/.cursor/mcp.json yourself:
{ "mcpServers": { "consentally": { "url": "https://app.consentally.com/api/mcp" } }}Cursor asks you to sign in to ConsentAlly the first time you use it.
VS Code
Install ConsentAlly in VS Code opens VS Code with the server filled in. Or run:
code --add-mcp '{"name":"consentally","type":"http","url":"https://app.consentally.com/api/mcp"}'It uses VS Code's AI features in agent mode; sign in to ConsentAlly when VS Code asks.
Approve it on ConsentAlly
ConsentAlly's page asks three things before the assistant gets anything:
- Organisation: which of your organisations it works in.
- What it may do: Read and change sets up the banner and scripts for you, and publishing always asks you first; Read only checks your setup and consent figures and cannot change anything. Only an organisation admin can let an assistant change things.
- Websites: all of the organisation's websites, or one.
Cancel: do not connect it turns the request down and connects nothing.
What each tool does
The assistant calls these tools by name. The ones marked asks first show you a preview and wait for your yes in the chat. Any other category for a script, stricter or one that still waits for consent, applies at once, from the next delivery; nothing else changes what visitors see. An organisation admin can turn on Require approval on ConsentAlly under Connected assistants: each of these changes then waits until an admin approves it on ConsentAlly, from a link the assistant gives, and a yes in the chat is not enough. Turning it on, and each approval, needs two-step verification, such as an authenticator app, on the admin's ConsentAlly account; a password alone never approves.
next_steps: where each website's setup stands and the one thing to do now.add_store: adds a website to your account.set_jurisdictions: sets the privacy rules from where you sell, as the dashboard's Where you sell step does. Draft only.get_config: reads the banner's draft settings and which version visitors see now.update_banner: changes the draft's layout, colours, text, links, languages or categories. Draft only.publish: publishes the draft. Asks first.rollback: makes an earlier published version live again. Asks first.install_snippet: gives the install tag, or the Shopify install link, with where it goes.install_status: says whether the tag is installed on your website.list_scripts: lists the third-party scripts found on your website and when each may run.classify_script: sets what a script is for. Asks first when that lets it run before visitors choose.consent_stats: your consent figures for a date range.lookup_consent: one visitor's consent record, by the consent ID from the banner's preferences.plan_options: the plans, their prices and what each includes.billing_link: the link where you change your plan yourself.
None of them deletes, unpublishes or charges, and every call is checked against your plan as the dashboard checks it. Each confirmed change is emailed to the account owner, with a link that undoes it for 7 days unless it was the first publish.
What ConsentAlly itself does not do is on Limitations. For the assistant's side of it, how it signs a person up, every tool and how confirmation and undo work, see ConsentAlly for AI agents.
Assistants without connectors
An assistant that cannot add an MCP connector can read app.consentally.com/auth.md: it explains how to connect to your account without any form. You still approve it on a ConsentAlly page, with a code the assistant gives you.
Disconnect an assistant
An organisation admin opens Connected assistants in the dashboard and disconnects it; its access ends at once.
Troubleshooting
- Connect does nothing. Your app opens ConsentAlly's sign-in in your browser. Allow pop-ups for the app and try again. In ChatGPT Business, only admins and owners can add a custom MCP server.
- It works in the wrong organisation. Disconnect it under Connected assistants, then connect again and pick the right organisation on ConsentAlly's page.
- It says a plan limit was reached. The assistant names the plan that allows more, and
billing_linkgives the link where you change your plan yourself. It never pays for you. - It says it is signed out. Connect it again: in Claude or ChatGPT with the connector's Connect button, in Claude Code with
/mcp.
Last updated