Docs

MCP server

Connect Claude Code, Claude Desktop or Cursor in one step. The assistant sees what the person who connected it may see.

InsightClickIQ is an MCP server. Any client that speaks the Model Context Protocol can query a customer’s analytics through the same engine and tool registry the console’s agents use.

Endpoint and transport

URLPOST https://clickiq.example.com/mcp
TransportStreamable HTTP, stateless, JSON responses: one JSON-RPC 2.0 request per POST, one JSON answer; no session ids, no SSE stream. initialize is optional
Protocol versions2024-11-05, 2025-03-26, 2025-06-18, 2025-11-25 and 2026-07-28
AuthAuthorization: Bearer <access token or API key>. Create an API key under Users → API keys, or POST /api/user/api-keys
ScopeEvery tool runs as the caller, pinned to their organisation by the same row-level security as the console; write tools need an editor

Claude Code

claude mcp add --transport http clickiq https://clickiq.example.com/mcp --header "Authorization: Bearer <token>"

Claude Desktop and Cursor

claude_desktop_config.json / .cursor/mcp.json
{ "mcpServers": { "clickiq": {
    "type": "http",
    "url": "https://clickiq.example.com/mcp",
    "headers": { "Authorization": "Bearer <token>" } } } }

curl

curl -s https://clickiq.example.com/mcp -H 'Authorization: Bearer <token>' \
  -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' 
clickiq.example.com/projects · MCP
‘Connect an AI agent (MCP)’ card showing a server URL, bearer-token instructions, tabs for Claude Code, Claude Desktop, Cursor and curl, a one-line ‘claude mcp add --transport http clickiq …’ command, and 33 tool names such as run_query, journey_dropoff, explain_page and render_report.
One command connects Claude Code (or Desktop or Cursor) to the project’s analytics. The tool list shows what an agent can call, from list_projects to create_alert and render_report. The server URL was replaced with an example host.

Tools

37 tools from the shared registry. Inputs are JSON schemas; results are compact JSON with table rows capped at 50 and every rate a fraction.

ToolWhat it returns
list_projects, get_catalogProjects; a project’s events (with 30-day counts), properties and samples, top pages, sources, countries
run_queryAny QuerySpec’s result; a validation error is the tool error
compare_periods, driversNow against the previous period; which source, referrer, device, country, browser or path carries a change
web_overviewThe Overview’s KPIs, series, top pages and sources
askAsk’s answer with its queries, sessions and dashboards
search_sessions, summarize_sessionSessions by any filter (up to 25); a session’s intent, outcome, frustration and highlights
list_signalsSignals with impact and recommendation
list_dashboards, get_dashboard, list_reports, render_reportDashboards with widget specs; reports rendered with their narrative
journey_patterns, journey_compare, journey_dropoffJourneys
heatmap_pages, heatmap_zones, explain_pageZones and the page explanation
forms_list, form_detail, errors, error_detail, performanceForms and quality
list_segments, segment_preview, list_annotationsAudiences and markers
list_flags, experiment_resultsFlags and experiments; an experiment’s variants, uplift, p, P(beat control) and readout
list_surveys, survey_resultsSurveys with response rates and NPS; results and AI themes (counts and themes, never the raw open-text answers)
Editors onlyinvestigate, create_dashboard, save_segment, create_annotation, create_alert

Resources: clickiq://projects and clickiq://projects/{project_id}/catalog. GET /api/mcp/info returns the URL, tools and these snippets, which the project page shows with copy buttons.

Need a hand with the integration?

Send us your event list or your app's screen map and we will review it before you ship.

Talk to an engineer