Amplitude vs Git
A side-by-side look at the Amplitude and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Amplitude for customer data platforms work as a local process; choose Git for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Amplitude when
- You need dedicated capabilities in the Customer Data Platforms domain.
- You prefer a local stdio subprocess transport.
- You want tools like
amp_get_events, amp_get_active_users, amp_get_retention.
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Customer Data Platforms | Version Control |
| Quality signal | 48/100 · Fair | 81/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,540 |
| Directory activity | 1 views 0 installs 0 upvotes | 51 views 0 installs 0 upvotes |
| Tools | 5 | 16 |
| Full listing | View Amplitude | View Git |
Tools & capabilities
Amplitude tools 5
amp_get_eventsGet event counts and breakdowns for a date range (e.g., "2024-01-01" to "2024-01-31"). Returns frequency, user segments, and trends by event name.amp_get_active_usersGet active user counts by granularity (daily, weekly, or monthly) for a date range. Returns totals and trend data.amp_get_retentionGet user retention metrics for a cohort over time. Returns retention percentages by time period (e.g., day 1, day 7, day 30).amp_user_searchSearch for users by ID or property (e.g., email, user_id). Returns matching profiles with properties, event history, and segments.amp_get_user_activityGet recent event activity timeline for a specific user. Returns events with timestamps, properties, and interactions.
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Amplitude
{
"mcpServers": {
"amplitude": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-amplitude"
]
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Frequently asked questions
Amplitude is categorized under Customer Data Platforms and uses a local stdio subprocess. Git belongs to Version Control and uses a local stdio subprocess. Pick Amplitude for customer data platforms work and Git for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Amplitude has no declared pricing — check the project's own site. Git is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add amplitude and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Amplitude has a quality signal of 48/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 51 views, 0 installs and 91,540 GitHub stars.