# Use with Claude and other AI tools

Let your coding assistant do the install, check the result and read these docs.

These docs are written to be read by people and by the AI tools that help them. You can bring Flat Consent into an AI tool in five ways, listed below.

## 1. Paste a prompt

Copy one of these into Claude Code, Cursor, Codex or any agent that can read the web.

**Install on my site**

```
Install Flat Consent on this site. Read https://flatconsent.com/docs/install.md and https://flatconsent.com/docs/embeds-and-scripts.md first. Put the script tag before any other script in the head, add a "Cookie settings" link with data-cmp="settings" to the footer, convert YouTube and Maps iframes to data-cmp-src, and mark any custom tracking scripts with type="text/plain" data-cmp="analytics" or "marketing". My site id is: ____
```

**Check what my site does**

```
Use the Flat Consent MCP tool check_site on ____ and tell me, in plain words, whether I need a cookie banner in Europe, the UK and the US, and which trackers run before anyone agrees.
```

**Explain a setting**

```
Read https://flatconsent.com/docs/regions.md and explain what visitors from California see on my site.
```

## 2. Install the Claude Code plugin

These two commands give Claude Code the install skill and the MCP server together:

```
/plugin marketplace add mlingner/flatconsent-claude
/plugin install flatconsent@flatconsent
```

Then ask: "Use the flatconsent skill to add cookie consent to this site."

## 3. Connect the MCP server on its own

The server needs no login for checks, install steps and the docs.

Claude Code:

```
claude mcp add --transport http flatconsent https://mcp.flatconsent.com/mcp
```

Claude desktop and claude.ai: add a custom connector with the URL `https://mcp.flatconsent.com/mcp`.

Cursor, Windsurf and others: add an HTTP MCP server with that URL.

Tools that work without a key: `check_site`, `get_check`, `install_steps`, `search_docs` and `get_doc`.

## 4. Let Claude manage your sites

Create an API key in the dashboard under **API**, then connect with it:

```
claude mcp add --transport http flatconsent https://mcp.flatconsent.com/mcp --header "Authorization: Bearer fc_..."
```

With a key you can also use `list_sites`, `get_site`, `add_site`, `update_site`, `run_check`, `check_install`, `site_choices` and `match_brand`. These go through the same validation and plan limits as the dashboard, and brand colours are used exactly as given. A key can do anything you can do in the dashboard except create more keys, so keep it as safe as a password. If it leaks, revoke it on the API page.

Prompts that work well with a key:

```
Add example.com to Flat Consent, wait for the check, then show me the banner settings it chose.
```

```
On site ____, switch the wording to plain, ask first in California, and turn the floating settings button on.
```

```
Check whether Flat Consent is installed correctly on ____ and fix anything it reports in this repo.
```

## 5. Add only the skill

To add the skill without the plugin:

```
mkdir -p .claude/skills/flatconsent && curl -sL https://flatconsent.com/skill.md -o .claude/skills/flatconsent/SKILL.md
```

## Every page as Markdown

Add `.md` to any docs address to get the page as Markdown, for example `https://flatconsent.com/docs/install.md`. The index is at [`/llms.txt`](/llms.txt), and every page in one file is at [`/llms-full.txt`](/llms-full.txt). Each page also has a **Copy for LLM** button.