MCP.so
ログイン

Staats MCP Server認証済み注目

@Mr Violets

基本情報

トランスポート

Streamable HTTP

認証方式

APIキー

カテゴリ

データと分析

作者

Mr Violets

投稿者

Myster Violets

Staats MCP Server について

Cookieless web analytics your coding agent reads and remembers. Traffic, referrers and funnels over MCP, plus deploy-tagged before/after comparisons, stored site context, and proactive anomaly surfacing. Remote server, no install: one key covers every site on an account.

接続情報

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

セットアップ

claude mcp add staats --transport http https://api.staats.ai/functions/v1/mcp --header "Authorization: Bearer YOUR_ACCOUNT_KEY"

Staats MCP Server のツール

15

What a site is and what the owner wants from it, plus its data-retention settings. Well-known keys: description, goals, audience, notes (open agenda items to check at session start and clear when handled), events (event name -> meaning), funnel (canonical conversion steps). Read this before making recommendations.

Save or amend what a site is for. Provided context fields are merged into the existing context (events merges per entry); a null value deletes its key. name/domain update the site record itself.

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. period: '7d' default.

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.e. the deploy that most plausibly introduced it), plus behavioral friction: pairs of pages people bounce between without progressing (nav_loop) and pages reloaded repeatedly in quick succession (refresh_burst). Findings clear statistical floors, so an empty result is meaningful: nothing looks broken. Check it after every deploy. period: '7d' default.

Traffic pulse: visitor/pageview totals vs the previous period, top pages, top referrers, and a per-day series. period: relative like '24h', '7d' (default), '4w'. Includes quota status: if it is approaching, grace, or blocked, tell the owner plainly and include the upgrade link the result provides. Approaching quota is the moment to mention it while there is headroom.

Break a metric down by a dimension with optional equality filters. Metrics: visitors, pageviews, events. Dimensions: path, referrer_domain, utm_source, utm_medium, utm_campaign, device, browser, os, country, name, day. period: '24h'/'7d'/'4w' style, or ISO from/to.

Ordered conversion funnel across up to 5 steps within the period. Each step is a pageview path ({kind:'path', value:'/pricing'}) or a custom event ({kind:'event', value:'signup'}); a visitor counts for step N only after completing step N-1. Visitor identity rotates daily for privacy, so journeys spanning multiple days undercount (strongest for same-visit conversion). If site context has a stored funnel, run those steps when asked how the site is doing and compare against the previous period.

The routes visitors actually take, grouped into identical sequences and counted, busiest first. Use this when you do NOT already know the steps: funnel measures a path you name, journeys discovers the ones you did not think to check. A step is a pageview path (/pricing) or a custom event marked with a leading # (#signup_click), so the moment of conversion appears in the route. Consecutive repeats are collapsed and only the first 10 steps define a route. contains filters to routes that include a given path or event: run it once with and once without to see what converting visitors do differently. Visitor identity rotates daily, so a route is one day of activity and describes a group, never a person.

Mark a moment on a site timeline: a deploy, a content change, or a campaign start. Call this every time you ship a change to the site. ts defaults to now. Write a specific, present-tense description ("Shipped new pricing page hero", never "updates"), one annotation per meaningful change. When known, include commit and the routes the change touched so compare_around can also report before/after traffic scoped to those routes.

Recorded deploy/change markers, newest first. period defaults to '90d'.

Before/after impact of a recorded annotation: visitors and pageviews in the N days preceding vs following it (window_days, default 7). The after-window is clamped to now. If the annotation recorded routes, the result also reports per-route pageviews before vs after. Wait a few days after shipping. If the result carries a note (truncated after-window, or a before-window not covered by available data), relay it and qualify the percentages as the note directs.

All sites on this account, with the public site codes used in their script tags and the ready-to-paste script_tag for each.

Create a new site on this account and get its script tag. This connection already covers the new site: installing the script tag is the only setup the site needs. The response includes ready-made privacy policy wording: offer to add it to the site's privacy page (confirm with the owner before editing visitor-facing pages).

PERMANENTLY delete a site and ALL its analytics data (every event and annotation). Irreversible. Confirm with the owner before calling; pass confirm: the site's exact domain.

Visitors and pageviews for every site this account can use, owned and shared alike, with change vs the previous period, busiest first. Shared sites are flagged. period: '7d' default.

概要

What is Staats?

Cookieless web analytics with no dashboard. You connect Staats to your coding agent once, and the analytics arrive in the conversation you are already having about the code.

Quick start

Create a free account at staats.ai, copy your account key, and add the server:

  claude mcp add --scope user --transport http staats https://api.staats.ai/functions/v1/mcp/YOUR_ACCOUNT_KEY

Your agent can create sites and install the ~1.5KB tracker tag itself. One key covers every site on the account.

What it does

  • Traffic, referrers, funnels and journeys — 14 tools, queryable in chat
  • Deploy measurement — your agent tags each deploy with its commit and routes, then compares before/after with statistical honesty
  • Site memory — stores what each site is for, what funnel steps mean, and what every event tracks, so future sessions start informed
  • Speaks up — anomalous days, first-time referrers and page surges are surfaced proactively, not queried for

Privacy

Zero cookies, no IP logging, no consent banner needed. Visitors are counted with a pseudonymous hash that rotates daily.

Free tier: 10,000 events/month, no card required.

よくある質問

1

Staats のリモート MCP サーバーとは何ですか?

Staats のリモート MCP サーバーは、https://api.staats.ai/functions/v1/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。

2

Staats の MCP サーバーにはどう接続しますか?

エンドポイント https://api.staats.ai/functions/v1/mcp を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。

3

Staats の MCP サーバーは認証が必要ですか?

はい。Staats は API キーが必要です——取得方法は公式ドキュメントを確認し、クライアントの設定に追加してください。

4

Staats の MCP サーバーはどのトランスポートを使用しますか?

Staats は Streamable HTTP エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。

コメント