Convai Analytics vs Git
A side-by-side look at the Convai Analytics 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 Convai Analytics for monitoring work as a local process; choose Git for other tools and integrations as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Convai Analytics when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
CONVAI_API_KEY. - You want tools like
get_summary, get_metrics_catalog, list_sessions.
Choose Git when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_entities, create_relations, add_observations.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Other Tools and Integrations |
| Quality signal | 56/100 · Good | 89/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 | CONVAI_API_KEY | None listed |
| Verified owner |
Tools & capabilities
Convai Analytics tools 44
get_summaryAnswer account-level questions like how many sessions, interactions, unique end users, errors, and headline latency percentiles happened in a time range.get_metrics_catalogList the public metrics this account can query so an agent can choose the right latency, reliability, usage, provider, or model metric.list_sessionsFind recent, longest, or slowest sessions for the caller's account before drilling into a session timeline or interaction trace.get_session_timelineShow the timeline of metrics and interaction ids inside one session, useful for explaining why a session felt slow.get_interaction_traceShow the per-request component spans for one interaction id, including processor/provider/model durations where available.get_first_response_summaryCharacter-first, mode-specific first-response SLA P50/P95/P99. Defaults include turn 1; use turnScope=warm for turn_id > 1.get_first_response_timeseriesBucketed first-response SLA P50/P95/P99 for one character and optional observed mode.get_first_response_breakdownGroup first-response SLA P50/P95/P99 for one character by mode, settings_hash, stage, provider, model, status, or turn_scope.get_first_response_markersReturn settings-hash change markers for one character's first-response latency graph.get_first_response_settingsFetch one sanitized latency-relevant settings snapshot by settings hash.get_interaction_first_responseReturn the additive first-response waterfall for one interaction id.get_p95_latency_over_time
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.
Convai Analytics
{
"mcpServers": {
"convai-analytics": {
"command": "npx",
"args": [
"-y",
"@convai/analytics-mcp@latest"
],
"env": {
"CONVAI_API_KEY": "YOUR_CONVAI_API_KEY_HERE"
}
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
Frequently asked questions
Convai Analytics is categorized under Monitoring and uses a local stdio subprocess. Git belongs to Other Tools and Integrations and uses a local stdio subprocess. Pick Convai Analytics for monitoring work and Git for other tools and integrations.
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.
Convai Analytics 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 convai-analytics and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Convai Analytics has a quality signal of 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Git has 89/100 (Excellent) with 39 views, 0 installs and 91,289 GitHub stars.