Amplitude Analytics connector for AI agents

Tools your analytics agent reaches for on Amplitude Analytics, scoped per tenant.

CALL ANY TOOL

Product analytics on the REST APIs: event segmentation, funnels, retention, cohorts, taxonomy, chart annotations, session replay, and exports. Keys stay vaulted.

amplitudeanalytics_list_annotation_categories

List annotation categories

List all chart annotation categories in the amplitude project, or filter to a single category by name.

Parameters

Name

Type

Required

Description

tags

string

Optional

New comma-separated list of tags for this event type.

For more tools, view docs.

Build your Agent

Drop the toolkit in, point it at the tenant, and your agent can run segmentation and funnel queries from the first run.

import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["amplitudeanalytics"], toolNames: ["amplitudeanalytics_get_event_segmentation", "amplitudeanalytics_get_funnel_results", "amplitudeanalytics_list_cohorts"] },
  pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  schema: z.object({}).passthrough(),
  func: async (args) => {
    const { data } = await sk.tools.executeTool({
      toolName: t.tool.definition.name,
      identifier: "user_123",
      params: args,
    });
    return JSON.stringify(data);
  },
}));

const agent = createReactAgent({ llm, tools: lcTools });

import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["amplitudeanalytics"], toolNames: ["amplitudeanalytics_get_event_segmentation", "amplitudeanalytics_get_funnel_results", "amplitudeanalytics_list_cohorts"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  type: "function",
  function: {
    name: t.tool.definition.name,
    description: t.tool.definition.description,
    parameters: t.tool.definition.input_schema,
  },
}));

const resp = await openai.responses.create({
  model: "gpt-4o", input: prompt, tools: llmTools,
});

import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["amplitudeanalytics"], toolNames: ["amplitudeanalytics_get_event_segmentation", "amplitudeanalytics_get_funnel_results", "amplitudeanalytics_list_cohorts"] },
  pageSize: 100,
});

const llmTools = tools.map((t) => ({
  name: t.tool.definition.name,
  description: t.tool.definition.description,
  input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
  model: "claude-sonnet-4-6", max_tokens: 1024,
  tools: llmTools,
  messages: [{ role: "user", content: prompt }],
});

import { Agent } from "@google/adk/agents";
import {
  MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
  connectionParams: new StreamableHTTPConnectionParams({
    url: "https://mcp.scalekit.com/amplitudeanalytics",
    headers: { Authorization: `Bearer ${userScopedToken}` },
  }),
});

const agent = new Agent({
  name: "agent", model: "gemini-2.0-flash",
  tools: await toolset.getTools(),
});

Try these prompts

Paste any prompt into your agent to start querying Amplitude from your workflows.

Funnels and retention

Copy the prompt

Copied

Where do users drop off in the onboarding funnel over the last 30 days?

Copy the prompt

Copied

Compare 7-day retention for users who connected a data source against those who did not.

Copy the prompt

Copied

Show conversion for [event_a] to [event_b] split by plan.

Segmentation

Copy the prompt

Copied

Break [event] counts down by country for last week.

Copy the prompt

Copied

Which events grew fastest month over month?

Copy the prompt

Copied

List the top property values sent with [event].

Taxonomy and cohorts

Copy the prompt

Copied

List cohorts in the project with size and last computed time.

Copy the prompt

Copied

Show event types with no schema description in the taxonomy.

Copy the prompt

Copied

Annotate today's chart with the v2.4 release.

SEE HOW AUTH WORKS

Your users connect once. Their Amplitude Analytics credentials stay vaulted, every call is scope-checked, and every action is logged.

Authorize

Your user connects

Amplitude Analytics

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Amplitude Analytics

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Amplitude Analytics

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Amplitude Analytics

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other connectors.

SALES

Deal intelligence agent

Score Gong call risk with an LLM, cross-reference the Attio record, and DM each owner their at-risk deals in Slack.

ENGINEERING

Engineering standup agent

Pull commits from GitHub and GitLab, track Jira issue movement, and post a per-engineer standup brief to Slack.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.

01.

Shared tokens break per-user analytics

A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.

// shared token
audit → bot_service_account
user_filter → broken

// scalekit
audit → user_abc
scope → enforced ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Amplitude Analytics today. Others tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Amplitude Analytics as the user or as a shared key?

As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.

Where is the Amplitude Analytics API key stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.

Can I limit what the agent is allowed to do in Amplitude Analytics?

Yes. Pass a tool name filter to listScopedTools so the analytics agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Amplitude Analytics.

What happens when a user revokes Amplitude Analytics access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Do analytics reads stay scoped to one Amplitude project?

Yes. The key pair you register is project scoped, and Scalekit stores it in that tenant's vault namespace. An agent call for one tenant resolves only that tenant's credential, so queries can never read another project's events.

On this page

Tool and actions Framework Compatibility Starter Prompt Auth Lifecycle Try Other Agents Why Scalekit