[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)

# BrightLocal API and MCP server

> BrightLocal has a full REST API, the Management APIs and Data APIs, and an official MCP server, BrightLocal Anywhere, that only reads (checked 23 Oct 2026). The MCP server needs an active Grow plan and Labs access, and BrightLocal says it cannot change anything in your account. The REST API needs an API key from BrightLocal support and a developer.

Local SEO platform for agencies and multi-location brands: Local Rank Tracker, Local Search Grid, Reputation Manager, Citation Tracker and Citation Builder for every business location.

## What is the BrightLocal API?

Cotlet's BrightLocal API exposes 11 endpoints for your own BrightLocal account: list locations, list rank tracker reports, get a rank tracker report, get a Local Search Grid report, list reviews, get a Citation Tracker report, list Active Sync alerts, update rank tracker keywords, re-run a report, respond to a review and set a review status. The list_locations endpoint returns list the locations in the account, as on All Locations. Each endpoint takes simple JSON inputs like report_id, cursor or status and works both as an operation of the brightlocal_read or brightlocal_write MCP tool for agents and as a REST call for scripts.

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

BrightLocal has a full REST API, the Management APIs and Data APIs, and an official MCP server, BrightLocal Anywhere, that only reads (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for BrightLocal with 11 endpoints (7 read, 4 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does BrightLocal have an official API?

BrightLocal has a full REST API, the Management APIs and Data APIs, and an official MCP server, BrightLocal Anywhere, that only reads (checked 23 Oct 2026). The MCP server needs an active Grow plan and Labs access, and BrightLocal says it cannot change anything in your account. The REST API needs an API key from BrightLocal support and a developer.

| Task | BrightLocal official | Cotlet |
|---|---|---|
| List locations and their reports | Yes: Management APIs; the MCP server reads locations too | Yes |
| Read Local Rank Tracker results | Yes: Management APIs and the read-only MCP server | Yes |
| Read Local Search Grid results | Yes: Management APIs and the read-only MCP server | Yes |
| Read reviews from Reputation Manager | Yes: Management APIs and the read-only MCP server | Yes |
| Read a Citation Tracker report | Yes: Citation data in the APIs; the MCP server answers questions about it | Yes |
| Change the keywords of a rank tracker report | Partly: The REST API can update reports; the MCP server is read-only | Yes |
| Re-run a report | Partly: The Rank Tracking API schedules reports; the MCP server is read-only | Yes |
| Reply to a Google or Facebook review | Partly: The MCP server is read-only; replies go out from the Respond button in the app | Yes |
| Set a review status such as Do Not Respond | No | Yes |
| Read Active Sync alerts | No: Alerts sit in the Alert Inbox of the app; no API or MCP tool found on the pages checked | Yes |

Sources: [BrightLocal Help: Is BrightLocal Anywhere secure?](https://help.brightlocal.com/hc/en-us/articles/31736399464466-Is-BrightLocal-Anywhere-secure), [BrightLocal Help: How do I get started with BrightLocal Anywhere?](https://help.brightlocal.com/hc/en-us/articles/31736403362962-How-do-I-get-started-with-BrightLocal-Anywhere), [BrightLocal Help: Does BrightLocal provide APIs?](https://help.brightlocal.com/hc/en-us/articles/203649917-Does-BrightLocal-provide-APIs), [BrightLocal: What is BrightLocal's MCP Server?](https://www.brightlocal.com/blog/introducing-mcp-server/)

## Quick reference

```text
BrightLocal has a full REST API, the Management APIs and Data APIs, and an official MCP server, BrightLocal Anywhere, that only reads (checked 23 Oct 2026). The MCP server needs an active Grow plan and Labs access, and BrightLocal says it cannot change anything in your account. The REST API needs an API key from BrightLocal support and a developer.
Cotlet provides a hosted MCP server and REST API for BrightLocal: 11 tools (7 read, 4 write).
Access       Sign up at https://cotlet.dev/app/signup?app=brightlocal, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    brightlocal_read, brightlocal_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/brightlocal, each operation at its own route, e.g. PATCH /api/v1/brightlocal/reports/{report_id}/rank-tracker-keywords
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_locations, list_rank_tracker_reports, get_rank_tracker_report, get_local_search_grid_report, list_reviews, get_citation_tracker_report, list_active_sync_alerts, update_rank_tracker_keywords, rerun_report, respond_to_review, set_review_status
Confirm      rerun_report, respond_to_review (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/brightlocal-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=brightlocal, requests BrightLocal in the Cotlet console and creates an API key there.
2. The user signs in to BrightLocal once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables BrightLocal 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 BrightLocal 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 BrightLocal 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 BrightLocal 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 BrightLocal 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 BrightLocal's terms; Cotlet is not affiliated with BrightLocal.
```

## What can an AI agent do in BrightLocal?

Cotlet is best for local SEO agencies and multi-location brands who need rank drops, review replies and keyword changes handled by an AI agent without running or fixing a server.

- **[Weekly local rank drop report](https://cotlet.dev/integrations/brightlocal-api-mcp-server/weekly-rank-drop-report.md)** (runs: weekly): "Every Monday, check all Local Rank Tracker reports for locations whose average Google position got worse since the last run, and list the keywords that dropped the most." → `list_rank_tracker_reports`, `get_rank_tracker_report`
- **[Reply to new Google reviews](https://cotlet.dev/integrations/brightlocal-api-mcp-server/reply-to-google-reviews.md)** (runs: daily): "Find new 4 and 5 star Google reviews across all locations that are still Unread, reply with a short thank-you using the reviewer's first name, and mark each one handled. Leave anything under 4 stars for me." → `list_reviews`, `respond_to_review`, `set_review_status`
- **[Update rank tracker keywords for many locations](https://cotlet.dev/integrations/brightlocal-api-mcp-server/bulk-update-rank-tracker-keywords.md)**: "Add "invisalign" plus the city to the keywords of every Local Rank Tracker report in the Texas group, then re-run those reports." → `list_rank_tracker_reports`, `update_rank_tracker_keywords`, `rerun_report`
- **Check citations for inconsistent name, address and phone** (runs: weekly): "For every Citation Tracker report, list citations where the name, address or phone differs from our business details." → `list_locations`, `get_citation_tracker_report`
- **Review pending Active Sync alerts**: "List the open Active Sync alerts across all locations, grouped by listing, with what BrightLocal holds and what changed." → `list_active_sync_alerts`

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

Yes. Cotlet does not replace your automation platform: it gives it a BrightLocal 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 weekly local rank drop report, 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/brightlocal/rank-tracker-reports. | 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/brightlocal/rank-tracker-reports with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 11 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 BrightLocal.

### list_locations

List the locations in the account, as on All Locations. Access: read. REST: `GET /api/v1/brightlocal/locations`. MCP: `brightlocal_read → list_locations`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `query` | string | no | Business name or zip code to search for. |
| `status` | string | no | Active or ad_hoc. Active locations can run scheduled reports; Ad-hoc locations run manual reports only. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns each location with its ID, business name, city and whether it is Active or Ad-hoc. Results come in the order of the All Locations page. Any user of the account can read it; the reports you see follow your role.

Example response:

```json
{
  "locations": [
    {
      "location_id": "loc_1180",
      "name": "Harbor Dental",
      "city": "Austin",
      "status": "active"
    },
    {
      "location_id": "loc_1204",
      "name": "Lakeside Dental",
      "city": "Round Rock",
      "status": "active"
    }
  ],
  "next_cursor": null
}
```

### list_rank_tracker_reports

List Local Rank Tracker reports with their latest run and average Google position. Access: read. REST: `GET /api/v1/brightlocal/rank-tracker-reports`. MCP: `brightlocal_read → list_rank_tracker_reports`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | string | no | Only reports of this location. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns one row per report: location, schedule (weekly, monthly or ad_hoc), date of the latest run, number of tracked keywords and the average Google position of that run. Use the report_id with get_rank_tracker_report.

Example response:

```json
{
  "reports": [
    {
      "report_id": "lrt_4821",
      "location": "Harbor Dental, Austin",
      "schedule": "weekly",
      "last_run": "2026-10-19",
      "keywords": 4,
      "average_google_position": 6.5
    },
    {
      "report_id": "lrt_4822",
      "location": "Lakeside Dental, Round Rock",
      "schedule": "weekly",
      "last_run": "2026-10-19",
      "keywords": 38,
      "average_google_position": 4.2
    }
  ],
  "next_cursor": null
}
```

### get_rank_tracker_report

Read one Local Rank Tracker report: average position, movement and keyword positions. Access: read. REST: `GET /api/v1/brightlocal/reports/{report_id}/rank-tracker-report`. MCP: `brightlocal_read → get_rank_tracker_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `report_id` | string | yes | Report ID from list_rank_tracker_reports. |

Returns the current and previous average Google position, Keyword Change and Positional Change against the previous run, and the keyword table with the old and new position of each keyword. Keyword Change is keywords moved up minus keywords moved down. Positional Change is places gained minus places lost.

Example response:

```json
{
  "report_id": "lrt_4821",
  "location": "Harbor Dental, Austin",
  "run_date": "2026-10-19",
  "previous_run_date": "2026-10-12",
  "average_google_position": 6.5,
  "previous_average_google_position": 5.25,
  "keyword_change": -1,
  "positional_change": -5,
  "keywords": [
    {
      "keyword": "dentist austin",
      "position": 3,
      "previous_position": 2
    },
    {
      "keyword": "emergency dentist austin",
      "position": 9,
      "previous_position": 4
    },
    {
      "keyword": "teeth whitening austin",
      "position": 7,
      "previous_position": 8
    },
    {
      "keyword": "dental implants near me",
      "position": 7,
      "previous_position": 7
    }
  ]
}
```

### get_local_search_grid_report

Read the latest run of a Local Search Grid report: average rank per keyword. Access: read. REST: `GET /api/v1/brightlocal/reports/{report_id}/local-search-grid-report`. MCP: `brightlocal_read → get_local_search_grid_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `report_id` | string | yes | Local Search Grid report ID. |

Returns the average rank per keyword and how many grid points show NF and how many show a dash. NF means Google found no local business results at that point. A dash means Google returned results but the business is not in the top 100.

Example response:

```json
{
  "report_id": "lsg_3305",
  "location": "Harbor Dental, Austin",
  "run_date": "2026-10-19",
  "keywords": [
    {
      "keyword": "dentist",
      "average_rank": 7.8,
      "nf_points": 0,
      "outside_top_100_points": 2
    },
    {
      "keyword": "emergency dentist",
      "average_rank": 12.4,
      "nf_points": 1,
      "outside_top_100_points": 3
    }
  ]
}
```

### list_reviews

List reviews from Review Inbox with their status. Access: read. REST: `GET /api/v1/brightlocal/reviews`. MCP: `brightlocal_read → list_reviews`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | string | no | Only reviews of this location. |
| `source` | string | no | Review site, for example Google, Facebook or Yelp. |
| `status` | string | no | Unread, Action Required, Do Not Respond, Manually Responded, Auto-Responded, Pending Removal, Successfully Removed or Removal Failed. |
| `rating` | integer | no | Only reviews with this star rating. |
| `since` | string | no | ISO date; only reviews from this day on. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the date, source, rating, review text and status of each review, newest first. can_respond is true only for Google and Facebook reviews of a location connected to Reputation Manager; for other sites BrightLocal offers a link to the listing.

Example response:

```json
{
  "reviews": [
    {
      "review_id": "rv_91c2",
      "location": "Harbor Dental, Austin",
      "source": "Google",
      "rating": 5,
      "date": "2026-10-21",
      "author": "Dana R.",
      "text": "Dr. Lee made my whitening visit painless. Booking was easy too.",
      "status": "Unread",
      "can_respond": true
    },
    {
      "review_id": "rv_77d4",
      "location": "Harbor Dental, Austin",
      "source": "Yelp",
      "rating": 2,
      "date": "2026-10-20",
      "author": "Sam T.",
      "text": "Waited 40 minutes past my appointment time.",
      "status": "Unread",
      "can_respond": false
    }
  ],
  "next_cursor": null
}
```

### get_citation_tracker_report

Read the citations a Citation Tracker report found and whether they match your business details. Access: read. REST: `GET /api/v1/brightlocal/reports/{report_id}/citation-tracker-report`. MCP: `brightlocal_read → get_citation_tracker_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `report_id` | string | yes | Citation Tracker report ID. |

Returns each citation with the site, URL and the name, address and phone found there, and whether they match the report's business details. Archived citations are left out; BrightLocal blacklists an archived citation page so it does not return on later runs.

Example response:

```json
{
  "report_id": "ct_2290",
  "location": "Harbor Dental, Austin",
  "citations": [
    {
      "site": "yelp.com",
      "url": "https://www.yelp.com/biz/harbor-dental-austin",
      "name": "Harbor Dental",
      "phone": "+1 512 555 0142",
      "matches": true
    },
    {
      "site": "yellowpages.com",
      "url": "https://www.yellowpages.com/austin-tx/mip/harbor-dental-1",
      "name": "Harbor Dental Care",
      "phone": "+1 512 555 0199",
      "matches": false
    }
  ]
}
```

### list_active_sync_alerts

List alerts from the Alert Inbox where a listing changed. Access: read. REST: `GET /api/v1/brightlocal/active-sync-alerts`. MCP: `brightlocal_read → list_active_sync_alerts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | string | no | Only alerts of this location. |
| `listing` | string | no | Platform, for example Google Business Profile, Facebook, Apple or Bing. |
| `cursor` | string | no | Next page cursor from the previous call. |

Returns the location, listing, date and time, the data BrightLocal holds and the change detected. Active Sync needs a Manage or Grow plan and an Active location. This tool does not accept or reject a change; that stays in the Alert Inbox.

Example response:

```json
{
  "alerts": [
    {
      "alert_id": "al_5512",
      "location": "Harbor Dental, Austin",
      "listing": "Google Business Profile",
      "created_at": "2026-10-21T08:14:00Z",
      "data_in_brightlocal": "Mon-Fri 8:00-17:00",
      "change_detected": "Mon-Fri 9:00-17:00"
    }
  ],
  "next_cursor": null
}
```

### update_rank_tracker_keywords

Replace the search terms of a Local Rank Tracker report. Access: write. REST: `PATCH /api/v1/brightlocal/reports/{report_id}/rank-tracker-keywords`. MCP: `brightlocal_write → update_rank_tracker_keywords`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `report_id` | string | yes | Report ID from list_rank_tracker_reports. |
| `keywords` | string[] | yes | The full list of search terms to track, one per item, up to 100. |

Saves the list under Search Settings of the report and returns what was added and removed. A list over 100 terms is rejected. BrightLocal shows the new keywords only after the next run. It reaches no one and a second call with the old list undoes it, so it does not ask for your OK by default.

Example response:

```json
{
  "report_id": "lrt_4821",
  "location": "Harbor Dental, Austin",
  "keyword_count": 5,
  "added": [
    "invisalign austin"
  ],
  "removed": [],
  "takes_effect": "next run"
}
```

### rerun_report

Start a new run of a Local Rank Tracker or Local Search Grid report now. Access: write, asks the user first. REST: `POST /api/v1/brightlocal/reports/{report_id}/rerun`. MCP: `brightlocal_write → rerun_report`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `report_id` | string | yes | Report ID from list_rank_tracker_reports. |
| `report_type` | string | yes | rank_tracker or local_search_grid. |

Starts the run and returns at once; BrightLocal shows Updating data... under the tool's name on the Location Dashboard until it finishes. On an Ad-hoc location each manual run uses an Ad-hoc Report Run. A run cannot be undone. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "report_id": "lrt_4821",
  "report_type": "rank_tracker",
  "status": "running"
}
```

### respond_to_review

Post a reply to a Google or Facebook review, as the Respond button does. Access: write, asks the user first. REST: `POST /api/v1/brightlocal/reviews/{review_id}/replies`. MCP: `brightlocal_write → respond_to_review`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `review_id` | string | yes | Review ID from list_reviews. |
| `body` | string | yes | Reply text, up to 350 characters. |

Posts the reply under the connected Google Business Profile or Facebook page. It works only for reviews with can_respond true and the status Unread or Action Required. A longer reply is rejected before it is sent, and a review from another site fails with the link to its listing. The reply is public. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "review_id": "rv_91c2",
  "source": "Google",
  "reply_length": 107,
  "sent_at": "2026-10-22T09:02:00Z"
}
```

### set_review_status

Set the Status of a review in Review Inbox. Access: write. REST: `PUT /api/v1/brightlocal/reviews/{review_id}/status`. MCP: `brightlocal_write → set_review_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `review_id` | string | yes | Review ID from list_reviews. |
| `status` | string | yes | Unread, Action Required, Do Not Respond or Manually Responded. |

Changes only the status label that BrightLocal users see in Review Inbox. It sends nothing to the review site and a second call sets it back, so it does not ask for your OK by default.

Example response:

```json
{
  "review_id": "rv_77d4",
  "status": "Action Required"
}
```

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

Connecting BrightLocal takes three steps: sign up, sign in to BrightLocal 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 BrightLocal to your agent.

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

2. **Sign in to BrightLocal in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to BrightLocal 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 BrightLocal 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.

```
Every Monday, check all Local Rank Tracker reports for locations whose average Google position got worse since the last run, and list the keywords that dropped the most.
```

### Call BrightLocal 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/brightlocal 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 PATCH https://cotlet.dev/api/v1/brightlocal/reports/lrt_4821/rank-tracker-keywords \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keywords":["dentist austin","emergency dentist austin","teeth whitening austin","dental implants near me","invisalign austin"]}'
```

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

```
{
  "report_id": "lrt_4821",
  "location": "Harbor Dental, Austin",
  "keyword_count": 5,
  "added": [
    "invisalign austin"
  ],
  "removed": [],
  "takes_effect": "next run"
}
```

## Why use Cotlet for BrightLocal?

**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 BrightLocal 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 BrightLocal changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect BrightLocal to Cotlet?

Yes. You sign in to BrightLocal yourself, in your own Cloud Browser, and we never save your password. Your agents only get BrightLocal 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 BrightLocal integration?**

No, Cotlet is independent of BrightLocal. BrightLocal's own API is too limited for this work. Cotlet works through your own BrightLocal account, the way you use BrightLocal 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 BrightLocal in your console: your agents lose access at once and you stay signed in. Signing out of BrightLocal in the browser works too, and Reset browser deletes the whole profile.

## Is there a BrightLocal MCP server on GitHub?

The realistic options are BrightLocal's own APIs and its read-only MCP server. A script on the REST API can change keywords and run reports, but you need an API key from BrightLocal support, a developer and upkeep. The MCP server needs the Grow plan and Labs access and only answers questions. Cotlet works in your own account, reads and writes, and our team keeps it working.

|  | BrightLocal API | Cotlet |
|---|---|---|
| Setup | Ask support for an API key, then write and host the code | Sign up, sign in to BrightLocal once, add one MCP server or API key |
| When BrightLocal changes | Your developer follows the API docs and fixes the script | Our team tests it daily and fixes it for you; failed calls are free |
| Your BrightLocal session | An API key you store and rotate yourself | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | The key works until support replaces it | Your Cloud Browser keeps you signed in; if BrightLocal logs you out, your agent gets a link to sign in again |
| Upkeep | You write, monitor and debug the integration | Nothing to host or update |
| Where it runs | Wherever you host it | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Management APIs are free within your plan limits; developer time is not | 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 BrightLocal 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 BrightLocal API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the BrightLocal 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 BrightLocal 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 BrightLocal 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 BrightLocal only after you enable it. When BrightLocal 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 BrightLocal, sign out of BrightLocal 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.
- **BrightLocal's terms:** You use your own BrightLocal account and stay responsible for following BrightLocal's terms. Cotlet is independent and not affiliated with BrightLocal. [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 BrightLocal in the console and press Request access. Then you create your API key and connect BrightLocal there.

**Do I need to be technical?**

No. You sign in to BrightLocal 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 BrightLocal to Cotlet?**

Yes. You sign in to BrightLocal yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get BrightLocal 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 BrightLocal 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 BrightLocal 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 BrightLocal's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. BrightLocal 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 BrightLocal 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?**

BrightLocal 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 Grow plan?**

No. Cotlet works in your own BrightLocal account. The Grow plan and Labs access are conditions of BrightLocal Anywhere, the official read-only MCP server. What your agent can do still follows your plan: Active Sync needs a Manage or Grow plan and an Active location, and daily Reputation Manager runs need the Daily Review Tracking add-on.

**Can my agent reply to every review?**

No. BrightLocal sends replies from the app only to Google and Facebook reviews of locations connected to Reputation Manager, up to 350 characters, and only while the review is Unread or Action Required. For other review sites, respond_to_review returns the link to the listing.

**Does a re-run use up anything?**

On an Ad-hoc location each manual report run uses an Ad-hoc Report Run from your plan. Check the count under All Locations before you let an agent re-run many reports.

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

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

**Can I use the BrightLocal 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/brightlocal 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.