Connect to Instinct
Paste this into Instinct. It connects the hosted Agent Analytics MCP server and pauses once for your sign-in.
Connect the Agent Analytics MCP server at https://mcp.agentanalytics.sh/mcp. Transport is Streamable HTTP. When it asks me to sign in, wait for me. I will sign in with Google or GitHub. Do not ask me for an API key. Then call list_projects and all_sites_overview and show me the result.Instinct brings product and growth questions into the conversation where you already work. Agent Analytics provides the analytics data. Instinct schedules the check and delivers the brief.
Use the hosted server documented in Skills vs MCP vs API:
- Server name: Agent Analytics
- Server URL:
https://mcp.agentanalytics.sh/mcp - Transport: Streamable HTTP
- Authentication: browser sign-in with Google or GitHub
Ask in chat with the prompt above. Complete browser sign-in with the identity that owns your Agent Analytics projects. You do not paste an account API key. The client must support remote Streamable HTTP and OAuth.
Prerequisites
Section titled “Prerequisites”- An Agent Analytics account and access to its Google or GitHub sign-in
- Instinct, with recurring tasks available
- A tracked project with real events for meaningful reports
If you still need instrumentation, follow First Project in 5 Minutes. Pageviews can verify that tracking works. Signups, purchases, feature use, and other events tied to your goals make the daily report useful. Some analytics reads require Pro. Your account’s usage limits apply.
Free hosted MCP includes list_projects, create_project, all_sites_overview, analytics_overview, bot_traffic_overview, and all_sites_bot_traffic. compare is free on every plan. query and the richer analytics tools require Pro.
Next: ask for a daily brief
Section titled “Next: ask for a daily brief”Copy this prompt and set the time and timezone you want:
Every day at 09:00 Asia/Jerusalem, use the connected Agent Analytics MCP tools and send me a short report here. Confirm the schedule, timezone, delivery destination, and next run before calling it set up. Run one report now to verify it.
Call list_projects. Call all_sites_overview for the account snapshot. For each project, call analytics_overview and read project_context when that result includes it. Use bot_traffic_overview or all_sites_bot_traffic when you need bot traffic called out. Use analytics_pages or analytics_breakdown when the overview is not enough. Use query only for a narrow count the other tools cannot answer. query is paid-only. A before/after read of a shipped change is the compare tool, which is free on every plan. compare takes project, goal_event, ship_date, window_days, and an optional nested rule. Use compare for a shipped change, not for yesterday versus the previous day. window_days must be a multiple of 7.
Compare the last completed day with the previous day and the latest completed seven days with the previous seven. State the exact date ranges and data timezone the tools returned. Use matching periods and definitions, separate bot traffic where a bot traffic tool supports it, and show counts alongside percentages. Flag small samples, missing events, plan limits, and failed reads instead of guessing.
Summarize what changed, which goal it affects, and one follow-up question or experiment worth considering. If nothing meaningful changed, say so briefly. Do not change my product, tracking, experiments, or account settings as part of this reporting task.Instinct owns this schedule. Connecting Agent Analytics does not create a recurring job. Ask Instinct to confirm it saved the task.
all_sites_overview, like the CLI command all-sites --period 7d, is an account overview, not an exact completed-day comparison. State the range the tool returned. Use non-overlapping completed windows. Do not compare a partial current day against a full previous day.
Project-scoped analytics results include project_context when it is non-empty. Annotations on those results cover the requested analytics date range plus one day before and after. The MCP tool append_project_annotation appends one annotation and takes project, occurred_at, title, and note. It does not replace the rest of project context.
Give the report context
Section titled “Give the report context”Project context stores each project’s goals, activation events, event glossary, and meaningful change annotations. Ask Instinct to propose missing goals and get your confirmation before storing initial durable context. Read existing context first so an update preserves useful information.
Portfolio context describes a shared growth system for intentionally related projects. Membership and identity grouping are separate from those interpretation notes. Neither should replace a project’s own goals or activation definition. See Projects, surfaces, and portfolios and Project context.
A daily brief should distinguish observed changes from hypotheses. More feature events alone do not prove that returning users are more engaged or explain why signups fell.
Fallback: connect with the CLI
Section titled “Fallback: connect with the CLI”Use the CLI when this Instinct runtime cannot call the hosted MCP server. That runtime must be able to run npx and keep CLI configuration between tasks.
Connect to my Agent Analytics account using the official CLI pinned to 0.5.41 (`npx --yes @agent-analytics/cli@0.5.41`). Start detached login, send me the approval URL, and wait for me to approve. I will reply with the finish code. Keep the saved login in persistent private storage so later scheduled tasks can use it. Do not ask me for an API key. Then run `auth status` and list my projects to confirm access.On this path, keep the same report rules as the daily brief above. Read goals with context get. A full annotation list is context get. Analytics responses include annotations only for the requested range plus one day before and after. Use all-sites --period 7d as an account overview. For a shipped-change read, run compare:
npx --yes @agent-analytics/cli@0.5.41 compare <project> --goal <event> --ship-date <YYYY-MM-DD>--days is window_days and defaults to 7. See Day-7 compare read.
What the login prompt runs
Section titled “What the login prompt runs”Instinct runs:
npx --yes @agent-analytics/cli@0.5.41 login --detached- Open the approval URL Instinct sends you.
- Sign in with the Google or GitHub identity that owns your Agent Analytics projects and approve access.
- For this detached handoff, return the one-time finish code shown after approval to Instinct.
- Instinct completes the command printed by the CLI, using the original request ID and your code:
npx --yes @agent-analytics/cli@0.5.41 login --auth-request <request-id> --exchange-code <finish-code>The CLI stores a renewable agent session. Keep credentials private. Do not paste long-lived account API keys or saved tokens into chat. Later runs can reuse the session while it remains valid.
Verify access before scheduling
Section titled “Verify access before scheduling”npx --yes @agent-analytics/cli@0.5.41 auth statusnpx --yes @agent-analytics/cli@0.5.41 all-sites --period 7dnpx --yes @agent-analytics/cli@0.5.41 context get my-siteReplace my-site with your project. The all-sites command gives an account overview. Inspect individual projects and their context before drawing conclusions. Check the current CLI reference for commands and plan requirements.
Reconnect, stop, or troubleshoot
Section titled “Reconnect, stop, or troubleshoot”- No projects: check that the approved Google or GitHub identity owns the expected account.
- No sign-in prompt: ask Instinct to call
list_projects, then approve the browser sign-in with the Google or GitHub identity that owns your projects. - MCP tools are unavailable in this runtime: use the CLI fallback and a private persistent directory through
AGENT_ANALYTICS_CONFIG_DIRor--config-dir, consistently for login and every scheduled command. Do not put saved credentials in a shared repository. - CLI session expired or revoked: repeat detached login and browser approval. The CLI refreshes valid sessions automatically. A failed read can also be a network or usage-limit issue, so inspect the error first.
- Stop reports: ask Instinct to cancel its recurring task and confirm cancellation.
- Revoke access: revoke the session in Agent Analytics Dashboard Settings / Agent Sessions. Cancel the Instinct task too, to avoid repeated failed reads.
