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

# AccuRanker API and MCP server

> AccuRanker has an official API and an official MCP server (checked 23 Oct 2026). The Read API and Write API (both v4) come with API access at no additional cost, but need a developer and an API token. The official MCP at connect.accuranker.com/mcp is read-only: it cannot create, edit or delete keywords, tags, domains or settings.

Rank tracking platform for SEO teams and agencies: domains in groups, tracked keywords by search engine, locale and device, tags, competitors, Share of Voice and reports.

## What is the AccuRanker API?

Cotlet's AccuRanker API exposes 11 endpoints for your own AccuRanker account: list domains, list keywords and ranks, get keyword rank history, list tags, list competitors, add keywords, add tags to keywords, remove tags from keywords, add domain, add competitor and delete keywords. The list_domains endpoint returns list the domains your AccuRanker user can open, with their group. Each endpoint takes simple JSON inputs like domain_id, search_engine or tags and works both as an operation of the accuranker_read or accuranker_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 (5 read, 6 write)
- **Updated:** 2026-10-17

AccuRanker has an official API and an official MCP server (checked 23 Oct 2026). Cotlet is a hosted MCP server and REST API for AccuRanker with 11 endpoints (5 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does AccuRanker have an official API?

AccuRanker has an official API and an official MCP server (checked 23 Oct 2026). The Read API and Write API (both v4) come with API access at no additional cost, but need a developer and an API token. The official MCP at connect.accuranker.com/mcp is read-only: it cannot create, edit or delete keywords, tags, domains or settings.

| Task | AccuRanker official | Cotlet |
|---|---|---|
| List domains and competitors | Yes: Read API and official MCP | Yes |
| List keywords with current ranks | Yes: Read API and official MCP | Yes |
| Rank history of one keyword | Yes: Read API and official MCP | Yes |
| List tags | Yes: Official MCP list_tags | Yes |
| Add keywords to a domain | Partly: Write API creates keywords with a token; the official MCP cannot | Yes |
| Add a domain | Partly: Write API creates domains with a token; the official MCP cannot | Yes |
| Delete keywords | Partly: Write API has a DELETE endpoint for keywords; the official MCP cannot | Yes |
| Add or remove tags in bulk | No: The official MCP is read-only and the Write API pages name groups, domains and keywords | Yes |

Sources: [AccuRanker Help: Connecting to AccuRanker MCP](https://www.accuranker.com/help/getting-started/connecting-to-accuranker-mcp/), [AccuRanker Help: MCP tool reference](https://www.accuranker.com/help/getting-started/accuranker-mcp-tool-reference/), [AccuRanker: API and integrations](https://www.accuranker.com/features/api-integrations/), [AccuRanker Write API (v4)](https://app.accuranker.com/api/write-docs)

## Quick reference

```text
AccuRanker has an official API and an official MCP server (checked 23 Oct 2026). The Read API and Write API (both v4) come with API access at no additional cost, but need a developer and an API token. The official MCP at connect.accuranker.com/mcp is read-only: it cannot create, edit or delete keywords, tags, domains or settings.
Cotlet provides a hosted MCP server and REST API for AccuRanker: 11 tools (5 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=accuranker, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    accuranker_read, accuranker_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/accuranker, each operation at its own route, e.g. POST /api/v1/accuranker/domains/{domain_id}/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_domains, list_keywords, get_keyword_history, list_tags, list_competitors, add_keywords, add_tags, remove_tags, add_domain, add_competitor, delete_keywords
Confirm      add_keywords, delete_keywords (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/accuranker-api-mcp-server.md

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

## What can an AI agent do in AccuRanker?

Cotlet is best for SEO managers and agencies who use AccuRanker and want their AI agent to add keywords, tag them and set up client domains without running or fixing a server.

- **[Bulk add keywords to a domain](https://cotlet.dev/integrations/accuranker-api-mcp-server/bulk-add-keywords.md)** (runs: weekly): "Add these 40 keywords to the Acme Outdoors domain in AccuRanker. Track them on Google in the United States, desktop and mobile, tag them q4-launch, and tell me how many tracked keywords that adds before you start." → `list_domains`, `list_keywords`, `add_keywords`
- **[Tag keywords in bulk](https://cotlet.dev/integrations/accuranker-api-mcp-server/tag-keywords-in-bulk.md)** (runs: weekly): "In AccuRanker, find the keywords on Acme Outdoors whose landing page is under /pricing and tag them pricing-pages. Remove the tag q3-test from every keyword that still has it." → `list_keywords`, `add_tags`, `remove_tags`
- **[Set up a new client domain with competitors](https://cotlet.dev/integrations/accuranker-api-mcp-server/set-up-new-client-domain.md)**: "Set up acme-outdoors.com in AccuRanker for a new client: put it in the Clients group, default to Google United States, add rei.com and backcountry.com as competitors, and add the keywords from my brief." → `add_domain`, `add_competitor`, `add_keywords`
- **Weekly keyword rank drops report** (runs: weekly): "Every Monday, list the keywords on Acme Outdoors that lost more than 5 positions since last week and tell me which landing pages they point to." → `list_domains`, `list_keywords`, `get_keyword_history`
- **Clean up keywords nobody needs**: "On Acme Outdoors, find keywords tagged q3-test and delete them. Show me the list first." → `list_keywords`, `delete_keywords`

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

Yes. Cotlet does not replace your automation platform: it gives it a AccuRanker 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 bulk add keywords to a domain, 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/accuranker/domains. | 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/accuranker/domains 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 AccuRanker.

### list_domains

List the domains your AccuRanker user can open, with their group. Access: read. REST: `GET /api/v1/accuranker/domains`. MCP: `accuranker_read → list_domains`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `search` | string | no | Part of a domain name or display name. |
| `group` | string | no | Group name; leave out for all groups. |

Returns each domain with its ID, display name, group and the number of tracked keywords. Use the domain_id in every other tool. Domains come in the order of the Domains tab.

Example response:

```json
{
  "domains": [
    {
      "domain_id": "48213",
      "domain": "acme-outdoors.com",
      "display_name": "Acme Outdoors",
      "group": "Clients",
      "tracked_keywords": 212
    },
    {
      "domain_id": "48377",
      "domain": "northpeak.io",
      "display_name": "Northpeak",
      "group": "Clients",
      "tracked_keywords": 96
    }
  ]
}
```

### list_keywords

List the tracked keywords of one domain with current rank, change and landing page. Access: read. REST: `GET /api/v1/accuranker/domains/{domain_id}/keywords`. MCP: `accuranker_read → list_keywords`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `domain_id` | string | yes | Domain ID from list_domains. |
| `search` | string | no | Part of a keyword. |
| `tag` | string | no | Only keywords with this tag. |
| `search_engine` | string | no | Google, Bing, Baidu or YouTube. |
| `cursor` | string | no | next_cursor from the previous page; leave out for the first page. |

Returns the rows of the Keywords tab: keyword ID, keyword, search engine, device, location, current rank, change since the compare date, landing page URL and tags. Rows come in the order the tab shows them; follow next_cursor for the rest. A keyword with no rank yet has rank null.

Example response:

```json
{
  "keywords": [
    {
      "keyword_id": "k_90311",
      "keyword": "rank tracking software",
      "search_engine": "Google",
      "device": "desktop",
      "location": "United States",
      "rank": 4,
      "change": 2,
      "landing_page": "https://acme-outdoors.com/pricing",
      "tags": [
        "pricing-pages"
      ]
    },
    {
      "keyword_id": "k_90312",
      "keyword": "keyword rank checker",
      "search_engine": "Google",
      "device": "mobile",
      "location": "United States",
      "rank": 7,
      "change": 5,
      "landing_page": "https://acme-outdoors.com/pricing/teams",
      "tags": []
    }
  ],
  "next_cursor": null
}
```

### get_keyword_history

Get the rank of one keyword over a date range. Access: read. REST: `GET /api/v1/accuranker/keywords/{keyword_id}/history`. MCP: `accuranker_read → get_keyword_history`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `keyword_id` | string | yes | Keyword ID from list_keywords. |
| `period_from` | string | no | First date, YYYY-MM-DD. |
| `period_to` | string | no | Last date, YYYY-MM-DD. |

Returns one point per date AccuRanker has a rank for, oldest first, with the ranking URL. Dates without a rank check are not filled in. Leave both dates out for the history the keyword shows by default.

Example response:

```json
{
  "keyword_id": "k_90311",
  "keyword": "rank tracking software",
  "history": [
    {
      "date": "2026-10-16",
      "rank": 6,
      "url": "https://acme-outdoors.com/pricing"
    },
    {
      "date": "2026-10-23",
      "rank": 4,
      "url": "https://acme-outdoors.com/pricing"
    }
  ]
}
```

### list_tags

List the tags of one domain with their type and keyword count. Access: read. REST: `GET /api/v1/accuranker/domains/{domain_id}/tags`. MCP: `accuranker_read → list_tags`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `domain_id` | string | yes | Domain ID from list_domains. |

Returns the rows of the Tag Cloud: tag name, static or dynamic, and how many keywords carry it. Use it before tagging to reuse an existing spelling.

Example response:

```json
{
  "tags": [
    {
      "tag": "pricing-pages",
      "type": "static",
      "keywords": 23
    },
    {
      "tag": "q3-test",
      "type": "static",
      "keywords": 31
    },
    {
      "tag": "top-movers",
      "type": "dynamic",
      "keywords": 12
    }
  ]
}
```

### list_competitors

List the competitors tracked on one domain. Access: read. REST: `GET /api/v1/accuranker/domains/{domain_id}/competitors`. MCP: `accuranker_read → list_competitors`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `domain_id` | string | yes | Domain ID from list_domains. |

Returns the rows of the Competitors tab: competitor domain and its Google Business name when one is set.

Example response:

```json
{
  "competitors": [
    {
      "competitor_id": "c_2201",
      "domain": "rei.com",
      "google_business_name": null
    },
    {
      "competitor_id": "c_2202",
      "domain": "backcountry.com",
      "google_business_name": null
    }
  ]
}
```

### add_keywords

Add keywords to a domain with search engine, locale, devices, location and tags. Access: write, asks the user first. REST: `POST /api/v1/accuranker/domains/{domain_id}/keywords`. MCP: `accuranker_write → add_keywords`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `domain_id` | string | yes | Domain ID from list_domains. |
| `keywords` | string[] | yes | Keywords to track. |
| `search_engine` | string | no | Google, Bing, Baidu or YouTube. Leave out for the domain default. |
| `country_locale` | string | no | Country and language as the locale picker names them, for example United States (English). Leave out for the domain default. |
| `devices` | string[] | no | desktop, mobile or both. Leave out for the domain default. |
| `location` | string | no | City or address; leave out for country-level data. |
| `tags` | string[] | no | Static tags to put on every added keyword. |

Returns how many keywords were added and how many tracked keywords that makes, because AccuRanker counts a keyword once per country locale, search engine, device and location. Keywords AccuRanker refuses come back in rejected with a reason. This changes your plan usage and is undone by deleting the keywords. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "domain_id": "48213",
  "added_keywords": 3,
  "tracked_keywords_added": 6,
  "search_engine": "Google",
  "country_locale": "United States (English)",
  "devices": [
    "desktop",
    "mobile"
  ],
  "tags": [
    "q4-launch"
  ],
  "rejected": []
}
```

### add_tags

Put static tags on keywords. Access: write. REST: `POST /api/v1/accuranker/domains/{domain_id}/tags`. MCP: `accuranker_write → add_tags`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `domain_id` | string | yes | Domain ID from list_domains. |
| `keyword_ids` | string[] | yes | Keyword IDs from list_keywords. |
| `tags` | string[] | yes | Tag names. A tag that does not exist is created. |

Returns how many keywords were tagged and the tags applied. The tags are static and stay until removed. It reaches no one and is undone with remove_tags, so it does not wait for your OK.

Example response:

```json
{
  "tagged_keywords": 3,
  "tags_applied": [
    "pricing-pages"
  ],
  "tag_type": "static"
}
```

### remove_tags

Take static tags off keywords. Access: write. REST: `DELETE /api/v1/accuranker/domains/{domain_id}/tags`. MCP: `accuranker_write → remove_tags`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `domain_id` | string | yes | Domain ID from list_domains. |
| `keyword_ids` | string[] | yes | Keyword IDs from list_keywords. |
| `tags` | string[] | yes | Tag names to remove. |

Returns how many keywords lost a tag. The tag stays in the Tag Cloud, and a dynamic tag is skipped and listed in skipped, because AccuRanker removes dynamic tags by itself. It reaches no one and is undone with add_tags, so it does not wait for your OK.

Example response:

```json
{
  "untagged_keywords": 31,
  "tags_removed": [
    "q3-test"
  ],
  "skipped": []
}
```

### add_domain

Add a domain to a group with its default search settings. Access: write. REST: `POST /api/v1/accuranker/domains`. MCP: `accuranker_write → add_domain`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `domain_name` | string | yes | Domain without https:// and www. |
| `group` | string | yes | Name of an existing group. |
| `display_name` | string | no | Label shown in your data. |
| `search_engine` | string | no | Default search engine: Google, Bing, Baidu or YouTube. |
| `country_locale` | string | no | Default country and language, for example United States (English). |
| `location` | string | no | Default location; leave out for country level. |
| `google_business_name` | string | no | Helps find local ranking data. |
| `include_subdomains` | boolean | no | Count results from subdomains. |
| `exact_match` | boolean | no | Count only results whose URL exactly matches the domain name. |

Returns the new domain with its ID. A group that does not exist fails with GROUP_NOT_FOUND; create the group in AccuRanker first. It adds no keywords, reaches no one and is undone by deleting the domain in the app, so it does not wait for your OK.

Example response:

```json
{
  "domain_id": "48501",
  "domain": "acme-outdoors.com",
  "display_name": "Acme Outdoors",
  "group": "Clients",
  "default_search_engine": "Google",
  "default_country_locale": "United States (English)"
}
```

### add_competitor

Add a competitor domain to a domain. Access: write. REST: `POST /api/v1/accuranker/domains/{domain_id}/competitors`. MCP: `accuranker_write → add_competitor`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `domain_id` | string | yes | Domain ID from list_domains. |
| `competitor_domain` | string | yes | Competitor domain without https:// and www. |
| `google_business_name` | string | no | Optional Google Business name of the competitor. |

Returns the competitor with its ID. It reaches no one and is removed with the delete button on the Competitors tab, so it does not wait for your OK.

Example response:

```json
{
  "competitor_id": "c_2203",
  "domain": "rei.com",
  "google_business_name": null
}
```

### delete_keywords

Delete keywords from a domain. Access: write, asks the user first. REST: `DELETE /api/v1/accuranker/domains/{domain_id}/keywords`. MCP: `accuranker_write → delete_keywords`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `domain_id` | string | yes | Domain ID from list_domains. |
| `keyword_ids` | string[] | yes | Keyword IDs from list_keywords. |

Returns how many keywords were deleted. AccuRanker's guide does not say whether the rank history of a deleted keyword is kept, and Cotlet cannot bring a keyword back, so the agent lists the keywords and waits for you. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "deleted_keywords": 31,
  "domain_id": "48213"
}
```

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

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

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

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

```
Add these 40 keywords to the Acme Outdoors domain in AccuRanker. Track them on Google in the United States, desktop and mobile, tag them q4-launch, and tell me how many tracked keywords that adds before you start.
```

### Call AccuRanker 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/accuranker 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/accuranker/domains/48213/keywords \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"keywords":["rank tracking software","keyword rank checker","seo rank tracker"],"search_engine":"Google","country_locale":"United States (English)","devices":["desktop","mobile"],"tags":["q4-launch"]}'
```

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

```
{
  "domain_id": "48213",
  "added_keywords": 3,
  "tracked_keywords_added": 6,
  "search_engine": "Google",
  "country_locale": "United States (English)",
  "devices": [
    "desktop",
    "mobile"
  ],
  "tags": [
    "q4-launch"
  ],
  "rejected": []
}
```

## Why use Cotlet for AccuRanker?

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

## Is it safe to connect AccuRanker to Cotlet?

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

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

## Is there a AccuRanker MCP server on GitHub?

Yes. AccuRanker offers an official MCP server for reading rank data, included with an AccuRanker or AccuLLM subscription, and a Write API for developers. Use the official MCP for reports. For adding keywords, tags, domains and competitors without writing code, Cotlet works in your signed-in AccuRanker account and runs next to it.

|  | Official MCP and Write API | Cotlet |
|---|---|---|
| Setup | MCP: add one URL and log in. Write API: a developer builds the calls with an API token | Sign up, sign in to AccuRanker once, add one MCP server or API key |
| What it does | MCP reads domains, keywords, rank history and AccuLLM data. The Write API creates groups, domains and keywords | Adds keywords, tags, domains and competitors, deletes keywords and reads ranks, the way you do in the app |
| When AccuRanker changes | AccuRanker maintains the MCP and API | Our team tests it daily and fixes it for you; failed calls are free |
| Your AccuRanker session | Your AccuRanker login authorizes the assistant | 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 assistant asks you to authenticate again | Your Cloud Browser keeps you signed in; if AccuRanker logs you out, your agent gets a link to sign in again |
| Where it runs | In the assistant you connect it to | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | MCP included with your subscription; API calls at no additional cost | 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 AccuRanker 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 AccuRanker API cost?

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

**Do I need to be technical?**

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

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

AccuRanker 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 API access in AccuRanker?**

No. Cotlet works in your own signed-in AccuRanker account, so it needs no API token. The official MCP does need API access on your user: AccuRanker's help says to contact support if you get an API access error. The AI visibility data of AccuLLM is part of the official MCP only with an active AccuLLM plan.

**Should I use the official MCP or Cotlet?**

Use both. The official MCP at connect.accuranker.com/mcp reads domains, keywords, rank history and AccuLLM data, and is included with an AccuRanker or AccuLLM subscription. Cotlet adds the writes the MCP cannot do: adding keywords, tags, domains and competitors, and deleting keywords.

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

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

**Can I use the AccuRanker 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/accuranker 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.