- contact@insightclickiq.com
- Every click, every session, explained by AI
Claude Code, Claude Desktop, Cursor or any MCP client can query InsightClickIQ through the same engine the console uses. The model calling it never writes SQL either.
Each project page has a Connect an AI agent (MCP) card with ready-to-paste configuration for Claude Code, Claude Desktop, Cursor and curl. Authenticate with your access token or an API key; every tool resolves the caller and pins the database session to their organisation, the same row-level security the console uses.
Claude Codeclaude mcp add --transport http clickiq https://clickiq.example.com/mcp \
--header "Authorization: Bearer <api key>"
One definition per tool: the agent harness and the MCP server read the same schemas, so a tool added for one is available to the other.
| Group | Tools |
|---|---|
| Projects and catalog | list_projects, get_catalog (events, properties, top values) |
| Queries | run_query (any QuerySpec), compare_periods, drivers, web_overview, ask |
| Sessions | search_sessions, summarize_session |
| Signals and dashboards | list_signals, list_dashboards, get_dashboard |
| Journeys, zones, forms | journey_patterns, journey_compare, journey_dropoff, heatmap_pages, heatmap_zones, explain_page, forms_list, form_detail |
| Quality | errors, error_detail, performance |
| Audiences and markers | list_segments, segment_preview, list_annotations |
| Experiments and surveys | list_flags, experiment_results, list_surveys, survey_results |
| Reports | list_reports, render_report |
| Writes (editors only) | investigate, create_dashboard, save_segment, create_annotation, create_alert |
Type them into Ask, give them to an agent as a goal, or send them through MCP from your own assistant.
Ask from the editor whether the change you just shipped broke the funnel.
The assistant sees exactly what the person who connected it may see.
The tools are the agents' tools; new capabilities arrive in both.