HitKeep
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HITKEEP_JWT_SECRET | Yes | A long random string used for JWT token generation. Required for authentication. | |
| HITKEEP_GLAMA_MCP_TOKEN | Yes | Throwaway bearer token seeded into demo data so Glama can inspect the read-only MCP tools during release checks. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hitkeep_get_ai_visibilityA | Read AI crawler fetch overview, timeseries, and optional fetch-to-visit correlation for one site. |
| hitkeep_get_api_referenceA | Fetch an official HitKeep REST API reference page as markdown by path or operation slug. |
| hitkeep_get_docA | Fetch an official HitKeep docs page as markdown. |
| hitkeep_get_ecommerceB | Read ecommerce summary, top products, source stats, and aggregate city, provider, and ASN breakdowns for one site. |
| hitkeep_get_event_breakdownB | Read a count breakdown for one event property. |
| hitkeep_get_event_namesA | List event names tracked for one site in a date range. |
| hitkeep_get_funnel_statsA | Read aggregate step visitors, drop-off, and conversion for one configured funnel. |
| hitkeep_get_mcp_helpA | Return local MCP usage guidance, token setup, privacy boundaries, date ranges, and filter syntax. |
| hitkeep_get_opportunitiesA | Read saved localized Opportunities recommendations for one site without raw prompts or provider payloads. |
| hitkeep_get_qr_campaignsA | Read aggregate QR campaign opens, pageviews, visitors, and optional open timeseries without redirect tokens or raw hit data. |
| hitkeep_get_search_consoleA | Read imported Google Search Console overview, series, and optional dimension reports for one site. |
| hitkeep_get_search_console_statusA | Read Google Search Console mapping and sync status for one HitKeep site. |
| hitkeep_get_site_overviewA | Read aggregate traffic KPIs, top dimensions, goals, chart data, and optional comparison for one site. |
| hitkeep_get_web_vitalsA | Read aggregate Web Vitals p75, sample counts, rating counts, and optional page or visitor-context breakdowns for one site. |
| hitkeep_list_sitesA | List HitKeep sites visible to the bearer API client. |
| hitkeep_search_docsA | Search official HitKeep documentation using the LLM catalog and cached markdown pages. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| hitkeep-docs-llms | The official HitKeep llms.txt catalog. |
| hitkeep-mcp-help | Usage guidance for the official HitKeep MCP server. |
| hitkeep-metric-definitions | Definitions for core HitKeep analytics metrics returned by MCP tools. |
TDQS
Scored across 16 tools
All 16 tools have clearly distinct purposes. Analytics tools target specific data types (overview, ecommerce, web vitals, funnels, events, QR, search console, opportunities), while docs tools are separated into reference, doc, and search functions. No two tools appear to compute or return the same information.
Every tool follows the 'hitkeep_<verb>_<noun>' pattern, using either 'get', 'list', or 'search' as verbs. The resource nouns are descriptive and match the output type. This is a perfectly consistent and predictable naming scheme.
With 16 tools, the server is slightly above the typical 3-15 threshold, but each tool represents a distinct analytics report or documentation feature. The breadth is justified by the wide domain coverage, though a few tools could be consolidated without loss of clarity.
The tool set covers the major analytics aspects a user would expect from HitKeep (overview, ecommerce, web vitals, funnels, events, search console, QR, opportunities). The only missing pieces are write operations, but for a read-only analytics server that is appropriate. The documentation tools (get_doc, get_api_reference, search_docs) are a nice addition for self-navigation.