Supersaas Analytics

com.supersaasanalyticsPublished by supersaasanalytics.comOfficial publisherv1.0.0Updated Nov 22, 2026

Read-only, cookieless web analytics: traffic, sources, pages, Goals, Funnels and revenue per site.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

Supersaas Analytics's hosted MCP server (supersaasanalytics.com), published by supersaasanalytics.com; API key required; Streamable HTTP.

No AI overview yet: these facts come from the registry entry and the server itself.

Publisher
supersaasanalytics.com
Endpoint
supersaasanalytics.com
Last checked

Installation

In SourceWeft

  1. Open Supersaas Analytics in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.supersaasanalytics%2Fanalytics/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "supersaas-analytics": {
      "type": "http",
      "url": "https://supersaasanalytics.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Supersaas Analytics

Cookieless web analytics for Organizations and any number of their own websites. Built with Nuxt 4, Nuxt UI, NuxtHub and Better Auth, and deployed to Cloudflare Workers with D1.

It replaces analytics-main (TanStack Start), with the same behaviour as seen by a Site's Visitors and by the owner.

What it does

  • Tracking snippet at /sd.js, minified at build time from tracking-snippet/sd.js and kept under 1,024 B gzipped. A Site embeds <script defer data-site="<site id>" src="https://<host>/sd.js"></script>. It reports Pageviews, SPA route changes and Outbound link clicks, sends Events through sd(name, props) and an identity through sd.identify(id), and captures tel:, mailto: and WhatsApp link clicks, form submits and clicks on [data-sd-event] elements as Events with the page path, and sd.visitorId() returns the Visitor id from the last /collect response. It sets no cookies and uses no storage.
  • Ingestion at POST /collect. It always answers 204 at once and writes in the background:
    • A Visitor is sha256(salt:site_id:ip:ua), where the salt is random per UTC day and deleted once the day ends, so the same person is a new Visitor each day.
    • sd.identify(id) stores hmac(site secret, id) on the Visitor, never the id itself. Visitors identified with the same id share that hash, which links their days.
    • A Visit is a 30-minute window measured from its start.
    • Hits from bot User-Agents, from a Site's ignored IPs or CIDRs (Settings → Filtering), and Pageviews or Events on its excluded path globs are dropped before anything is stored.
    • Geo comes from Cloudflare, or from forwarded x-vercel-ip-* headers when a Site proxies /collect through its own domain, which also passes the visitor's IP first in X-Forwarded-For.
  • All sites at /app/<organization>, behind sign-in: Visitors, Pageviews (last 24 hours, with their absolute change against the 24 hours before) and Live visitors across every Site, then one band per Site with its online count, the same figures and an hourly sparkline, all from one request.
  • Live at /app/<organization>/live (every Site, each Visitor with a Site badge) and /app/<organization>/sites/<site>/live: "N live", Pageviews per minute over the last 30 minutes with the peak, referrer, country and device chips, and the current Visitors (page, city, browser, device, Source) beside the globe. Hovering a Visitor highlights its point and turns the globe to it. Polled every 15 seconds.
  • Dashboard at /app/<organization>/sites/<site>:
    • a Range picker (today, yesterday, last 24 hours, 7, 30 and 90 days, 6 and 12 months, custom) and a Live visitor badge
    • a KPI strip (Visitors, Pageviews, Bounce rate, Visit duration, and Conversion rate once the Site has a Goal), each with its change against the previous period, that toggles the chart's series
    • ranked Pages (with Outbound links), Sources, Devices and Locations (with a live globe). Sources group into Channels (Direct, Search, Social, AI assistant, Email, Paid, Referral) from the referrer and UTM, with tabs for referrers, AI assistants and the UTM campaign, medium, term and content
    • a Realtime card (Visitors online, the last 30 minutes of Pageviews and the current Visitors) with "View realtime →"
    • Events, one row per Event and the page it fired on. Clicking one opens a panel that breaks it down by property key and value, for that page or all pages, read from raw rows.
    • Goals (Site Settings → Attribution): Quick add chips for the auto-captured WhatsApp, Phone, Email, Form submit and Outbound clicks, or a custom Goal on an Event name or a page pattern (/blog/*). The Goals card lists each Goal's unique Visitors, total conversions and conversion rate, read from raw rows; clicking one narrows the dashboard to the Visits that converted (?f=goal:event:signup).
    • Funnels per Site: 2 to 8 Pageview-pattern or Event steps completed in order within 1 hour, 24 hours, 7 or 30 days (other pages in between are fine; Identified visitors count across days). Each card shows Entered, Completed and Conversion rate, each step's count and share of entries, and "↓ X% continue · N dropped" between steps. A builder slide-over previews the draft over the current Range; the dashboard shows a Funnel with "All funnels →".
    • a Journeys explorer per Site: columns "Starting point → 1 step after → 2 steps after …" of the pages Visitors open, with each node's Visitors and share, starting points grouped by their first path segment, a "No further action" row for the Visitors who left, and "Events on " for the selected node. It reads raw rows, follows the Range and Filters, and each Funnel card links to it with "Explore journeys →".
    • a Pages tab per Site: Pages, Pageviews, Visits, Avg. bounce and Avg. duration, then a searchable table sorted by any column with each page's title and path (or full URL), a trend sparkline, views, Visits with their change, bounce rate and time on page. It follows the Range and Filters.
    • a Users tab per Site: Visitors, Pageviews, Views per Visitor and Avg. time, then the Visitors of the Range ("Visitor 083047", country, Source, device, Visits, Pageviews, time, entry → exit), searchable by visitor id, country or page. Clicking one opens its journey: totals, the first Source, Visit chips and a timeline of Pageviews (time on page, entry marked), Outbound links and Events with their properties. An Identified visitor's journey covers every day with the same identify hash.
    • Filters: clicking a ranked row narrows the whole dashboard to the Visits that match it. Filters stack, live in the URL (?f=country:PK&f=browser:Safari) and show as removable chips. Filtered views read raw rows.
  • Daily Rollup at 00:10 UTC for each Site's previous local day. Key figures read past days only from Rollups, and today and "Last 24 hours" from raw rows. Single-day and 24-hour charts are hourly, from raw rows.
  • Accounts and Organizations with Better Auth: email and password (verified), magic links, Google and GitHub. Members have one role, Owner, Admin or Viewer, and each Organization has exactly one Owner. Email goes through Resend and is printed to the console in dev.

Quick start

sh
pnpm installpnpm dev            # http://localhost:3001pnpm db:seed        # fill a Site with demo traffic
CommandWhat it does
pnpm devdev server on port 3001, SQLite in .data/db
pnpm testVitest: unit and server projects
pnpm lint / pnpm typecheckESLint (demo-next style) / vue-tsc
pnpm db:generategenerate a migration from server/db/schema
pnpm db:seed [siteId] [days]replace a Site's analytics with demo data (dev only)
pnpm rollup [YYYY-MM-DD]run the daily Rollup on the dev server
pnpm run deploybuild for Cloudflare, migrate the remote D1, deploy

Environment variables are listed in .env.example. None are needed locally.

Guides

The full documentation is at supersaasanalytics.com/docs.

Contributing

Pull requests are welcome. Run pnpm lint, pnpm typecheck and pnpm test first. This repository is published from our main repository, so a merged change arrives in the next release rather than as a merge here; you are credited as its author.

Licence

Supersaas Analytics is fair source, under the Functional Source License, Version 1.1, ALv2 Future License (FSL-1.1-ALv2, see fsl.software).

  • You may self-host it for free and modify it for your own sites.
  • You may not sell it or offer it as a competing service.
  • Each release becomes Apache 2.0 two years after it is published.

Source: README.md at commit 7882a5c

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 22, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.