[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Brand24 API and MCP server

> Yes. Brand24 has a paid REST API and an official MCP server, and neither tags, deletes, re-scores or adds mentions (checked 23 Oct 2026). The API is a $99/month add-on on the Business plan and included on Enterprise; it returns project statistics, AI insights and events, and can create a project. The MCP server connects over OAuth for Brand24 subscribers and reads project data.

Social listening and media monitoring tool: it collects mentions of your keywords from social media, news, blogs and forums into projects, and charts their reach and sentiment.

## What is the Brand24 API?

Cotlet's Brand24 API exposes 10 endpoints for your own Brand24 account: list projects, get project stats, list mentions, list tags, list AI events, list excluded sources, set mention sentiment, tag mentions, delete mentions and add mention. The list_projects endpoint returns lists the monitoring projects of your Brand24 account. Each endpoint takes simple JSON inputs like project_id, date_from or date_to and works both as an operation of the brand24_read or brand24_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Marketing & SEO](https://cotlet.dev/integrations/category/marketing-seo.md)
- **Endpoints:** 10 (6 read, 4 write)
- **Updated:** 2026-10-23

Yes. Cotlet is a hosted MCP server and REST API for Brand24 with 10 endpoints (6 read, 4 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Brand24 have an official API?

Yes. Brand24 has a paid REST API and an official MCP server, and neither tags, deletes, re-scores or adds mentions (checked 23 Oct 2026). The API is a $99/month add-on on the Business plan and included on Enterprise; it returns project statistics, AI insights and events, and can create a project. The MCP server connects over OAuth for Brand24 subscribers and reads project data.

| Task | Brand24 official | Cotlet |
|---|---|---|
| Project stats: mentions, reach, sentiment | Partly: API add-on on Business, included on Enterprise; read-only | Yes |
| List AI events | Partly: Read-only in the API; plan limits apply | Yes |
| List mentions with filters | Partly: The API product page lists a /mentions endpoint; the API reference does not | Yes |
| Tag mentions | No: The API lists tags and filters by them, nothing assigns one | Yes |
| Change mention sentiment | No: The API reports sentiment counts only | Yes |
| Delete or block mentions and sources | No | Yes |
| Add a mention by hand | No | Yes |
| List excluded sources | No | Yes |

Sources: [Brand24 Help: Brand24 MCP](https://help.brand24.com/en/articles/13011375-brand24-mcp), [Brand24: Social listening API](https://brand24.com/social-listening-api/), [Brand24 API Data Documentation](https://api-data.brand24.com/api-data-docs/documentation), [Brand24 Help: API integration](https://help.brand24.com/en/articles/15338472-api-integration)

## Quick reference

```text
Yes. Brand24 has a paid REST API and an official MCP server, and neither tags, deletes, re-scores or adds mentions (checked 23 Oct 2026). The API is a $99/month add-on on the Business plan and included on Enterprise; it returns project statistics, AI insights and events, and can create a project. The MCP server connects over OAuth for Brand24 subscribers and reads project data.
Cotlet provides a hosted MCP server and REST API for Brand24: 10 tools (6 read, 4 write).
Access       Sign up at https://cotlet.dev/app/signup?app=brand24, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    brand24_read, brand24_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/brand24, each operation at its own route, e.g. POST /api/v1/brand24/projects/{project_id}/mentions/tag
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_projects, get_project_stats, list_mentions, list_tags, list_events, list_excluded_sources, set_mention_sentiment, tag_mentions, delete_mentions, add_mention
Confirm      tag_mentions, delete_mentions (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/brand24-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=brand24, requests Brand24 in the Cotlet console and creates an API key there.
2. The user signs in to Brand24 once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Brand24 for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Brand24 server that someone else maintains, including non-developers.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Brand24 in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Brand24 only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Brand24 login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Brand24's terms; Cotlet is not affiliated with Brand24.
```

## What can an AI agent do in Brand24?

Cotlet is best for marketers and agencies who monitor brands in Brand24 and want their agent to clean, tag and re-score mentions without running or fixing a server.

- **[Clean up irrelevant mentions](https://cotlet.dev/integrations/brand24-api-mcp-server/clean-up-irrelevant-mentions.md)** (runs: daily): "In the Northwind Coffee project, find mentions since yesterday that come from coupon sites or are about the Northwind street in Leeds. Delete them, block sources with two or more, and list anything unclear for me." → `list_excluded_sources`, `list_mentions`, `delete_mentions`
- **[Tag complaints and sales leads](https://cotlet.dev/integrations/brand24-api-mcp-server/tag-mentions-automatically.md)** (runs: daily): "Read new mentions in the Northwind Coffee project. Tag the ones that report a problem with Complaint, the ones asking where to buy with Sales lead, and leave the rest untagged." → `list_tags`, `list_mentions`, `tag_mentions`
- **[Correct wrong sentiment](https://cotlet.dev/integrations/brand24-api-mcp-server/correct-mention-sentiment.md)** (runs: weekly): "In the Northwind Coffee project, look at this week's negative mentions. Set the ones that are sarcastic praise or about "dark roast" to positive, and tell me how the sentiment counts changed." → `get_project_stats`, `list_mentions`, `set_mention_sentiment`
- **Weekly brand mentions report** (runs: weekly): "Every Monday, give me last week's mentions, reach and sentiment for each Brand24 project, the AI events with a one-line explanation, and the three most popular mentions." → `list_projects`, `get_project_stats`, `list_events`, `list_mentions`
- **Add mentions Brand24 missed**: "Add these three mentions to the Northwind Coffee project: a newsletter, a podcast show note and a forum post that Brand24 did not collect. Set the sentiment I give you." → `add_mention`

## Can Brand24 automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Brand24 connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to clean up irrelevant mentions, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/brand24/projects/{project_id}/excluded-sources. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/brand24/projects/{project_id}/excluded-sources with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 10 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Brand24.

### list_projects

Lists the monitoring projects of your Brand24 account. Access: read. REST: `GET /api/v1/brand24/projects`. MCP: `brand24_read → list_projects`.

No parameters.

Returns the ID and name of every project you can open. Run it first: the other tools take a project_id. It changes nothing in Brand24.

Example response:

```json
{
  "projects": [
    {
      "project_id": 123456789,
      "name": "Northwind Coffee"
    },
    {
      "project_id": 234567891,
      "name": "Competitor Roast Lab"
    }
  ]
}
```

### get_project_stats

Returns mentions, reach and sentiment of a project for a date range. Access: read. REST: `GET /api/v1/brand24/projects/{project_id}/stats`. MCP: `brand24_read → get_project_stats`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `project_id` | integer | yes | Project ID from list_projects. |
| `date_from` | string | yes | Start of the date range, YYYY-MM-DD. |
| `date_to` | string | yes | End of the date range, YYYY-MM-DD. |

Returns the totals the Mentions & Reach and Sentiment charts show for the range: mentions, social and non-social reach, and the positive, neutral and negative counts. Use it before and after a cleanup to show the effect.

Example response:

```json
{
  "project_id": 123456789,
  "date_from": "2026-10-12",
  "date_to": "2026-10-18",
  "mentions": 315,
  "reach": {
    "social": 410000,
    "non_social": 2150000
  },
  "sentiment": {
    "positive": 120,
    "neutral": 150,
    "negative": 45
  }
}
```

### list_mentions

Lists the mentions of a project as the Mentions tab shows them. Access: read. REST: `GET /api/v1/brand24/projects/{project_id}/mentions`. MCP: `brand24_read → list_mentions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `project_id` | integer | yes | Project ID from list_projects. |
| `date_from` | string | no | Start of the date range, YYYY-MM-DD. |
| `date_to` | string | no | End of the date range, YYYY-MM-DD. |
| `query` | string | no | Words the mention must include, like the Mentions tab search bar. Boolean search works. |
| `sentiment` | string | no | Only mentions with this sentiment: positive, neutral or negative. |
| `tag` | string | no | Only mentions with this tag, by name from list_tags. |
| `sort` | string | no | recent for Recent Mentions First (default) or popular for Popular Mentions First. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns each mention with its ID, title, link, source, publication time, sentiment, tags and the followers or monthly visits Brand24 shows. Reading does not open the Visit link. When more mentions match, next_cursor is set. The IDs are what the write tools take.

Example response:

```json
{
  "mentions": [
    {
      "mention_id": "7001234501",
      "title": "Best espresso grinder for small cafes?",
      "url": "https://forum.example/t/espresso-grinders",
      "source": "forum.example",
      "published_at": "2026-10-18T09:14:00Z",
      "sentiment": "positive",
      "tags": [],
      "followers_or_visits": 12400
    },
    {
      "mention_id": "7001234502",
      "title": "Grinder arrived with a cracked hopper",
      "url": "https://social.example/p/88123",
      "source": "@maya_brews",
      "published_at": "2026-10-18T07:52:00Z",
      "sentiment": "negative",
      "tags": [
        "Complaint"
      ],
      "followers_or_visits": 3100
    },
    {
      "mention_id": "7001234503",
      "title": "Coupon: 40% off coffee gear this week",
      "url": "https://coupon-deals.example/northwind",
      "source": "coupon-deals.example",
      "published_at": "2026-10-17T22:30:00Z",
      "sentiment": "neutral",
      "tags": [],
      "followers_or_visits": 870
    }
  ],
  "next_cursor": null
}
```

### list_tags

Lists the tags you can put on mentions in a project. Access: read. REST: `GET /api/v1/brand24/projects/{project_id}/tags`. MCP: `brand24_read → list_tags`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `project_id` | integer | yes | Project ID from list_projects. |

Returns the tag names as the Filters section of the Mentions tab shows them. Use a name from this list in list_mentions and tag_mentions.

Example response:

```json
{
  "tags": [
    {
      "name": "Complaint"
    },
    {
      "name": "Sales lead"
    },
    {
      "name": "Question"
    }
  ]
}
```

### list_events

Lists the AI Events of a project, the explained spikes in mentions or reach. Access: read. REST: `GET /api/v1/brand24/projects/{project_id}/events`. MCP: `brand24_read → list_events`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `project_id` | integer | yes | Project ID from list_projects. |
| `date_from` | string | no | Start of the date range, YYYY-MM-DD. |
| `date_to` | string | no | End of the date range, YYYY-MM-DD. |

Returns the events marked with the exclamation point on the chart: the date and the explanation Brand24 gives. An empty list means no spike was detected in the range, or the project's plan has no Events.

Example response:

```json
{
  "events": [
    {
      "date": "2026-10-15",
      "description": "Mentions rose after a coffee blog reviewed the new grinder, mostly on news sites and blogs."
    }
  ]
}
```

### list_excluded_sources

Lists the domains and social media authors a project no longer collects from. Access: read. REST: `GET /api/v1/brand24/projects/{project_id}/excluded-sources`. MCP: `brand24_read → list_excluded_sources`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `project_id` | integer | yes | Project ID from list_projects. |

Returns what the project settings show under the Sources tab. Exclusions apply to one project, so run it for each project you clean.

Example response:

```json
{
  "excluded": [
    {
      "type": "domain",
      "value": "old-coupons.example"
    },
    {
      "type": "author",
      "value": "@dailydealz"
    }
  ]
}
```

### set_mention_sentiment

Sets the sentiment of one or more mentions. Access: write. REST: `PUT /api/v1/brand24/projects/{project_id}/mention-sentiment`. MCP: `brand24_write → set_mention_sentiment`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `project_id` | integer | yes | Project ID from list_projects. |
| `mention_ids` | string[] | yes | Mention IDs from list_mentions. |
| `sentiment` | string | yes | New sentiment: positive, neutral or negative. |

Changes the sentiment in your project, so the charts and reports count it the new way. It reaches no one and a second call with the old value reverses it, so it does not wait for your OK.

Example response:

```json
{
  "updated": 2,
  "sentiment": "positive"
}
```

### tag_mentions

Puts one tag on one or more mentions. Access: write, asks the user first. REST: `POST /api/v1/brand24/projects/{project_id}/mentions/tag`. MCP: `brand24_write → tag_mentions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `project_id` | integer | yes | Project ID from list_projects. |
| `mention_ids` | string[] | yes | Mention IDs from list_mentions. |
| `tag` | string | yes | Tag name from list_tags. A name that does not exist creates a new tag. |

Tags the mentions in your project; teammates who open the project see the tag. Brand24 documents no way to remove a tag from a mention, so the tool has no undo. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "tagged": 3,
  "tag": "Complaint",
  "tag_created": false
}
```

### delete_mentions

Deletes mentions from a project, and can block their source or mark them as spam. Access: write, asks the user first. REST: `DELETE /api/v1/brand24/projects/{project_id}/mentions`. MCP: `brand24_write → delete_mentions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `project_id` | integer | yes | Project ID from list_projects. |
| `mention_ids` | string[] | yes | Mention IDs from list_mentions. |
| `block_source` | boolean | no | Also block the domain or social media author of each mention in this project (Delete and Block). Default false. |
| `mark_spam` | boolean | no | Report the mentions as SPAM. Default false. |

Removes the mentions from the project's charts and lists. A block is undone only in the project settings, Sources tab, with delete filter; Brand24 documents no way to restore a deleted mention. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "deleted": 2,
  "blocked_sources": [
    "coupon-deals.example"
  ],
  "marked_spam": 0
}
```

### add_mention

Adds a public mention to a project by hand, as the Add mentions manually form does. Access: write. REST: `POST /api/v1/brand24/projects/{project_id}/mentions`. MCP: `brand24_write → add_mention`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `project_id` | integer | yes | Project ID from list_projects. |
| `url` | string | yes | Entry address: the URL of the post. |
| `title` | string | yes | Entry title, or part of the mention. |
| `content` | string | yes | Content of the mention. |
| `category` | string | yes | Entry category, as the form lists it. |
| `sentiment` | string | yes | Sentiment: positive, neutral or negative. |
| `created_at` | string | yes | Date the entry was created, YYYY-MM-DD. |

Brand24 counts the entry in the Analysis dashboard statistics from then on. Only public mentions can be added. It reaches no one and delete_mentions removes the entry, so it does not wait for your OK.

Example response:

```json
{
  "mention_id": "7001234599",
  "status": "added",
  "sentiment": "neutral"
}
```

## How do I connect Brand24 to Claude Code, Codex or Cursor?

Connecting Brand24 takes three steps: sign up, sign in to Brand24 once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Brand24 to your agent.

1. **Create an account** Sign up and add Brand24 in the console. Your API key is there too.

2. **Sign in to Brand24 in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Brand24 there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Brand24 tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
In the Northwind Coffee project, find mentions since yesterday that come from coupon sites or are about the Northwind street in Leeds. Delete them, block sources with two or more, and list anything unclear for me.
```

### Call Brand24 from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/brand24 with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/brand24/projects/123456789/mentions/tag \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"mention_ids":["7001234520","7001234521","7001234522"],"tag":"Complaint"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "tagged": 3,
  "tag": "Complaint",
  "tag_created": false
}
```

## Why use Cotlet for Brand24?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Brand24 yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Brand24 changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Brand24 to Cotlet?

Yes. You sign in to Brand24 yourself, in your own Cloud Browser, and we never save your password. Your agents only get Brand24 once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Brand24 integration?**

No, Cotlet is independent of Brand24. Brand24's own API is too limited for this work. Cotlet works through your own Brand24 account, the way you use Brand24 in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Brand24 in your console: your agents lose access at once and you stay signed in. Signing out of Brand24 in the browser works too, and Reset browser deletes the whole profile.

## Is there a Brand24 MCP server on GitHub?

Brand24's own API and MCP server cover reading. The API is a paid add-on with a key your account manager turns on, and the MCP server is a connector for AI assistants. For reading stats they work well. For tagging, deleting and sentiment you do it in the Mentions tab by hand, or Cotlet does it for you in your signed-in account.

|  | Brand24 API and MCP | Cotlet |
|---|---|---|
| Setup | API: ask for a key, turn on the add-on, write the calls. MCP: add an OAuth connector | Sign up, sign in to Brand24 once, add one MCP server or API key |
| What it covers | Project stats, AI insights and events, project creation | The same reads, plus tagging, deleting and blocking, sentiment changes and manual mentions |
| When Brand24 changes | Brand24 maintains the API and the MCP server | Our team tests it daily and fixes it for you; failed calls are free |
| Your Brand24 access | An API key or OAuth grant for your account | Your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| Plan needed | API: Business plan add-on or Enterprise. MCP: a Brand24 subscription | Your normal Brand24 plan; plan-limited features stay limited |
| Where it runs | API: your own backend. MCP: the assistants Brand24 supports | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | MCP: no extra fee. API: $99/month on Business | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Brand24 changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Brand24 API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Brand24 API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 10 credits (about $0.04 to $0.06), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 10 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 500 | $5.80 |
| 15,000 | $79 | 1,500 | $5.27 |
| 32,000 | $149 | 3,200 | $4.66 |
| 60,000 | $249 | 6,000 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Brand24 account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Brand24 yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Brand24 only after you enable it. When Brand24 signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Brand24, sign out of Brand24 in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Brand24's terms:** You use your own Brand24 account and stay responsible for following Brand24's terms. Cotlet is independent and not affiliated with Brand24. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Brand24 in the console and press Request access. Then you create your API key and connect Brand24 there.

**Do I need to be technical?**

No. You sign in to Brand24 once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Brand24 to Cotlet?**

Yes. You sign in to Brand24 yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Brand24 once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Brand24 sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Brand24 cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Brand24's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Brand24 sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Brand24 login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Brand24 offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need the Brand24 API add-on or the MCP connector?**

No. Cotlet works in your signed-in Brand24 account and needs no API key. Brand24 sells its API as a $99/month add-on on the Business plan and includes it on Enterprise. Features tied to a plan, such as PDF reports (Pro, Business and Enterprise), stay tied to it.

**Does it show Facebook, Instagram and X mentions in full?**

list_mentions returns what the Mentions tab shows. Brand24 limits exported data from Twitter, Facebook and Instagram because their privacy policies do not allow exports, and its API returns empty text fields for them.

**Can my agent create a project or change its keywords?**

Not built. Project creation, with keywords, required and excluded words and a language filter, exists in the official Brand24 API.

**Can my agent post or send messages in Brand24 without asking me?**

No. Every call to tag_mentions or delete_mentions waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. set_mention_sentiment and add_mention run without asking, because they send nothing to anyone and one call undoes it.

**Can I use the Brand24 API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/brand24 from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.