amplitude-mcp-analytics

# amplitude-mcp-analytics Amplitude MCP Analytics SDK — Model Context Protocol server usage tracking for Amplitude Analytics. > **Status:** Preview. Server and tool instrumentation, the default event set, > identity resolution, and custom events are available now. Transport and > correlation handling (stdio, Streamable HTTP — stateful and stateless — and > SSE) is handled for you under the hood. ## Install ```bash uv add amplitude-mcp-analytics 'mcp>=1.16,<2' ``` `amplitude-analytics` comes along as a dependency — nothing else to install whichever way you construct the client. `mcp` is listed here because your MCP server needs it, not because this SDK depends on it: the coupling is duck-typed, so the SDK never pins a range against yours. The supported range is **`mcp>=1.16,<2`**. The `mcp` 2.x line restructures the server internals; a 2.x server is detected and rejected with a clear error rather than silently emitting nothing (2.x support is planned). > **Agent-assisted setup:** the > [`instrument-mcp-server` skill](https://github.com/amplitude/builder-skills/tree/main/engineering-skills/skills/instrument-mcp-server) > (part of the [builder-skills](https://github.com/amplitude/builder-skills) > `engineering-skills` plugin) exists for agent-assisted setup, but it was > written for the Node SDK. A coding agent can still follow this README > manually to instrument a Python server. ## Quick start ```python import os from mcp.server.fastmcp import FastMCP from amplitude_mcp_analytics import AmplitudeMCPAnalytics mcp = FastMCP("my-mcp-server") analytics = AmplitudeMCPAnalytics( api_key=os.environ["AMPLITUDE_API_KEY"], server_name="my-mcp-server", server_version="1.0.0", ) # Bind the server (enables analytics + emits connection events), then wrap your # tool handlers. Order matters: instrument_server() must run before mcp.run(). analytics.instrument_server(mcp, auth_type="oauth") @mcp.tool() # @mcp.tool() stays outermost — see below @analytics.i…