← staats.ai

INDIVIDUAL MCP TOOL

funnel

Ordered conversion funnel across up to 5 steps within the period.

staats.ainone authenticationAvailability not checked

LIVE ENDPOINT

https://api.staats.ai/functions/v1/mcp

No auth detected

Connect to this endpoint to inspect the live schema for funnel and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

  • No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

staats.ai

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.staats]
url = "https://api.staats.ai/functions/v1/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "staats": {
      "type": "http",
      "url": "https://api.staats.ai/functions/v1/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: staats
Remote MCP URL: https://api.staats.ai/functions/v1/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "staats": {
      "url": "https://api.staats.ai/functions/v1/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "staats": {
      "type": "http",
      "url": "https://api.staats.ai/functions/v1/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "staats",
  "transport": "streamable-http",
  "url": "https://api.staats.ai/functions/v1/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • get_site_context — What a site is and what the owner wants from it, plus its data-retention settings.
  • update_site_context — Save or amend what a site is for.
  • what_changed — Notable movements in the period without scanning raw numbers: statistically unusual traffic days, referrer surges and first-time referrers, pages whose share of traffic jumped, alongside the annotations recorded in the same period.
  • what_broke — Signs of visitors hitting problems in the period: JS errors the tracker captured (new_error, error_spike: each with a sanitized sample message, source, line, affected visitor count, and the nearest annotation, i.
  • get_overview — Traffic pulse: visitor/pageview totals vs the previous period, top pages, top referrers, and a per-day series.
  • query — Break a metric down by a dimension with optional equality filters.
  • journeys — The routes visitors actually take, grouped into identical sequences and counted, busiest first.
  • record_annotation — Mark a moment on a site timeline: a deploy, a content change, or a campaign start.