Documentation

Getting started

OverviewQuickstartConnect ClaudeConnect ChatGPTConnect Cursor, Claude Code, VS Code

Core concepts

How it worksWhat gets collectedData freshnessMetrics and moneyGetting good answers

Reference

All tools37
Start here
get_cro_overviewget_opportunity_sizingget_anomalies
Funnel and conversion
get_funnel_analysisget_conversion_correlationsget_cart_analysisget_exit_analysisget_journey_patternsget_session_insights
Page and element diagnostics
get_top_issuesget_element_click_analysisget_page_dom_snapshotget_click_heatmapget_click_analysisget_page_vitalsget_page_performanceget_form_analyticsget_hover_analysisget_section_visibilityget_js_errorsget_page_templates
Products and discovery
get_product_performanceget_product_catalogget_product_changesget_search_analysisget_product_page_structure
Individual sessions
get_session_journeysget_session_summaries
Measuring a change
get_before_after
Custom events
get_custom_event_suggestionstest_custom_event_rulecreate_custom_event_rulelist_custom_event_rulesdelete_custom_event_ruleget_custom_event_definitionsget_custom_event_statsget_custom_events

Guides

Playbooks21Custom eventsPlans and limits

Support

TroubleshootingPrivacy and security

Connect Cursor, Claude Code, VS Code

Clients with no OAuth of their own read a config file and send a bearer token. That covers Cursor, Claude Code, VS Code, Windsurf, and anything else that speaks streamable HTTP MCP.

  1. Generate an API key

    In your Shopify admin, open Apps → Click Context, go to the setup tab, and press Generate API key.

    The key is shown once and stored only as a hash. Copy it now. If you lose it, generate a new one — which invalidates the old one.

    Treat it like a password

    The key grants read access to your store's behavioural data and lets the holder create and delete custom event rules. Keep it out of a repository. Most clients let you reference an environment variable rather than inlining the value.

  2. Add the server to your MCP config

    Paste this into your client's MCP configuration, replacing YOUR_API_KEY:

    {
  "mcpServers": {
    "click-context": {
      "type": "http",
      "url": "https://app.clickcontext.com/api/mcp/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

    Configuration lives in different places per client:

    Cursor
    .cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project.
    Claude Code
    Run claude mcp add, or edit .mcp.json in the project root.
    VS Code
    .vscode/mcp.json, or the MCP section of your user settings.
    Windsurf
    ~/.codeium/windsurf/mcp_config.json.

  3. Restart the client and check the tool list

    Most clients read the config at start-up. After restarting you should see the Click Context tools listed. If the count is 37, the handshake and the key both worked.

The endpoint

URL
https://app.clickcontext.com/api/mcp/mcp
Transport
Streamable HTTP
Auth
HTTP header Authorization: Bearer <key>
Identity
Resolved from the key. You never pass a store id.

Do not use the Claude URL here

/api/mcp/sseexists for Claude's connector UI, which negotiates the transport itself. A config-file client takes the URL literally and will hang waiting on an SSE stream this deployment does not serve.

Rotating and revoking

Generating a new key immediately invalidates the previous one. There is one key per store, so rotating it disconnects every client using the old value — update them all in the same sitting.

Uninstalling the app ends access entirely, regardless of any key still sitting in a config file.

If your client does support OAuth

Prefer it. OAuth tokens are scoped to a connection and can be revoked without disturbing anything else. See Connect Claude for the flow — any client implementing the same discovery will work the same way.