--- title: "Connect Claude to HitKeep Analytics | HitKeep" description: "Install the first-party HitKeep plugin in Claude web or Claude Code, then configure a separate scoped MCP connection and review or revoke access." canonical: "https://hitkeep.com/guides/integrations/claude/" --- # Connect Claude to HitKeep Analytics Connect Claude to aggregate HitKeep reports in two separate steps: install the optional analytics skills, then authorize an MCP connection to your HitKeep instance. The package adds instructions; only the connection grants access to data. ## Before you start - Use a Claude account and client version with the relevant plugin or custom connector feature. Menu labels can vary by locale and account. - Sign in to the HitKeep instance that owns the sites you intend to share. - For OAuth, use an instance that advertises OAuth support. The published plugin is available independently of the 2.15.0 application rollout; [check release availability](https://hitkeep.com/guides/security/oauth/#release-availability), especially on 2.14.2 or older. - Hosted Claude connectors need a reachable HTTPS MCP endpoint. Self-hosted operators should follow the [MCP server guide](https://hitkeep.com/guides/integrations/mcp/) for the leader, proxy, and canonical public URL. ## Install the plugin in Claude web 1. Download the [HitKeep Analytics 2.15.0 ZIP](https://github.com/HitKeep/hitkeep-assistant-plugins/releases/download/v2.15.0/hitkeep-analytics-2.15.0.zip). The [release page](https://github.com/HitKeep/hitkeep-assistant-plugins/releases/tag/v2.15.0) includes `checksums.txt`. 2. Open **Settings → Plugins → Add → Upload plugin**. 3. Choose the ZIP, review the preview, and select **Upload**. 4. Confirm the plugin detail shows **HitKeep**, version **2.15.0**, and **5 Skills**. The installed view offers **Try in chat** and describes the package as adding instructions only. This is a private native archive installation, separate from approval in Anthropic’s public plugin directory. It does not add a connector or sign in to HitKeep. ## Install the plugin in Claude Code Add the first-party repository marketplace and install its analytics plugin: ``` claude plugin marketplace add HitKeep/hitkeep-assistant-plugins claude plugin install hitkeep-analytics@hitkeep claude plugin details hitkeep-analytics@hitkeep ``` The inventory should contain `hitkeep-analytics`, `hitkeep-traffic-diagnosis`, `hitkeep-ai-visibility-analyst`, `hitkeep-ecommerce-analyst`, and `hitkeep-tracking-verifier`. The skills-only package has no bundled MCP servers or executable hooks. Start a new client session if the installed skills are not yet visible. ## Copy the endpoint from HitKeep Open **Integration → Assistants** in HitKeep and copy the MCP endpoint. Use the exact displayed URL, including a custom path or reverse proxy prefix. Keep your EU, US, or self-hosted instance consistent throughout setup. ![HitKeep Assistants page showing the canonical MCP endpoint and Claude setup guidance](https://hitkeep.com/_astro/mcp.DtQD81jG_Z29RaME.webp) The endpoint belongs to your instance. The setup page does not verify whether Claude has connected. ## Connect Claude web through MCP 1. Open **Settings → Connectors → Add → Add custom connector**. 2. Enter a recognizable name and the exact HTTPS MCP URL copied from HitKeep. 3. Continue through the connector’s authentication flow. Sign in to HitKeep when prompted. 4. Review the requesting application, MCP resource, team, sites, and scopes. For analytics, use `sites:read` and `analytics:read` and select only the sites needed. 5. Complete the return to Claude and confirm the connector is connected before asking for analytics. For a hosted client with an HTTPS callback that requires a registered ID, ask a HitKeep team owner or admin to use **Integration → OAuth clients** and register the exact client and HTTPS callback URL. HitKeep uses public PKCE clients; do not invent a client secret. See the [OAuth client and callback requirements](https://hitkeep.com/guides/security/oauth/). ## Connect Claude Code through MCP Replace the example URL with the endpoint copied from your instance: ``` claude mcp add --transport http hitkeep https://analytics.example.com/mcp claude mcp login hitkeep ``` Use the native client’s validated HTTPS CIMD by default. If an explicit native registration is necessary, ask the HitKeep operator to [pre-register an operator-controlled public client](https://hitkeep.com/guides/security/oauth/#pre-register-an-operator-controlled-client). The team UI accepts HTTPS callbacks only; native HTTP loopback callbacks belong to validated CIMD or the operator-controlled registration. Complete the browser sign-in and review the same team, site, resource, and scope choices. Preserve the exact callback hostname and allow only permitted loopback port variation; do not add a client secret. If your instance does not offer OAuth, a separate [scoped API-client bearer connection](https://hitkeep.com/guides/integrations/mcp/) is available for clients that support manual headers. Keep tokens in the client’s secret store, outside prompts and committed configuration. ## Check the connection and manage access First ask Claude to list the HitKeep sites authorized for the connection. Then choose one and ask: “Summarize the last seven complete days and compare them with the previous seven. State the date range and any missing data.” Confirm the response uses aggregate HitKeep tools and the intended site. An installed plugin, a copied endpoint, or a successful sign-in alone does not prove an aggregate query succeeded. Use the dashboard to check a result that needs visual investigation. Open the HitKeep header user menu and choose **Connected applications** to inspect or revoke the grant. ![HitKeep connected application details with authorized sites, requested permissions, MCP resource, and Revoke access](https://hitkeep.com/_astro/oauth-application-details.Dff9osOA_ZxrMMP.webp) Review the actual grant in HitKeep. Removing a plugin and revoking an application’s data access are different actions. ## Troubleshooting | Symptom | Check | | --- | --- | | No plugin upload or custom connector option | Check your Claude client, account, and workspace feature availability; use the supported Claude Code path if appropriate. | | Plugin installed but no analytics tools | Configure MCP separately. The plugin intentionally contains no server connection. | | OAuth discovery missing | Confirm the instance version, valid HTTPS public URL, leader endpoint, and advertised OAuth support. Do not work around it by sharing dashboard cookies. | | Client or callback rejected | Register the exact public client and callback where needed; do not substitute a secret or change callback hostnames. | | No sites or access denied | Check consented sites, scopes, team membership, and current site permission. Selecting another dashboard site does not expand the grant. | | Revoked or expired grant | Start the client’s connect or sign-in flow again and review the new consent. Removing a stale client connection can be necessary before reconnecting. | | Empty reports | Check the date range, tracking data, and any required Search Console import or crawler feed before drawing conclusions. | MCP stays read-only and aggregate-only. Raw exports, administration, billing, token management, and dashboard sessions are outside this surface. See [MCP behavior and limits](https://hitkeep.com/guides/integrations/mcp/) and [the Claude integration overview](https://hitkeep.com/use-cases/claude-web-analytics/). [Previous MCP server](https://hitkeep.com/guides/integrations/mcp/)[Next ChatGPT analytics setup](https://hitkeep.com/guides/integrations/chatgpt/)