cogny clianalyticsfirst 15 calls free

    plausible queried from the terminal.

    Run Plausible Stats API v2 queries, pull aggregate metrics, time series, and breakdowns by page, source, country, or device, and count live visitors — all from Bash over the Plausible MCP. The Stats API without the curl boilerplate.

    • 1. sign up, free for the first calls (uses your git email)npx @cogny/cli init --agent claude-code
    • 2. see every Plausible toolcogny tools list
    • 3. call any tool from bash, no MCP wiringcogny tools call mcp__Plausible__breakdown --input '{…}'
    01two paths
    you're a person

    The Plausible dashboard is fast for a glance but slow for ad-hoc questions — you click filter pills and screenshot the chart. The CLI gives you the exact metric × dimension breakdown as JSON you can pipe, schedule, or hand to an agent. Connect Plausible once in Cogny Solo and let your coding agent, or a scheduled loop, do the querying for you.

    Start Solo
    you're an agent

    Sign yourself up with one command. The CLI issues a key, wires nothing, and exposes every Plausible tool over JSON-RPC. The first 15 calls are free.

    • npx @cogny/cli init --agent claude-code
    02tools call

    real Plausible tools.

    Tool names as the Plausible MCP serves them. Send --input JSON, get JSON back. The payloads are illustrative.

    • mcp__Plausible__breakdown

      Break a metric down by a property (top pages, sources, etc.).

      • cogny tools call mcp__Plausible__breakdown \ --input '{"site_id":"example.com","dimension":"visit:source","metrics":["visitors","bounce_rate"],"date_range":"7d","limit":3}'
      example response
      {
        "results": [
          {
            "dimensions": [
              "Google"
            ],
            "metrics": [
              4120,
              0.41
            ]
          },
          {
            "dimensions": [
              "Direct"
            ],
            "metrics": [
              1880,
              0.52
            ]
          },
          {
            "dimensions": [
              "Twitter"
            ],
            "metrics": [
              640,
              0.63
            ]
          }
        ]
      }
    • mcp__Plausible__aggregate

      Headline metrics for a site over a period.

      • cogny tools call mcp__Plausible__aggregate \ --input '{"site_id":"example.com","metrics":["visitors","pageviews","bounce_rate"],"date_range":"30d"}'
      example response
      {
        "results": [
          {
            "metrics": [
              38214,
              91022,
              0.47
            ]
          }
        ]
      }
    • mcp__Plausible__realtime_visitors

      Count of visitors active in the last 5 minutes.

      • cogny tools call mcp__Plausible__realtime_visitors \ --input '{"site_id":"example.com"}'
      example response
      23
    03tools list

    the rest of the surface.

    A sample of the other Plausible tools. Run cogny tools list --json for every tool and its input schema.

    • mcp__Plausible__query
    • mcp__Plausible__timeseries
    04then a verdict

    calls from a script. verdicts from cogny.

    Every write is logged with who authorised it. Launches your agent makes (a new campaign, a new ad) become measured tickets automatically; for other changes, your agent offers to register them. Cogny measures each in your own data, three days later for ads and seven for content and SEO, and closes it as worked, partial, didn't work or inconclusive.

    • worked

      Moved the number. Every measured win has a share card.

    • partial

      Some of it did.

    • didn't work

      On the record anyway, so it isn't proposed again.

    • inconclusive

      Not enough data to call.

    How the loop works

    05questions

    questions.

    Is this an official Plausible CLI?
    No — it is the Cogny CLI calling the Plausible MCP over the cogny-mcp-proxy. You connect your Plausible API key once in Cogny and then call every tool from Bash. Self-hosted and EU instances are supported via the connection’s server URL.
    Which metrics and dimensions can I use?
    The full Stats API v2 set: metrics like visitors, visits, pageviews, bounce_rate, visit_duration, and conversion_rate; dimensions like event:page, visit:source, visit:country, visit:device, and time:day. Pass them straight through query.
    Can I schedule these from cron?
    Yes. The CLI is a normal binary — wire cogny tools call breakdown --input ... into cron, a Makefile, or your agent and capture stdout. On Cogny Solo, standard MCP calls are unmetered under fair use.
    06related

    Building an agent? The full tool map for every server is one fetch: /cli/llms.txt

    plausible, then a verdict.