Skip to main content
Katla ships a remote MCP server, so you can manage your domains and ask questions about your cookies and consent records straight from an AI assistant - the same things you can do with the CLI, without the terminal. Ask “which marketing cookies is example.com setting?” or “what’s our consent acceptance rate this month?” and the assistant answers using your real Katla data.

​
Prerequisites

  • A Katla account at katla.app with at least one site
  • An AI assistant that supports remote MCP servers - Claude, ChatGPT, Claude Code, Cursor, or VS Code
There is nothing to install and no API key to create.

​
Step 1: Copy the server URL

​
Step 2: Add it to your assistant

  1. Open Settings → Connectors in Claude (web, desktop, or mobile).
  2. Click Add custom connector.
  3. Name it Katla and paste https://api.katla.app/mcp as the URL.
  4. Click Add.

​
Step 3: Sign in

Click Connect (in Claude Code, run /mcp and choose Authenticate). A browser window opens where you sign in with your normal Katla account, exactly as you would on the dashboard. That’s it - the Katla tools are now available in any new chat.
Everything the MCP server does runs as you. It can only reach the teams and sites you already have access to, and team roles, site permissions, and plan limits are enforced exactly as they are in the dashboard and CLI.

​
Step 4: Try it

Ask your assistant something it needs your Katla data to answer:
If it lists your domains, you’re connected.

​
What you can ask

Audit cookies

“What cookies does example.com set, and which are marketing?”

Check consent

“What’s the consent acceptance rate for example.com?”

Onboard a domain

“Add shop.example.com to Katla and scan it.”

Fix a classification

“Reclassify the _hjSession cookie on example.com as analytics.”

Write your own wording

“Describe _ga on example.com in German as ‘Unterscheidet Besucher’.”

Install the banner

“How do I install the Katla widget on example.com?”

​
Setting up a new domain, end to end

The steps below normally mean several separate visits to the dashboard. Ask for them together and the assistant walks the sequence itself:
  1. “Add shop.example.com to Katla.” The domain is usable immediately - there is no DNS record or meta tag to publish first.
  2. “Scan it.” Starts a cookie crawl. Scans count against your plan quota.
  3. “What did it find?” Lists the cookies and their categories.
  4. “How do I install the banner?” Returns your script tag.

​
Troubleshooting

Check that the URL is exactly https://api.katla.app/mcp, with no trailing slash. If you run your own Katla API, see self-hosting.
Your Katla session expired. Disconnect and reconnect the connector to sign in again.
The client requested only the katla:read scope. Reconnect and grant katla:write too.
You have used your plan’s monthly scan allowance. Ask the assistant to check your plan, or review it in the dashboard.
You belong to more than one team. Name the team in your request, or ask it to list your teams first.

​
Next steps

MCP reference

Every tool, the permission model, and self-hosting.

CLI

The same capabilities from your terminal.