Cursor

Cursor Clics Remote MCP

Use the Clics remote MCP connector in Cursor.

Connection

The remote MCP endpoint is:

https://api.clics.dev/v1/mcp

In Cursor, the user installs Clics from the Marketplace or adds its remote MCP server, signs in to Clics, and selects a workspace.

Confirm the connected tool list before calling a tool. If the connector is not connected, ask the user to connect Clics in Cursor first.

Tool Workflow

Start with list_projects unless the user already gave a project_id.

Use project tools before analytics tools:

1. Resolve the project with list_projects or get_project.
2. If there is no project, follow Empty Workspace Setup.
3. Use goals, funnels, sessions, stats, or AI crawler tools against that project.
4. Report the project name or project_id, date range, filters, and environment.

Tools

Projects

Use projects to choose the analytics scope and to set up tracking.

Example:

{
  "name": "Acme",
  "website_url": "https://acme.com",
  "allow_localhost": true
}

Goals

Use goals to track conversions.

Goal types and rules:

Funnels

Use funnels to measure ordered conversion paths.

Funnel conversion window units:

seconds, minutes, hours, days, weeks, months

Funnel filter fields:

country, device, browser, os, page, event, hostname, referrer,
utm_source, utm_medium, utm_campaign, utm_term, utm_content

Funnel filter operators:

is, is_not, contains, not_contains

Sessions

Use sessions to inspect individual visits and their events.

Stats

Use query_stats for dashboard-style analytics.

Main input:

• project_id: required Clics project ID.
• metrics: required non-empty array of metric enums.
• date_range: required period preset string, or [start, end] ISO8601 pair.
• domain: optional domain filter. Schemes, paths, and ports are stripped by the API. Omit it for all production domains, or pass localhost for development traffic.
• timezone: optional IANA timezone. Defaults to UTC.
• dimensions: optional grouping. Use one time dimension, or up to two non-time breakdown dimensions.
• filters: optional tuples in [operator, dimension, values] format.
• order_by: optional tuples in [field, direction] format.
• include: optional object with previous_period and total_rows.
• pagination: optional object with limit and offset.

Metrics:

visitors, visits, pageviews, bounce_rate, visit_duration,
views_per_visit, conversion_rate, events

KPI and time-series metrics:

visitors, visits, pageviews, bounce_rate, visit_duration, views_per_visit

Breakdown metrics:

visitors, pageviews, conversion_rate, events

Dimensions:

event:page, event:hostname, event:name, event:outbound_url,
visit:country, visit:device, visit:browser, visit:os, visit:referrer,
referrer:ai_provider,
visit:utm_source, visit:utm_medium, visit:utm_campaign, visit:utm_term,
visit:utm_content,
time, time:hour, time:day

Time dimension presets:

time, time:hour, time:day

Use only one time dimension at a time. Do not combine a time dimension with breakdown dimensions.

Filter-only dimension:

event:goal

Stats filter operators:

is, is_not, contains, contains_not

Stats filter shape:

["is", "visit:country", ["US", "FR"]]

The first item is the operator, the second item is a filter dimension, and the third item is a string array of accepted values.

Stats filter dimensions:

event:page, event:hostname, event:goal, event:name, event:outbound_url,
visit:country, visit:device, visit:browser, visit:os, visit:referrer,
referrer:ai_provider,
visit:utm_source, visit:utm_medium, visit:utm_campaign, visit:utm_term,
visit:utm_content

Stats order shape:

["visitors", "desc"]

The first item is any metric or query dimension. The second item is asc or desc.

Stats include shape:

{
  "previous_period": true,
  "total_rows": true
}

previous_period is useful for KPI queries without dimensions. total_rows is useful with paginated breakdowns.

Stats pagination shape:

{
  "limit": 50,
  "offset": 0
}

limit must be between 1 and 1000. offset must be 0 or greater.

Example:

{
  "project_id": "project_123",
  "date_range": "last7days",
  "metrics": ["visitors", "pageviews"],
  "dimensions": ["time:day"],
  "timezone": "Europe/Paris"
}

AI Crawler Analytics

Use get_ai_crawler_analytics to inspect AI crawler activity. AI crawler analytics are production-only; use no environment argument.

Main input:

• project_id
• optional date_range
• optional timezone
• optional filters: category, provider, crawler, status
• optional operators: provider_op, crawler_op, status_op

AI crawler categories:

answer_fetch, search_index, training

AI crawler filter operators:

is, is_not

AI crawler providers:

OpenAI, Anthropic, Perplexity, Google, Microsoft, Mistral, Amazon,
DuckDuckGo, Apple, Moonshot AI, Common Crawl

AI crawlers:

ChatGPT-User, OAI-SearchBot, GPTBot,
Claude-User, Claude-SearchBot, ClaudeBot,
Perplexity-User, PerplexityBot,
Google-Agent, Google-GeminiNotebook, Google-NotebookLM,
Google-Read-Aloud, Google-InspectionTool, Googlebot, GoogleOther,
Google-CloudVertexBot,
Bingbot, msnbot,
MistralAI-User, MistralAI-Index,
Amzn-User, Amzn-SearchBot, Amazonbot,
DuckAssistBot,
Applebot,
Kimi-User, Kimi-SearchBot, KimiBot,
CCBot

Example:

{
  "project_id": "project_123",
  "date_range": "last30days",
  "timezone": "Europe/Paris",
  "provider": "OpenAI",
  "provider_op": "is",
  "category": "answer_fetch"
}

Input Shapes

These examples mirror the remote MCP tool schemas. Use the live tool schema as the final source of truth if Cursor shows a field-level schema.

Project Inputs

list_projects accepts optional pagination:

{
  "limit": 20,
  "cursor": "next_cursor"
}

get_project and delete_project:

{
  "project_id": "project_123"
}

create_project:

{
  "name": "Acme Marketing",
  "website_url": "example.com",
  "allow_localhost": false
}

update_project requires project_id and at least one field to change:

{
  "project_id": "project_123",
  "name": "Acme",
  "website_url": "acme.com",
  "allow_localhost": true
}

Goal Inputs

list_goals:

{
  "project_id": "project_123",
  "env_id": "production"
}

create_goal uses display_name and goal_type:

{
  "project_id": "project_123",
  "env_id": "production",
  "display_name": "Signup",
  "goal_type": "page",
  "rule": {
    "page_path": "/signup"
  }
}

update_goal does not take project_id. Pass goal_id and at least one field:

{
  "goal_id": "goal_123",
  "display_name": "Trial signup",
  "rule": {
    "page_path": "/thank-you"
  }
}

delete_goal:

{
  "goal_id": "goal_123"
}

Funnel Inputs

list_funnels accepts optional pagination:

{
  "project_id": "project_123",
  "env_id": "production",
  "limit": 20,
  "cursor": "next_cursor"
}

get_funnel and delete_funnel use only funnel_id:

{
  "funnel_id": "funnel_123"
}

create_funnel requires at least two ordered steps. Each step needs a name and at least one filter:

{
  "project_id": "project_123",
  "env_id": "production",
  "name": "Checkout",
  "conversion_window": {
    "value": 7,
    "unit": "days"
  },
  "steps": [
    {
      "name": "Cart",
      "filters": [
        {
          "filter_type": "page",
          "operator": "is",
          "values": ["/cart"]
        }
      ]
    },
    {
      "name": "Purchase",
      "filters": [
        {
          "filter_type": "page",
          "operator": "is",
          "values": ["/thanks"]
        }
      ]
    }
  ]
}

update_funnel does not take project_id. Pass funnel_id and at least one field:

{
  "funnel_id": "funnel_123",
  "name": "Updated checkout"
}

Session Inputs

list_sessions:

{
  "project_id": "project_123",
  "domain": "example.com",
  "date_range": "last7days",
  "limit": 20,
  "cursor": "next_cursor"
}

For a custom session range, pass both start and end; when both are set, date_range is ignored:

{
  "project_id": "project_123",
  "start": "2026-09-01",
  "end": "2026-09-03"
}

get_session and list_session_events:

{
  "project_id": "project_123",
  "session_id": "session_123",
  "date_range": "allTime"
}

Stats Inputs

query_stats takes the full stats request body. date_range is either a preset string or a two-item [start, end] ISO8601 array.

Complete accepted input fields:

project_id, domain, timezone, metrics, date_range, dimensions, filters,
order_by, include, pagination

Stats date range presets:

last24h, last7days, last30days, last3months, last12months,
monthToDate, quarterToDate, yearToDate, allTime

Stats time dimension presets:

time, time:hour, time:day

Use time:hour for hourly series, time:day for daily series, and time only when the dashboard-level aggregate time bucket is wanted. Do not combine these with country/device/page/referrer/event breakdown dimensions.

KPI query:

{
  "project_id": "project_123",
  "domain": "example.com",
  "timezone": "Europe/Paris",
  "metrics": ["visitors", "pageviews", "bounce_rate"],
  "date_range": "last30days",
  "include": {
    "previous_period": true
  }
}

Time-series query:

{
  "project_id": "project_123",
  "timezone": "Europe/Paris",
  "metrics": ["visitors", "visits", "pageviews"],
  "date_range": "last7days",
  "dimensions": ["time:day"],
  "order_by": [["time:day", "asc"]]
}

Breakdown query with filters, sort, and pagination:

{
  "project_id": "project_123",
  "metrics": ["visitors", "pageviews"],
  "date_range": ["2026-09-01T00:00:00Z", "2026-09-03T23:59:59Z"],
  "dimensions": ["visit:country"],
  "filters": [["is", "visit:device", ["desktop"]]],
  "order_by": [["visitors", "desc"]],
  "pagination": {
    "limit": 50,
    "offset": 0
  }
}

AI Crawler Inputs

get_ai_crawler_analytics uses production implicitly. provider and crawler may be a single enum value or a non-empty array of enum values. Use provider_op, crawler_op, and status_op for filter operators.

{
  "project_id": "project_123",
  "date_range": "last30days",
  "timezone": "Europe/Paris",
  "category": "answer_fetch",
  "provider": ["OpenAI", "Anthropic"],
  "provider_op": "is",
  "crawler": "GPTBot",
  "crawler_op": "is_not",
  "status": "200",
  "status_op": "is",
  "breakdown_limit": 50,
  "filter_values_limit": 200
}

For a custom AI crawler range, pass start and end:

{
  "project_id": "project_123",
  "start": "2026-09-01T00:00:00Z",
  "end": "2026-09-03T23:59:59Z"
}

Shared Presets

Environment values:

production, development

env_id is used by goals and funnels. Default to production when the user does not specify an environment. query_stats does not take env_id; use its domain field, or pass localhost as the domain for development traffic.

Date range presets:

last24h, last7days, last30days, last3months, last12months,
monthToDate, quarterToDate, yearToDate, allTime

For a custom range, pass the explicit start and end dates in the format expected by the tool schema.

Timezone values are IANA timezones, for example:

UTC, Europe/Paris, Europe/London, America/New_York, America/Los_Angeles

Empty Workspace Setup

Start by calling list_projects when the user asks to inspect analytics and no project is known. If the workspace has no projects, pause analytics work and ask the user for:

• project name
• production website domain
• whether localhost tracking should be allowed for development

Create the project with create_project. After creation, use the returned project_id in the setup instructions.

Browser Tracking Setup

After creating the project, help the user install browser tracking. Read:

https://docs.clics.dev/installation-guides

Choose the section that matches the user's framework. If the framework or entry file is unclear, ask where the app shell, root layout, or HTML head lives.

Give the user the browser tracking snippet with the real project_id already filled in:

<script
  defer
  data-project-id="<project_id>"
  src="https://clics.dev/tracker.js"
></script>

For Next.js, use the same project_id in next/script:

<Script
  strategy="afterInteractive"
  src="https://clics.dev/tracker.js"
  data-project-id="<project_id>"
/>

Help the user place the snippet in the correct file, then tell them to open the site and check the Clics dashboard for the first pageview.

AI Crawler Tracking Setup

AI crawler analytics uses a separate server-side setup. Read:

https://docs.clics.dev/installation-guides/ai-crawler-tracking

Identify the section for the user's runtime, such as Next.js, TanStack Start, Hono, Express, Cloudflare, or a generic Fetch handler. Help the user add the server-side tracking code and the required project-scoped crawler token.

Use get_ai_crawler_analytics after setup to verify crawler activity when data is available. Report that AI crawler analytics are production-only.

Reporting

When reporting analytics, state:

• project used
• date range
• timezone when provided
• filters applied
• environment when the tool accepts env_id
• domain when the tool accepts domain
• for AI crawler analytics, production is implied

When a result is empty, say whether the workspace has no project, the project has no data for that date range, or the filters removed all rows.