Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add amplitude/mcp-marketplace --skill getting-started-with-amplitudegit clone --depth 1 https://github.com/amplitude/mcp-marketplaceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/amplitude/mcp-marketplace/getting-started-with-amplitude)<a href="https://agentmods.dev/skills/amplitude/mcp-marketplace/getting-started-with-amplitude"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/getting-started-with-amplitude/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/amplitude/mcp-marketplace/getting-started-with-amplitude"><img src="https://agentmods.dev/badge/skills/amplitude/mcp-marketplace/getting-started-with-amplitude.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00134 | $0.01108 |
| Opus 5.5 | $0.00054 | $0.00443 |
| Sonnet 5.5 | $0.00027 | $0.00222 |
| Haiku 4.5 | $0.00013 | $0.00111 |
Grade A, and why
getting-started-with-amplitude scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 15d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 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 (analytics-skills, execution-skills, relevant product-skills). Supplemental skills may load from plugins/amplitude/skills/ per 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 — Docs is recommended but not required to verify project access.
Step 2: Region and OAuth
Ask unless known:
Is your Amplitude data in US (default) or EU residency?
Match the MCP URL before OAuth. On failure, check region mismatch first.
Step 3: Verify existing access
- Complete product MCP OAuth.
- Call
get_amplitude_contextwith noprojectId. - Summarize accessible orgs/projects.
If no projects appear:
- Troubleshoot OAuth, region, and account permissions.
- Do not promise automated new-org creation in this MVP.
- Use Docs MCP for general signup documentation only if the user is still becoming a customer outside this bot's scope.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 15d ago First seen · 95 lines · 134 tokens per session scan A 65825fec16ef
getting-started-with-amplitude is a skill published in the GitHub repository amplitude/mcp-marketplace (45 stars, last pushed yesterday), licensed MIT. It adds 134 tokens to every session and 1,108 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-03.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.