CortIQ MCP server

Connect

1. In the CortIQ dashboard, open CortIQ API & MCP and create an API key for the site. Keys start with ck_live_ and are shown once.
2. Add the server to your MCP client. For Claude Code:

claude mcp add cortiq-analytics \
  --transport http \
  https://cxmkdtgfocgbfizawlwa.supabase.co/functions/v1/mcp-server \
  --header "Authorization: Bearer ck_live_YOUR_KEY"

Other clients need the endpoint URL and the Authorization header. We document Claude Code; we have not tested every client.

Tools

• Site and schema: cortiq_list_sites, cortiq_describe_schema.
• Traffic: cortiq_sessions_summary, cortiq_daily_visitors, cortiq_bounce_rate, cortiq_top_pages, cortiq_top_sources, cortiq_top_entry_pages, cortiq_top_exit_pages, cortiq_pageviews_by_device.
• Engagement: cortiq_avg_engagement_time, cortiq_click_counts, cortiq_heatmap_grid, cortiq_top_rage_clicks, cortiq_top_outbound, cortiq_web_vitals, cortiq_form_analytics, cortiq_funnel_completion.
• AI traffic: cortiq_ai_agent_traffic, cortiq_ai_bot_analysis, cortiq_ai_agent_journey, cortiq_ai_vs_human.

Every tool only reads data. There are no tools that write, delete or change settings.

Access and limits

• Each key reads exactly one site. Create one key per site.
• The same key works for the MCP server and the REST API.
• Keys are stored as SHA-256 hashes. You can disable or delete a key at any time.
• Rate limit per key, 1,000 requests per hour by default. You can change it when you create the key.

Protocol details

The server speaks JSON-RPC 2.0 over HTTP POST, with one JSON response per request. It reports MCP protocol version 2024-11-05 and supports initialize, ping, tools/list and tools/call. It does not stream (no SSE) and offers no resources or prompts.