Data and analytics

The Amplitude connector.

Product analytics: active users, events, sessions. Connect once with your own key. Every agent your team runs reads the same 6 tools under one permission model.

How access is governed

6

Read tools

Open by default. They run when called, and every call is logged with the endpoint, tool and capability.

0

Write tools

Amplitude exposes no write tools. Nothing it does mutates external state.

0

Destructive tools

Amplitude defines no destructive tools. Nothing here deletes data.

Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.

Every Amplitude tool

6 tools, named as the agent sees them.

  • get_active_usersread

    Get active or new user counts per interval over a date range (DAU/WAU/MAU-style series).

  • get_event_segmentationread

    Get counts for one event over a date range (totals or unique users per interval).

  • get_realtime_usersread

    Get active user counts for the last 5 minutes, compared to the same window yesterday.

  • get_avg_session_lengthread

    Get average session length per day over a date range.

  • search_userread

    Find a user by Amplitude id, user id, or device id and return their matching profiles.

  • list_annotationsread

    List chart annotations (releases, launches, incidents) the team has marked on their charts.

Use it from any agent

The same Amplitude tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.

.mcp.json · works for Cursor and Claude Desktop too
{
  "mcpServers": {
    "growth": {
      "type": "http",
      "url": "https://app.notara.ai/mcp/g/acme/growth",
      "headers": {
        "Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

The URL and token are placeholders. Real endpoints are issued per group from the dashboard.

Setup

  1. 01

    Create a Amplitude Secret Key in your Amplitude account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.

  2. 02

    Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.

  3. 03

    The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.

Connect Amplitude once. Use it everywhere.

Use Notara directly, or bring us the workflow that needs to be redesigned and built.