Getting Started with Amplitude
First-run onboarding for the Amplitude Grok data-partner bot. Use when a user starts a new session, asks how to connect Amplitude MCP, needs US vs EU residency help, adding Docs MCP, confirming project access, or choosing what to do first with their existing Amplitude data. Trigger on "get started with Amplitude", "connect Amplitude MCP", "Amplitude bot", "help me use Amplitude in Grok", or "what can this bot do with my Amplitude project". Do not use this skill to lead with setup/instrumentation for brand-new orgs — this bot targets existing Amplitude customers.
Install
/plugin marketplace add amplitude/mcp-marketplaceThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add amplitude/mcp-marketplace --skill getting-started-with-amplitudegit clone --depth 1 https://github.com/amplitude/mcp-marketplace.git /tmp/mcp-marketplace
mkdir -p ~/.claude/skills
cp -r /tmp/mcp-marketplace/plugins/amplitude-grok/skills/getting-started-with-amplitude ~/.claude/skills/getting-started-with-amplitudePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# getting-started-with-amplitude You are the **first-run guide** for the Amplitude **data-partner** Grok bot. Verify MCP connectivity, confirm the user already has Amplitude projects, set safety expectations, and route to **analysis and product workflows** — not setup-first instrumentation. Read [`SAFETY.md`](../SAFETY.md) for the full session. ## Step 0: Set expectations This bot helps people who **already use Amplitude** explore data, explain charts, build dashboards, review experiments, read taxonomy context, and run briefings. **Setup-first signup and instrumentation pipelines are not the MVP story** (those come later in the product roadmap). Primary skills live in **[builder-skills](https://github.com/amplitude/builder-skills)** (`analytics-skills`, `execution-skills`, relevant `product-skills`). Supplemental skills may load from `plugins/amplitude/skills/` per [`CURATED_SKILLS.yaml`](../CURATED_SKILLS.yaml). ## Step 1: Two MCP servers | Server | URL | Auth | Purpose | | --- | --- | --- | --- | | **Product MCP** | US: `https://mcp.amplitude.com/mcp` · EU: `https://mcp.eu.amplitude.com/mcp` | OAuth | Project data, charts, dashboards, experiments | | **Docs MCP** | `https://amplitude.com/docs/api/mcp` | None | Public Amplitude documentation | Product MCP is **not** event ingestion. Point SDK questions to Docs MCP or public docs. If Docs MCP is missing, share [`MCP.md`](../MCP.md) — Docs is recommended but not required to verify project access.
Details
- Skill name
getting-started-with-amplitude- Repository
- amplitude/mcp-marketplace
- Path
plugins/amplitude-grok/skills/getting-started-with-amplitude/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Getting Started with Amplitude skill do?
First-run onboarding for the Amplitude Grok data-partner bot. Use when a user starts a new session, asks how to connect Amplitude MCP, needs US vs EU residency help, adding Docs MCP, confirming project access, or choosing what to do first with their existing Amplitude data. Trigger on "get started with Amplitude", "connect Amplitude MCP", "Amplitude bot", "help me use Amplitude in Grok", or "what can this bot do with my Amplitude project". Do not use this skill to lead with setup/instrumentation for brand-new orgs — this bot targets existing Amplitude customers.
How do I install the Getting Started with Amplitude skill?
Claude Code plugin: /plugin marketplace add amplitude/mcp-marketplace. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Getting Started with Amplitude popular?
It lives in amplitude/mcp-marketplace, which has 48 GitHub stars and 12 forks.
Related skills
Add Analytics Instrumentation
48amplitude/mcp-marketplace
End-to-end analytics instrumentation workflow for a PR, branch, file, directory, or feature. Reads the code, discovers what events should be tracked, and produces a concrete instrumentation plan — all in one shot. Use this skill whenever a user wants to add analytics to a PR, asks "instrument this PR", "add tracking to this branch", "what analytics does this file need", "instrument the checkout flow", "run the full instrumentation workflow", or any request that implies going from code changes to a tracking plan. Also trigger when the user gives you a PR link, branch name, file path, or feature
Analyze Account Health
48amplitude/mcp-marketplace
Summarizes B2B account health by analyzing usage patterns, engagement trends, risk signals, and expansion opportunities. Use for customer success reviews, renewal preparation, QBRs, or account prioritization.
Analyze AI Topics
48amplitude/mcp-marketplace
Analyzes what users ask AI agents about and how well each topic is served. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when the user asks "what are people asking the AI", "top AI topics", "where is the AI struggling", "AI coverage gaps", "what should we improve in our AI", or wants product insights from AI conversation patterns.
Investigate AI Session
48amplitude/mcp-marketplace
Deep-dives into specific AI agent sessions or failure patterns to explain why something went wrong. Only use when the user has Amplitude Agent Analytics instrumented in their project. Use when investigating a specific session ID, debugging agent failures, understanding why quality is low, tracing tool errors, or when monitor-ai-quality surfaces an issue that needs root cause analysis.
Event Description Generator
48amplitude/mcp-marketplace
Orchestrate event description audits by delegating chunk work to the event-descriptions-worker subagent. Resolve a project name to projectId via get_context when needed, then spawn worker subagents over cursors for a bounded run window and write outputs into run-scoped directories. Use when auditing missing event descriptions at scale without doing per-event analysis directly in this skill.
Iso 42001
33scytale-labs/GRC-Claude-Skills
Use when the user asks about ISO/IEC 42001 — Artificial Intelligence Management System (AIMS), AI risk assessment, the Annex A AI-specific controls, Annex B implementation guidance, AI governance, AI impact assessment, or using ISO 42001 alongside ISO 27001 for an AI-enabled product. For organizations building, deploying, or governing AI systems.
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.