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

# Plausible API and MCP server

> Plausible has an official API, but a limited one (checked 22 Oct 2026). The Stats API only reads data and needs the Business plan, the Sites API that creates sites, goals and shared links is Enterprise only, and there is no official MCP server.

Privacy-friendly web analytics: a one-page dashboard of visitors, sources, pages and goals for each site, with shared links, email reports and team access.

## What is the Plausible API?

Cotlet's Plausible API exposes 14 endpoints for your own Plausible account: list sites, get site stats, get top pages, get traffic sources, list goals, get goal conversions, list shared links, list guests and invitations, create site, add goal, create shared link, invite guest, set email reports and add annotation. The list_sites endpoint returns list the sites on the Sites page with their visitors in the last 24 hours. Each endpoint takes simple JSON inputs like site, from or to and works both as an operation of the plausible_read or plausible_write MCP tool for agents and as a REST call for scripts.

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

Plausible has an official API, but a limited one (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Plausible with 14 endpoints (8 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Plausible have an official API?

Plausible has an official API, but a limited one (checked 22 Oct 2026). The Stats API only reads data and needs the Business plan, the Sites API that creates sites, goals and shared links is Enterprise only, and there is no official MCP server.

| Task | Plausible official | Cotlet |
|---|---|---|
| Read visitors, pageviews, sources and pages | Partly: Stats API, Business plan and up | Yes |
| List sites | Partly: Read-only call, needs a Stats API key (Business plan) | Yes |
| Create a site | Partly: Sites API, Enterprise only | Yes |
| Add goals | Partly: Sites API, Enterprise only | Yes |
| Create shared links | Partly: Sites API, Enterprise only | Yes |
| Invite guests to a site | Partly: Sites API, Enterprise only | Yes |
| Set email reports | No | Yes |
| Add annotations | No | Yes |

Sources: [Plausible Docs: APIs and data access](https://plausible.io/docs/data-access), [Plausible Docs: Stats API](https://plausible.io/docs/stats-api), [Plausible Docs: Sites API](https://plausible.io/docs/sites-api), [Plausible Docs: Subscription plans](https://plausible.io/docs/subscription-plans)

## For AI agents

```text
Plausible has an official API, but a limited one (checked 22 Oct 2026). The Stats API only reads data and needs the Business plan, the Sites API that creates sites, goals and shared links is Enterprise only, and there is no official MCP server.
Cotlet provides a hosted MCP server and REST API for Plausible: 14 tools (8 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=plausible, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    plausible_read, plausible_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/plausible, each operation at its own route, e.g. POST /api/v1/plausible/shared-links
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_sites, get_site_stats, get_top_pages, get_sources, list_goals, get_goal_conversions, list_shared_links, list_site_people, create_site, add_goal, create_shared_link, invite_guest, set_email_reports, add_annotation
Confirm      create_shared_link, invite_guest, set_email_reports, add_annotation (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/plausible-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=plausible, requests Plausible in the Cotlet console and creates an API key there.
2. The user signs in to Plausible once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Plausible 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 Plausible server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Plausible MCP server instead.

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 Plausible 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 Plausible 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 Plausible 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 Plausible's terms; Cotlet is not affiliated with Plausible.
```

## What can an AI agent do in Plausible?

Cotlet is best for site owners and agencies on Plausible who need new sites, goals, client dashboard links and weekly traffic reports handled by an AI agent without running or fixing a server.

- **[Set up a new site with goals](https://cotlet.dev/integrations/plausible-api-mcp-server/set-up-new-site-goals.md)**: "Add shop.acme-shop.example to Plausible in the Europe/Warsaw timezone, then add a pageview goal for /checkout/thank-you called "Checkout complete" and a custom event goal "Newsletter Signup"." → `list_sites`, `create_site`, `list_goals`, `add_goal`
- **[Share a client dashboard](https://cotlet.dev/integrations/plausible-api-mcp-server/share-client-dashboard.md)**: "Create a password-protected shared link named "Acme monthly" for acme-shop.example, invite nora@client.example as a Guest Viewer, and tell me the link and who is invited." → `list_shared_links`, `create_shared_link`, `invite_guest`, `list_site_people`
- **[Weekly traffic report](https://cotlet.dev/integrations/plausible-api-mcp-server/weekly-traffic-report.md)** (runs: weekly): "Every Monday, report visitors and pageviews for each of my Plausible sites for last week against the week before, with the top 3 pages, the top 3 sources and goal conversions." → `list_sites`, `get_site_stats`, `get_top_pages`, `get_sources`, `get_goal_conversions`
- **Annotate a launch and check the effect**: "Add a site note on 14 October that says "Launch email sent to 8,000 subscribers", then compare visitors for the three days after with the three days before." → `add_annotation`, `get_site_stats`
- **Find goals that never convert** (runs: weekly): "List the goals of acme-shop.example and tell me which ones had no conversions last week." → `list_goals`, `get_goal_conversions`

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

Yes. Cotlet does not replace your automation platform: it gives it a Plausible 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 traffic 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/plausible/sites. | 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/plausible/sites with your API key. | cron or GitHub Actions. |

## Tools

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

### list_sites

List the sites on the Sites page with their visitors in the last 24 hours. Access: read. REST: `GET /api/v1/plausible/sites`. MCP: `plausible_read → list_sites`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `team` | string | no | Team name. Only needed when your account belongs to more than one team; default is the team you last used. |

Returns one row per site on the Sites page, in the order the page shows them, with the visitor count for the last 24 hours that Plausible prints next to each site. Sites you only see as a guest are listed too. Use it first: every other tool takes a site domain from this list.

Example response:

```json
{
  "team": "Acme Shop",
  "sites": [
    {
      "site": "acme-shop.example",
      "visitors_24h": 612
    },
    {
      "site": "blog.acme-shop.example",
      "visitors_24h": 148
    }
  ]
}
```

### get_site_stats

Read the top stats of a site dashboard for a date range, optionally compared with an earlier one. Access: read. REST: `GET /api/v1/plausible/site-stats`. MCP: `plausible_read → get_site_stats`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |
| `from` | string | no | First day of the date range, YYYY-MM-DD. Default: the last 30 days. |
| `to` | string | no | Last day of the date range, YYYY-MM-DD. Default: today. |
| `compare` | string | no | previous_period or year_over_year. Leave out for no comparison. |

Returns unique visitors, visits, pageviews, views per visit, bounce rate and visit duration for the range, the same numbers as the graph at the top of the dashboard. With compare, it adds the same numbers for the matching earlier range and the change in visitors. The current day is incomplete, so a range that ends today understates it.

Example response:

```json
{
  "site": "acme-shop.example",
  "from": "2026-10-12",
  "to": "2026-10-18",
  "visitors": 4210,
  "visits": 5033,
  "pageviews": 9120,
  "views_per_visit": 1.81,
  "bounce_rate": "58%",
  "visit_duration": "1m 34s",
  "compared_to": {
    "from": "2026-10-05",
    "to": "2026-10-11",
    "visitors": 3890,
    "pageviews": 8410
  },
  "visitors_change": "+8%"
}
```

### get_top_pages

Read the Top Pages report: pages, entry pages or exit pages. Access: read. REST: `GET /api/v1/plausible/top-pages`. MCP: `plausible_read → get_top_pages`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |
| `view` | string | no | pages (default), entry_pages or exit_pages. |
| `from` | string | no | First day of the date range, YYYY-MM-DD. Default: the last 30 days. |
| `to` | string | no | Last day of the date range, YYYY-MM-DD. Default: today. |
| `limit` | integer | no | Rows to return, most visited first. Default 10. |

Returns the rows of the report tab you pick, most visited first, with visitors and pageviews per page path. Each row is a page path, not a full URL. The report has no filter by goal or source in this tool.

Example response:

```json
{
  "site": "acme-shop.example",
  "view": "pages",
  "rows": [
    {
      "page": "/pricing",
      "visitors": 1180,
      "pageviews": 1640
    },
    {
      "page": "/blog/launch-notes",
      "visitors": 902,
      "pageviews": 960
    },
    {
      "page": "/signup",
      "visitors": 455,
      "pageviews": 520
    }
  ]
}
```

### get_sources

Read the Sources report: channels, referrers or campaigns. Access: read. REST: `GET /api/v1/plausible/sources`. MCP: `plausible_read → get_sources`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |
| `view` | string | no | channels (default), referrers or campaigns. |
| `from` | string | no | First day of the date range, YYYY-MM-DD. Default: the last 30 days. |
| `to` | string | no | Last day of the date range, YYYY-MM-DD. Default: today. |

Returns the rows of the Sources tab you pick, most visitors first. The campaigns view lists the UTM data the Campaigns tab shows. A visit with no referrer is listed as direct traffic, the way the dashboard lists it.

Example response:

```json
{
  "site": "acme-shop.example",
  "view": "channels",
  "rows": [
    {
      "source": "Organic Search",
      "visitors": 1480
    },
    {
      "source": "Direct",
      "visitors": 1120
    },
    {
      "source": "Email",
      "visitors": 390
    }
  ]
}
```

### list_goals

List the goals set up in the site settings. Access: read. REST: `GET /api/v1/plausible/goals`. MCP: `plausible_read → list_goals`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |

Returns each goal with its display name, trigger (pageview or custom_event) and the page path or event name it matches. It lists the goals as configured, whether or not anyone has converted yet. Use it before add_goal to avoid a duplicate.

Example response:

```json
{
  "site": "acme-shop.example",
  "goals": [
    {
      "name": "Checkout complete",
      "trigger": "pageview",
      "target": "/checkout/thank-you"
    },
    {
      "name": "Newsletter signup",
      "trigger": "custom_event",
      "target": "Newsletter Signup"
    }
  ]
}
```

### get_goal_conversions

Read the Goals report of the dashboard for a date range. Access: read. REST: `GET /api/v1/plausible/goal-conversions`. MCP: `plausible_read → get_goal_conversions`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |
| `from` | string | no | First day of the date range, YYYY-MM-DD. Default: the last 30 days. |
| `to` | string | no | Last day of the date range, YYYY-MM-DD. Default: today. |
| `goal` | string | no | Display name of one goal. Leave out for all goals. |

Returns the goals report: the visitors who converted, the number of conversions and the conversion rate for each goal. Plausible shows a goal in the dashboard only after its first conversion is recorded, so a goal with no data in the range is missing from this report; compare it with list_goals to find them.

Example response:

```json
{
  "site": "acme-shop.example",
  "from": "2026-10-12",
  "to": "2026-10-18",
  "goals": [
    {
      "goal": "Checkout complete",
      "visitors": 212,
      "conversions": 218,
      "conversion_rate": "5.0%"
    },
    {
      "goal": "Newsletter signup",
      "visitors": 164,
      "conversions": 164,
      "conversion_rate": "3.9%"
    }
  ]
}
```

### list_shared_links

List the shared links of a site from Visibility in the site settings. Access: read. REST: `GET /api/v1/plausible/shared-links`. MCP: `plausible_read → list_shared_links`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |

Returns the name and link of each shared link. The name is the label you gave the link and is not shown to viewers. Plausible never shows a link password again after it is set, so this list cannot return one.

Example response:

```json
{
  "site": "acme-shop.example",
  "links": [
    {
      "name": "Acme monthly",
      "url": "https://plausible.io/share/acme-shop.example?auth=k3T9xQ2mVb7Lw0pD"
    }
  ]
}
```

### list_site_people

List the guests and pending invitations of a site from People in the site settings. Access: read. REST: `GET /api/v1/plausible/site-peoples`. MCP: `plausible_read → list_site_people`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |

Returns each guest with their email and role (Guest Viewer or Guest Editor), and whether the invitation was accepted or is still pending. Invitations expire after 48 hours, so an old pending row means the invitation has lapsed.

Example response:

```json
{
  "site": "acme-shop.example",
  "people": [
    {
      "email": "nora@client.example",
      "role": "Guest Viewer",
      "status": "accepted"
    },
    {
      "email": "sam@client.example",
      "role": "Guest Editor",
      "status": "pending"
    }
  ]
}
```

### create_site

Add a website to your Plausible team from the Sites page. Access: write. REST: `POST /api/v1/plausible/sites`. MCP: `plausible_write → create_site`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `domain` | string | yes | Bare domain without https:// or www., e.g. acme-shop.example. A subdomain such as blog.acme-shop.example makes a separate site. |
| `timezone` | string | no | Reporting timezone as an IANA name, e.g. Europe/Warsaw. Default: the form default. |

Clicks + Add a website with the domain and timezone you give. It does not install the tracking script: the site shows no data until you add the script to the website. It reaches no one. It cannot delete a site, so a wrong domain is removed in Plausible; this tool does not undo it.

Example response:

```json
{
  "domain": "shop.acme-shop.example",
  "timezone": "Europe/Warsaw",
  "status": "created"
}
```

### add_goal

Add a pageview or custom event goal in the site settings. Access: write. REST: `POST /api/v1/plausible/goals`. MCP: `plausible_write → add_goal`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |
| `trigger` | string | yes | pageview or custom_event. |
| `target` | string | yes | Page path for a pageview goal (an asterisk matches a pattern, e.g. /blog*), exact event name for a custom event goal. |
| `display_name` | string | no | Name shown in the Goals report. Default: Plausible fills it from the path or event name. |

Opens Goals in the site settings, clicks + Add goal and saves it. A custom event name must match what your site sends, including capitalisation. Plausible counts a goal only from the moment it exists and does not backfill, and shows it in the dashboard after its first conversion. It reaches no one, and the goal can be edited in the settings at any time.

Example response:

```json
{
  "site": "acme-shop.example",
  "name": "Checkout complete",
  "trigger": "pageview",
  "target": "/checkout/thank-you",
  "status": "added"
}
```

### create_shared_link

Create a shared link to the dashboard under Visibility in the site settings. Access: write, asks the user first. REST: `POST /api/v1/plausible/shared-links`. MCP: `plausible_write → create_shared_link`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |
| `name` | string | yes | Label for your own reference. Viewers do not see it. |
| `password` | string | no | Optional. Viewers must enter it. It can only be set now, not read or changed later. |
| `segment` | string | no | Optional. Name of a site segment to lock the shared dashboard to. Personal segments are not allowed. |

Returns the new link. Anyone with the link sees the dashboard without a Plausible account, and only that site. With a segment, viewers can add filters but cannot remove the segment. Shared-link viewers do not count toward your team member limit. The link goes to other people. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "site": "acme-shop.example",
  "name": "Acme monthly",
  "url": "https://plausible.io/share/acme-shop.example?auth=k3T9xQ2mVb7Lw0pD",
  "password_protected": true,
  "segment": null
}
```

### invite_guest

Invite a guest to one site from People in the site settings. Access: write, asks the user first. REST: `POST /api/v1/plausible/guest/invite`. MCP: `plausible_write → invite_guest`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |
| `email` | string | yes | Email address of the guest. |
| `role` | string | yes | guest_viewer (dashboard only) or guest_editor (dashboard and site settings). |

Plausible emails the invitation. The guest must sign up or log in with that exact address and accept it within 48 hours. Guests count toward your team member limit, and pending invitations count too. Only an Owner or Admin of the team can invite. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "site": "acme-shop.example",
  "email": "nora@client.example",
  "role": "Guest Viewer",
  "status": "invited"
}
```

### set_email_reports

Turn weekly or monthly email reports on or off and add recipients in the site settings. Access: write, asks the user first. REST: `PUT /api/v1/plausible/email-reports`. MCP: `plausible_write → set_email_reports`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |
| `weekly` | boolean | no | Weekly report, sent every Monday. |
| `monthly` | boolean | no | Monthly report, sent on the first day of the month. |
| `add_recipients` | string[] | no | Email addresses to add to Report recipients. |

Sets the Email reports section for the site. The stats are embedded in the email, so recipients need no login, and they do not count toward your team member limit. Recipients you do not list stay as they are; this tool does not remove any. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "site": "acme-shop.example",
  "weekly": true,
  "monthly": false,
  "recipients": [
    "nora@client.example",
    "team@acme-shop.example"
  ]
}
```

### add_annotation

Add a note to a date on the main traffic chart. Access: write, asks the user first. REST: `POST /api/v1/plausible/annotations`. MCP: `plausible_write → add_annotation`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `site` | string | yes | Domain of the site as the Sites page lists it, e.g. acme-shop.example. |
| `date` | string | yes | Date of the note, YYYY-MM-DD. |
| `note` | string | yes | Text of the note, 255 characters at most. |
| `visibility` | string | no | personal (only you) or site (everyone with dashboard access). Default: site. |

Does what right-click > Add note does on the chart. A site note is seen by all team members and by anyone using a shared link, and only team members with editor access or above can add one. Plausible allows 500 annotations per site. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "site": "acme-shop.example",
  "date": "2026-10-14",
  "note": "Launch email sent to 8,000 subscribers",
  "visibility": "site",
  "status": "added"
}
```

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

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

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

2. **Sign in to Plausible in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Plausible 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 Plausible 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 shop.acme-shop.example to Plausible in the Europe/Warsaw timezone, then add a pageview goal for /checkout/thank-you called "Checkout complete" and a custom event goal "Newsletter Signup".
```

### Call Plausible 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/plausible 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/plausible/shared-links \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"site":"acme-shop.example","name":"Acme monthly","password":"river-lamp-42"}'
```

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

```
{
  "site": "acme-shop.example",
  "name": "Acme monthly",
  "url": "https://plausible.io/share/acme-shop.example?auth=k3T9xQ2mVb7Lw0pD",
  "password_protected": true,
  "segment": null
}
```

## Why use Cotlet for Plausible?

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

## Is it safe to connect Plausible to Cotlet?

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

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

## Is there a Plausible MCP server on GitHub?

Yes. Community Plausible MCP servers exist on GitHub, usually maintained by one person. The one Plausible's docs list works through the Stats API, so it needs a Business plan key and reads stats only. You install it and keep it running yourself. Cotlet hosts a server for you that also changes settings, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, create a Stats API key, add it to each MCP client | Sign up, sign in to Plausible once, add one MCP server or API key |
| What it does | Reads stats through the Stats API; no sites, goals, shared links or guests | Reads the dashboard and also adds sites, goals, shared links, guests, email reports and notes |
| When Plausible changes | It breaks until you or the maintainer fix it | Our team tests it daily and fixes it for you; failed calls are free |
| Your Plausible session | An API key in a file on your computer, readable by any program you run | 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 you revoke it; a lost or leaked key needs a new one | Your Cloud Browser keeps you signed in; if Plausible logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | 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 Plausible 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 Plausible API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Plausible 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 20 to 30 credits (25 for most tools, about $0.10 to $0.15), 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 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $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 Plausible 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 Plausible 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 Plausible only after you enable it. When Plausible 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 Plausible, sign out of Plausible 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.
- **Plausible's terms:** You use your own Plausible account and stay responsible for following Plausible's terms. Cotlet is independent and not affiliated with Plausible. [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 Plausible in the console and press Request access. Then you create your API key and connect Plausible there.

**Do I need to be technical?**

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

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

Plausible 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).

**Which Plausible plan do I need?**

Cotlet works in your own Plausible account, not through the API, so it does not need the Business plan for the Stats API or the Enterprise plan for the Sites API. What the app offers still follows your plan: Plausible lists funnels, revenue tracking and custom properties under Business, and multiple sites, shared links and team members under Growth. Your role counts too: inviting guests needs an Owner or Admin.

**Can the agent delete a site, goal or shared link?**

No. No tool deletes anything. Deleting a site in Plausible removes all its data, and per the Sites API docs the data removal can take up to 48 hours before the domain can be registered again. Do that in Plausible yourself.

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

No. Every call to create_shared_link, invite_guest, set_email_reports or add_annotation waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals. create_site, add_goal runs without asking, because it sends nothing to anyone and one call undoes it.

**Can I use the Plausible 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/plausible 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 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.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.