PluginBench
MCP Server
Active
MIT

HitKeep MCP Server

io.github.PascaleBeier/hitkeep

AI-native, privacy-first web analytics with sovereign data and read-only MCP access to aggregate insights.

What is the HitKeep MCP server?

The HitKeep MCP server is a read-only interface to HitKeep's web analytics platform, providing AI agents access to aggregate traffic, conversion, and Search Console data. It enables approved assistants to query analytics insights while maintaining data governance and privacy through a stateless, remote HTTP connection.

HitKeep is an open-source, privacy-first web analytics platform that treats AI as a first-class traffic channel. The MCP server exposes read-only access to aggregate analytics data—traffic metrics, conversions, Search Console integration, and AI visibility reports—allowing Claude and other AI agents to answer questions about website performance using cited, governed evidence without direct dashboard access.

How to install HitKeep

Copy-paste configuration for popular MCP clients.

transport: http
Config generated by PluginBench — verify against the source before use.
Environment / auth
  • Authorization
    required
    secret

    Bearer token from a scoped HitKeep personal or team API client.

~/.cursor/mcp.json
{
  "mcpServers": {
    "hitkeep": {
      "url": "https://{hitkeep_host}/mcp"
    }
  }
}

Tools & capabilities

Tools this server exposes to the agent.

  • Analytics Query — Read-only access to aggregate traffic, conversion, and performance metrics
  • Search Console Integration — Query Search Console data including clicks, impressions, click-through rate, and position trends
  • AI Visibility Reporting — Access AI-specific analytics distinguishing crawler fetches, AI referrals, and related activity
  • Ecommerce Analytics — Query revenue KPIs, trends, top products, and revenue sources
  • Custom Events — Access data from custom tracking events such as signups, purchases, and qualified leads

Use cases

  • Ask an AI assistant about your website's traffic trends and top referral sources using cited analytics data
  • Query ecommerce revenue metrics and product performance without exposing raw visitor data
  • Investigate AI crawler activity and AI-referred traffic separately from human visitors
  • Generate reports on Search Console performance including impressions, clicks, and keyword rankings
  • Access conversion funnel and goal completion data to understand user journey outcomes

HitKeep MCP server FAQ

What is the HitKeep MCP server?

It's a read-only MCP interface that gives AI agents like Claude access to aggregate analytics data from a HitKeep instance—traffic, conversions, Search Console, and AI visibility metrics—while maintaining data governance and privacy.

Is HitKeep free?

Yes, HitKeep is 100% open source under the MIT license. You can self-host the complete product including custom tracking domains and team SSO, or use HitKeep Cloud for managed hosting in EU or US regions.

How do I connect the HitKeep MCP server to Claude or Cursor?

Configure the remote HTTP endpoint in your MCP settings: `https://{hitkeep_host}/mcp`. The server runs as part of your HitKeep instance and requires no separate installation.

Does the MCP server require authentication?

The MCP server is read-only and stateless. Access control is managed through your HitKeep instance's permissions and SSO configuration; approved assistants receive governed access to aggregate data only.

What data can the MCP server access?

The server provides read-only access to aggregate analytics: pageviews, traffic sources, conversions, goals, funnels, ecommerce revenue, Search Console metrics, Web Vitals, and AI visibility reports. It does not expose individual visitor profiles or session data.

Does HitKeep respect privacy?

Yes. The browser tracker sets no analytics cookies, respects Do Not Track, and collects focused website analytics without building cross-site visitor profiles. All data remains under your control with full sovereignty and export options.

README (reference)

Source of truth, from the repository.

<p align="center"> <picture> <source media="(prefers-color-scheme: dark)" srcset="./frontend/dashboard/public/hitkeep-wordmark-white.png"> <source media="(prefers-color-scheme: light)" srcset="./frontend/dashboard/public/hitkeep-wordmark-blue.png"> <img src="./frontend/dashboard/public/hitkeep-wordmark-blue.png" alt="HitKeep" width="352"> </picture> </p> <h1 align="center">AI native, sovereign, privacy-first web analytics in one binary.</h1> <p align="center"> 100% open source under MIT, HitKeep unifies traffic, conversions, Search Console, and AI visibility with custom tracking domains, SSO, open exports, and no separate database, queue, or cache. </p> <p align="center"> <a href="https://hitkeep.com/guides/installation/">Self-host</a> · <a href="https://hitkeep.com/guides/introduction/">Documentation</a> · <a href="https://hitkeep.com/cloud">Cloud</a> · <a href="https://hitkeep.com">Website</a> </p> <p align="center"> <a href="https://github.com/PascaleBeier/hitkeep/releases"><img alt="Latest release" src="https://img.shields.io/github/v/release/PascaleBeier/hitkeep?sort=semver"></a> <a href="https://github.com/PascaleBeier/hitkeep/actions/workflows/ci.yml"><img alt="Continuous integration status" src="https://github.com/PascaleBeier/hitkeep/actions/workflows/ci.yml/badge.svg?branch=main"></a> <a href="./LICENSE"><img alt="MIT license" src="https://img.shields.io/github/license/PascaleBeier/hitkeep"></a> <a href="https://hub.docker.com/r/pascalebeier/hitkeep"><img alt="Docker pulls" src="https://img.shields.io/docker/pulls/pascalebeier/hitkeep?logo=docker&label=docker%20pulls"></a> <a href="https://www.bestpractices.dev/projects/11990"><img alt="OpenSSF Best Practices badge" src="https://www.bestpractices.dev/projects/11990/badge"></a> </p>

HitKeep dashboard showing setup progress, traffic metrics, conversion reports, and analytics navigation

Why HitKeep

  • 100% open source. The complete product is MIT-licensed. Custom tracking domains and team SSO live in the same public codebase—not in a separate proprietary edition.
  • Full data sovereignty. Self-host one Go binary with embedded DuckDB and NSQ, or export your data in open formats. Complete takeout, APIs, webhooks, share links, and permissions keep the data useful outside HitKeep.
  • AI-native analytics. HitKeep treats AI as a first-class traffic channel: crawler fetches, AI-referred visits, and chatbot outcomes remain distinct. Ask AI uses cited aggregate evidence, while read-only MCP gives approved assistants governed analytics access.
  • Privacy by default. The browser tracker sets no analytics cookies, respects Do Not Track, and collects focused website analytics without building a cross-site identity.
  • Reporting that reaches the outcome. Follow acquisition through pages, automatic and custom events, goals, funnels, ecommerce revenue, UTM and QR campaigns, Search Console, and Web Vitals.

Self-host the complete open-source product, or use HitKeep Cloud in a managed EU or US region when you do not want to operate it yourself.

HitKeep is web-focused. It favors aggregate traffic and conversion evidence over visitor profiles, session replay, mobile SDKs, or built-in experimentation. The result is a smaller collection boundary and operating surface without stopping at a basic pageview counter.

Quick Start

Download the Docker Compose file and environment template:

mkdir hitkeep && cd hitkeep
curl -fsSLo compose.yml https://raw.githubusercontent.com/PascaleBeier/hitkeep/main/examples/compose.yml
curl -fsSLo .env https://raw.githubusercontent.com/PascaleBeier/hitkeep/main/examples/.env.example

Open .env and replace paste-the-generated-value-here with a long random value from your password manager. Then start HitKeep:

docker compose up -d

Open http://localhost:8080 and create the first account. Keep .env private and retain the same secret across restarts.

Before exposing an instance publicly, follow the Docker Compose guide for HTTPS and trusted proxies, then review backups and the configuration reference. Prefer a native service? Download the Linux AMD64 or ARM64 binary from GitHub Releases and follow the binary installation guide.

Track Your First Site

Create a site in the dashboard, then add the tracker to your pages:

<script async src="https://analytics.example.com/hk.js"></script>

Pageviews and supported automatic interaction events—outbound clicks, file downloads, and form submissions—start flowing immediately. Use the custom events guide for product-specific actions such as signups, purchases, or qualified leads.

Explore HitKeep

<details> <summary>See AI visibility, ecommerce, Search Console, and Ask AI</summary>

AI visibility

HitKeep AI visibility report separating crawler fetches, AI referrals, and related activity

Ecommerce

HitKeep ecommerce analytics showing revenue KPIs, trends, top products, and revenue sources

Search Console

HitKeep Search Console report showing clicks, impressions, click-through rate, position, and query trends

Ask AI

HitKeep Ask AI answer with completed analytics tools, cited evidence, a table, and a safe dashboard action

</details>

Documentation, Community, and Support

Find answers in the documentation, report reproducible bugs through GitHub Issues, and disclose vulnerabilities privately through the security policy.

<details> <summary>Contributor quick path</summary>

Run ./hk setup, then start seeded development with ./hk dev --seed or use ./hk dev --detach. Capture product proof with ./hk screenshot; inspect ./hk catalog commands --output json and ./hk catalog configuration --output json instead of copying mutable workflow facts. Validate with ./hk qa pr. The Compose stack and complete workflow live in CONTRIBUTING.md.

</details>

License

HitKeep is distributed under the MIT License.

Related MCP servers

TITickerRisk logo

TickerRisk

Maintained

Check options trades for hidden catalysts (earnings, FDA, legal, SEC) before you sell premium.

0
Python
MIT
View repository →
PIPiia Engram logo

Local-first AI work identity layer—portable context across Claude Code, Cursor, Codex, and other MCP tools.

167
Python
AGPL-3.0
View repository →

Keyless 12-tool patentability MCP: USPTO pillar scores, prior art, hosted at patentprecheck.com/mcp.

Cited product-review verdicts from real user voices — free remote MCP, no API key.

0
View repository →

Human-authenticated setup for routing GitHub pull requests into the right Slack channel.

0
JavaScript
MIT
View repository →

40 MCP tools: multi-chain RPC, market and transaction decisions, AI, EU compliance and US imports

0
MIT
View repository →