OpenAnalytics MCP server
Commit Oct 22, 2026Provides privacy-first web analytics with revenue attribution and an MCP server for AI-driven data exploration.
Also known as OpenLabs-so/openanalytics
- Stars
- 652
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 22, 2026
- License
- AGPL-3.0
What is OpenAnalytics MCP?
OpenAnalytics provides privacy-first web analytics with revenue attribution and an MCP server for AI-driven data exploration.
Summary generated from the project's README
About OpenAnalytics MCP server
Analyzing website traffic and revenue through a privacy-first lens is what OpenAnalytics enables for developers and site owners. This system provides page views, custom events, sessions, and web vitals without using cookies or cross-site profiles. It is designed to be self-hosted on your own hardware using Docker, though a hosted version is also available. Users can connect their Stripe accounts to gain insights into revenue attribution alongside standard visitor metrics.
To use the AI-driven data exploration features, you can connect an MCP server to your client. This setup requires an OpenAI API key to enable the AI assistant functionality. The architecture is built to be lightweight, using a small tracker script that adheres to a strict byte budget. For those who prefer managed infrastructure, the system can integrate with Neon for Postgres storage, allowing for easier backups and point-in-time restores while maintaining full control over your event data stored in ClickHouse.
What you can do with it
- 1Track revenue attributionConnect your Stripe account to see how web traffic correlates with actual earnings.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachableopenlabs-so/openanalytics is public and reachablegithub.com/openlabs-so/openanalytics ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-22github.com/openlabs-so/openanalytics ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubOpenAnalytics
Privacy-first web analytics. One lightweight tracker script, no cookies, no cross-site profiles, aggregate-only reads — self-hostable on your own hardware under AGPL-3.0.
A hosted instance runs at getopen.so, operated by the authors: the same code, someone else's servers.
Sponsored by the Neon Open Source Program. Neon is the managed Postgres behind getopen.so and the one we recommend for self-hosting — see Deploying with Neon.

▶ Watch the dashboard in motion, a tour of these same screens on YouTube.
What is in this repository
The product, as one pnpm monorepo:
| App | Role |
|---|---|
apps/tracker |
The browser snippet — a few KiB, with a byte budget CI enforces |
apps/collector |
Ingest: validates, sanitizes, rate-limits, enqueues |
apps/worker |
Drains the queue into ClickHouse; sessions, rollups, exports, mail, deletions |
apps/api |
Control plane: auth, sites, keys, sharing, event definitions, funnels, widgets, revenue, AI assistant, MCP |
apps/query-gateway |
The only process allowed to read ClickHouse; verifies signed query envelopes |
apps/realtime |
The SSE stream behind the live dashboard |
apps/web |
The dashboard (Next.js) |
apps/cli |
oa — site setup, stats, device-flow login |
packages/* |
domain, postgres (+migrations), clickhouse (+migrations), redis, auth, contracts (OpenAPI), observability, integrations, migrations, testkit |
Stores: Postgres (control plane), ClickHouse (events and rollups), Valkey ×2 (one durable event queue, one losable realtime cache).
What it does, in one list: page views, custom and attribute-driven events, sessions, web vitals, funnels, per-site retention, embeddable widgets, public share links, revenue analytics from your Stripe account, CSV/JSON import and export, an MCP server, and a CLI.
Who is on the site now, from a presence cache rather than a table scan. Names are generated per visitor and mean nothing outside the day they were minted.

Where one visitor went, session by session. The identity behind a trail is a salted hash that rotates every night, so the trail is as long as a visit and never as long as a person.

Where they are, at city level and only when a site opts in. The lookup runs against a database on your own disk and never leaves the host.

Architecture rules CI enforces, not conventions:
apps/webmay import onlypackages/contracts— the OpenAPI document is the single seam between frontend and backend.- ClickHouse is reachable only through the query gateway, which verifies Ed25519-signed query envelopes minted by the api.
- The tracker has a hard byte budget; a change that exceeds it fails CI.
- The Postgres schema this repository builds contains no billing tables, and a CI job asserts that against a real database rather than a file list.
Self-hosting
SELF-HOSTING.md is the guide: a generator script, one
docker compose up -d, automatic TLS, and an explanation of every secret and
every failure mode. Requirements are a Linux host with Docker, four DNS records,
about 4 GB of RAM and 25 GB of free disk.
Installing is a pull, not a build. A release publishes ten images to
ghcr.io/openlabs-so/openanalytics, so a fresh host is a few minutes and needs
no toolchain on it.
Point four names at the host before you start. Certificates are issued on the first boot and issuance fails without them, half an hour later and nowhere near the cause:
app.example.com api.example.com c.example.com rt.example.com
git clone https://github.com/OpenLabs-so/openanalytics
cd openanalytics
git checkout "$(git tag -l 'v*' --sort=-v:refname | sed '/-/d' | head -1)" # newest release, not main
cd infra/selfhost
./generate-secrets.sh --domain example.com --email you@example.com --with-geoip
docker compose pull && docker compose up -d
# then open https://app.example.com and create the first account
The checkout is where the version is chosen, and it is chosen once. The
generator reads the tag back out of the tree it is standing in and points .env
at that release's images, printing which it picked and why; on a branch, on
main, or with no git at all it writes the build defaults instead. That is not
a convenience — the compose file, the env templates and the migrations ship
with the images, so a release's images against another tree is a configuration
nobody has tested.
Postgres can live on Neon instead of on the host. The stack bundles a
Postgres container, and Neon is the managed option we
recommend: four environment variables and one line in .env, and Postgres
backups and point-in-time restore become Neon's job.
infra/selfhost/NEON.md walks through it, including
moving an existing install across.
Images are amd64. On arm64, or to run a branch, build the ten here instead:
same compose file, one flag, about ten minutes and swap on a 4 GB box. Later,
./upgrade.sh moves between releases and takes the snapshot ./rollback.sh
needs, because migrations do not go down: the way back is a restore, and a
restore discards what arrived after the upgrade. It tells you that before it
starts, not at rollback time when you no longer have a choice.
RELEASING.md is what a version number here means.
To run it from source instead — for development, or to slot the services into
infrastructure you already have — follow
Running from source. The order matters
and one obvious order does not work: the migration runners are compiled
output, so pnpm run build comes before pnpm run migrate:postgres.
infra/selfhost/env/*.env.example documents every variable each service reads,
and there is one file per service on purpose — the environment schema forbids
some keys to some services, so a single shared .env cannot be correct. The
AI assistant (OPENAI_API_KEY) and object storage are optional: unset, those
surfaces disable themselves and everything else runs.
Run the test suite the way CI does:
pnpm run test # unit + contract + tracker, no infrastructure needed
pnpm run verify # everything CI checks, including boundaries and the size budget
Privacy model
No cookies, no fingerprinting, no cross-site identifiers. Visitor identity is a daily-rotating salted hash; raw IP addresses are never stored. Do Not Track and Global Privacy Control are honored at the collector, before anything is written. City-level geolocation is opt-in per site.
Geolocation is resolved locally against a database on your own disk — no lookup
ever leaves the host. None is bundled (a 60 MB download, and stale within a month);
infra/selfhost/geoip/fetch-dbip.sh downloads one.
IP Geolocation by DB-IP — https://db-ip.com — used under CC BY 4.0.
Contributing
Pull requests are merged here, with your name on the commit. This repository used to receive periodic exports from a private monorepo, and a merged PR was flattened by the next one; that ended in August 2026. A bot asks you to sign the CLA once — it is not an assignment, you keep your copyright — and there is no DCO sign-off on top of it.
CONTRIBUTING.md has the setup, the ground rules CI enforces, and where to start. Discussions are for questions and for ideas worth talking through first.
Security reports: SECURITY.md — please not a public issue.
License and trademark
Code: AGPL-3.0. If you run a modified OpenAnalytics as a network service, the AGPL requires you to offer your modified source to its users.
The browser tracker is the exception: apps/tracker/ and the oa.js it builds
are MIT, because it is the one file that runs on your
site, not on the server. Embedding it creates no obligation under the AGPL.
The "OpenAnalytics" name and the hosted service's domain identify the instance its authors operate and are not part of the license grant. A self-hosted instance runs the software, not the brand.
OpenAnalytics MCP questions
Is OpenAnalytics privacy-friendly?
Yes, it is a privacy-first, cookieless analytics solution that uses no cross-site profiles and rotates visitor identity hashes nightly.
Can I self-host OpenAnalytics?
Yes, it is self-hostable on your own hardware under the AGPL-3.0 license using Docker Compose.
What databases does it use?
The system uses Postgres for the control plane, ClickHouse for events and rollups, and Valkey for event queuing and realtime caching.
Does it support revenue tracking?
Yes, it provides revenue analytics integrated from your Stripe account.