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.
AuthorizationrequiredsecretBearer token from a scoped HitKeep personal or team API client.
Tools & capabilities
Tools this server exposes to the agent.
Analytics Query— Read-only access to aggregate traffic, conversion, and performance metricsSearch Console Integration— Query Search Console data including clicks, impressions, click-through rate, and position trendsAI Visibility Reporting— Access AI-specific analytics distinguishing crawler fetches, AI referrals, and related activityEcommerce Analytics— Query revenue KPIs, trends, top products, and revenue sourcesCustom 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
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.
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.
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.
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.
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.
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.

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

Ecommerce

Search Console

Ask AI

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.
- Operate: Installation · Configuration · REST API · Goals · Funnels
- Evaluate: Comparison library · Compliance · Releases · Changelog
- Contribute: Contributor guide · Security policy · Issues
- Support open source: Fund HitKeep on GitHub Sponsors or make a one-time contribution.
License
HitKeep is distributed under the MIT License.
Related MCP servers

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

Piia Engram
Local-first AI work identity layer—portable context across Claude Code, Cursor, Codex, and other MCP tools.
Keyless 12-tool patentability MCP: USPTO pillar scores, prior art, hosted at patentprecheck.com/mcp.

io.github.Patheras/gyibb-mcp
Cited product-review verdicts from real user voices — free remote MCP, no API key.

Tenpace Review Router
Human-authenticated setup for routing GitHub pull requests into the right Slack channel.
40 MCP tools: multi-chain RPC, market and transaction decisions, AI, EU compliance and US imports
