Menu
Mattering Automations connector

A Plausible Analytics MCP that answers traffic questions in one call

Connect one API key and Plausible's stats become workflow steps for visual automations and AI agents. One query node covers aggregates, timeseries, and breakdowns across every metric on your dashboard, a realtime node reads the live visitor count, and Enterprise Sites API keys unlock site, goal, and shared link provisioning.

8 ready-made nodes One credential to connect Works with Claude, ChatGPT, and Matter

What the Plausible Analytics MCP connector does

The Plausible Analytics connector for Mattering Automations is 8 nodes over Plausible's privacy-first, cookieless analytics: the unified v2 stats query, the realtime visitor count, and the sites surface for listing and fetching sites, listing goals, and creating sites, goals, and shared dashboard links. Five nodes read, three create, and nothing in the connector deletes anything.

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer how traffic moved this week, which pages grew, and where visitors came from with a single call to Plausible: Query Stats, because Plausible's v2 query endpoint takes metrics, a date range, dimensions, and filters in one request.

Because Mattering is a work platform rather than middleware, analytics work lands somewhere useful by default: a weekly traffic digest can arrive as a report task in Mattering Productivity, a scheduled spike check can open an investigation task when the numbers move, and query results can accumulate in a Mattering database for the comparisons a dashboard screenshot cannot make.

Plausible issues API keys in two grades, chosen when the key is created. A Stats API key, a Business plan feature, unlocks the two stats nodes. The six sites-surface nodes, from listing sites to creating goals and shared links, need a Sites API key, an Enterprise plan feature, and each of those nodes says so in its description, which turns a 401 under a Stats key into a self-explaining answer rather than a mystery.

One connection, three surfaces

  • Visual automations. Drag Plausible Analytics nodes onto the canvas and wire them to triggers, conditions, and other apps.
  • AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
  • The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.

Every Plausible Analytics node, ready to drop on the canvas

8 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.

Read and query nodes 5

Plausible: Get Realtime Visitors

Get the number of visitors currently on your site (anyone who triggered a pageview in the last 5 minutes). Needs a Stats API key. The response body is a bare number, so the count lands directly at data (e.g. data equals 21), not under a wrapper key. This is the one legacy v1 stats endpoint still shipped: the v2 query API has no realtime range, so this remains the documented way to read the live count. Free to call and read-only, which makes it the connector's credential health check.

Plausible: Get Site

Fetch one site's details by domain: timezone, allowed custom properties, and the tracker script configuration (which optional tracking features are on). Requires a SITES API key (an Enterprise plan feature on plausible.io, created as its own key type under Settings, API Keys); a Stats API key gets a 401 here.

Plausible: List Goals

List a site's configured goals (custom events and page visits) at data.goals, each with its id, goal_type, event_name or page_path, and display_name. Goal ids and names feed the event:goal dimension of the Query Stats node. Requires a SITES API key (an Enterprise plan feature on plausible.io, created as its own key type under Settings, API Keys); a Stats API key gets a 401 here.

Plausible: List Sites

List the sites your API key can access, with each site's domain and timezone at data.sites. Cursor-paginated. Requires a SITES API key (an Enterprise plan feature on plausible.io, created as its own key type under Settings, API Keys); a Stats API key gets a 401 here.

Plausible: Query Stats

Query any historical stat from your Plausible dashboard through the unified v2 query endpoint: pick metrics, a date range, and optional dimensions and filters, and get rows at data.results (one metrics array plus one dimensions array per row). This single node replaces the legacy v1 aggregate, timeseries, and breakdown endpoints: aggregate is a query with no dimensions, a timeseries is a time dimension, and a breakdown is any other dimension. Needs a Stats API key (Business plan feature; default rate limit 600 requests per hour).

Action nodes 3

Plausible: Create Goal

Create a goal on a site, or find the existing one: the endpoint is an idempotent create-or-find PUT, so re-running it never duplicates a goal. Two kinds: goal_type event (matches a custom event by name) or goal_type page (matches visits to a page path, wildcards supported). Requires a SITES API key (an Enterprise plan feature on plausible.io, created as its own key type under Settings, API Keys); a Stats API key gets a 401 here.

Plausible: Create Shared Link

Create a shared dashboard link for a site, or find the existing one by name (idempotent create-or-find PUT). Returns the secret URL at data.url, ready to send to a client or embed in a report - anyone with the link can view the dashboard without logging in. Requires a SITES API key (an Enterprise plan feature on plausible.io, created as its own key type under Settings, API Keys); a Stats API key gets a 401 here.

Plausible: Create Site

Add a new site to Plausible programmatically, e.g. when provisioning analytics for each new customer site. Returns the created site with its tracker script configuration. Reversible: the site can be deleted from the Plausible dashboard (this connector ships no delete node on purpose). Requires a SITES API key (an Enterprise plan feature on plausible.io, created as its own key type under Settings, API Keys); a Stats API key gets a 401 here.

Connecting Plausible Analytics takes one credential

Plausible issues API keys from Settings, API Keys in your plausible.io account, and the key's grade is chosen at creation: a Stats API key (a Business plan feature) for reading analytics, or a Sites API key (an Enterprise plan feature) for provisioning sites, goals, and shared links. Either grade is sent as a bearer credential on every request, and the key is shown once, at creation.

1

In Plausible, open Settings, go to API Keys, and create a New API Key, choosing the grade your automations need: Stats for reading analytics, Sites for provisioning. Copy the key when it appears; Plausible shows it once.

2

In Mattering Automations, open Connectors, click Add Connector, choose Plausible Analytics, and create a credential with that key.

3

Click Test Connection with the domain of a site your key can access. Plausible has no authenticated read that takes zero parameters on a Stats API key, so the test reads that site's realtime visitor count, a free, read-only call that proves the key works.

4

All 8 Plausible Analytics nodes appear in the canvas palette. On a Stats key, the two stats nodes work and the six sites nodes return Plausible's 401, exactly as their descriptions say they will.

Common uses for the Plausible Analytics MCP

Any traffic question in one call

Plausible: Query Stats is the whole historical dashboard behind one node: pick metrics such as visitors, pageviews, bounce rate, or visit duration, a date range, and optional dimensions and filters. An aggregate is a query with no dimensions, a timeseries is a time dimension, and a breakdown by page, source, or country is any other dimension, so an assistant answers traffic questions without stitching endpoints together.

A weekly traffic digest where the team works

A scheduled run of Plausible: Query Stats pulls the week's visitors, top pages, and top sources, and the summary lands as a report task in Mattering Productivity instead of an email nobody opens. Add a second query for the previous week and the digest carries the comparison.

Spike and slump checks that open work

Run Plausible: Query Stats on a schedule, compare the result against the trailing numbers kept in a Mattering database, and open an investigation task when traffic jumps or drops past a threshold. Plausible: Get Realtime Visitors adds the live count, returned as a bare number, when a workflow needs to know what is happening right now.

Goal and conversion reporting

Plausible: List Goals returns a site's configured goals with their ids and names, and those feed the event:goal dimension of Plausible: Query Stats, so conversion counts and conversion rates per goal come back as ordinary query rows a workflow can route anywhere. Listing goals sits on the Enterprise sites surface; the goal-dimension queries themselves run on a Stats key.

Provisioning analytics for every new client site

On an Enterprise Sites API key, Plausible: Create Site adds a site the moment a customer onboards, Plausible: Create Goal configures its conversion goals, and Plausible: Create Shared Link returns a secret dashboard URL ready to send to the client. The goal and shared link creates are idempotent create-or-find operations, so re-running the workflow never duplicates them.

Example: A weekly traffic digest that lands as a report task

Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.

1

Trigger: a schedule fires every Monday morning.

2

Plausible: Query Stats aggregates the week: visitors, pageviews, bounce rate, and visit duration over the last 7 days, in one call with no dimensions.

3

Plausible: Query Stats runs again with a page dimension for the top pages, and once more with a source dimension for where the traffic came from.

4

A Mattering database keeps each week's numbers, so the workflow compares this week against last and phrases the change.

5

The digest lands as a report task in Mattering Productivity, assigned to whoever owns the site, with the numbers and the comparison in the body.

6

If visitors moved past a threshold week over week, the workflow opens a separate investigation task so the change gets looked at, not just reported.

Plausible Analytics MCP questions, answered

What Plausible Analytics operations are supported?

8 nodes. The stats surface is Plausible: Query Stats, the unified v2 query for every historical metric, plus Plausible: Get Realtime Visitors for the live count. The sites surface is Plausible: List Sites, Plausible: Get Site, Plausible: List Goals, Plausible: Create Site, Plausible: Create Goal, and Plausible: Create Shared Link. Deliberately not shipped: the legacy v1 aggregate, timeseries, and breakdown endpoints (the v2 query covers all three), site and goal deletion (destructive), guest and team administration, and the events ingestion endpoint.

Does this work with Claude, ChatGPT, or other AI assistants?

Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.

Why do some nodes return a 401 when my key works elsewhere?

Plausible issues two distinct key grades, chosen at creation. A Stats API key, a Business plan feature, serves Plausible: Query Stats and Plausible: Get Realtime Visitors. The six sites-surface nodes require a Sites API key, an Enterprise plan feature, and each says so in its own description, so a 401 from a sites node under a Stats key is the grade boundary, not a broken credential. Plausible documents the two as separate key types rather than tiers of one key, and the connector makes no claim that either grade serves the other surface.

Why is there one query node instead of aggregate, timeseries, and breakdown nodes?

Because Plausible folded all three into its v2 query endpoint and marks the v1 stats API a legacy feature. In the v2 grammar, an aggregate is a query with no dimensions, a timeseries is a query with a time dimension, and a breakdown is a query with any other dimension, with metrics, date ranges, filters, ordering, and pagination shared across all of them. One rich node instead of three redundant ones, and results come back as rows of metrics and dimensions at data.results.

Can the connector send pageviews or events into Plausible?

No, deliberately. Plausible's event ingestion endpoint identifies visitors by client IP address and user agent, so events posted from an automation runner would all carry one server's IP and one user agent, attributing the site's traffic to a single phantom visitor and poisoning the very data the stats nodes read. The script tag on your site is the right way in; this connector reads analytics and provisions sites, it does not write traffic.

Can a traffic change trigger a workflow?

There is no inbound Plausible trigger in this connector. The pattern is a scheduled sweep: run Plausible: Query Stats or Plausible: Get Realtime Visitors on a schedule, compare the result against a threshold or the previous period, and branch on what changed. A five-minute realtime sweep is cheap, since the endpoint is free to call and read-only.

What are the rate limits?

Plausible API keys are limited to 600 requests per hour by default. That is generous for the scheduled-sweep patterns this connector encourages: a weekly digest uses a handful of calls, and even a five-minute realtime check spends 12 an hour. API calls themselves carry no per-call charge within the limit, and the connector adds no limits of its own.

Can this connector delete or overwrite my analytics?

No. Five of the eight nodes are read-only, and the three writes are all creates: Plausible: Create Goal and Plausible: Create Shared Link are idempotent create-or-find operations that never duplicate on re-run, and Plausible: Create Site adds a site that can be removed from the Plausible dashboard. The connector ships no delete nodes on purpose, so site and goal deletion stay a deliberate human act in the dashboard.

8 nodes waiting on the canvas

Put Plausible Analytics to work inside your workspace

Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.

All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Plausible Analytics is a product of its respective owner; Mattering is an independent platform.

Start Free Explore our Products