YouTube Trends MCP vs Convai Analytics
A side-by-side look at the YouTube Trends MCP and Convai Analytics MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose YouTube Trends MCP for monitoring work over a hosted endpoint; choose Convai Analytics for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose YouTube Trends MCP when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
TRENDSMCP_API_KEY. - You want tools like
get_time_series, get_growth, get_top_trends.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 49/100 · Fair | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | TRENDSMCP_API_KEY | CONVAI_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 3 | 44 |
| Full listing | View YouTube Trends MCP | View Convai Analytics |
Tools & capabilities
YouTube Trends MCP tools 3
get_time_seriesWeekly (or daily) history for **one** `source` + `keyword`. Same name on MCP and REST (`mode: "get_time_series"`). REST also accepts `get_trends` as an alias.get_growthPoint-to-point percent change. Several windows in one call still count as **one** request for that source + keyword.get_top_trendsLive ranked list. **No keyword.** On MCP, `type` is required and must match the feed name **exactly** (including capitals). On REST, omit `type` only if you intend to pull every feed (billed per feed).
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_timeAnswer whether p95 end-to-end voice latency is getting better or worse over time.- +32 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.
YouTube Trends MCP
{
"mcpServers": {
"youtube-trends-mcp": {
"url": "https://api.trendsmcp.ai/mcp"
}
}
}
Convai Analytics
{
"mcpServers": {
"convai-analytics": {
"command": "npx",
"args": [
"-y",
"@convai/analytics-mcp@latest"
],
"env": {
"CONVAI_API_KEY": "YOUR_CONVAI_API_KEY_HERE"
}
}
}
}
Frequently asked questions
YouTube Trends MCP is categorized under Monitoring and uses a remote HTTP/SSE transport. Convai Analytics belongs to Monitoring and uses a local stdio subprocess. Pick YouTube Trends MCP for monitoring work and Convai Analytics for monitoring.
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.
YouTube Trends MCP has no declared pricing — check the project's own site. Convai Analytics has no declared pricing — check the project's own site. 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 youtube-trends-mcp and convai-analytics as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, YouTube Trends MCP has a quality signal of 49/100 (Fair) with 3 views, 0 installs and 1 GitHub stars. Convai Analytics has 56/100 (Good) with 2 views, 0 installs and 0 GitHub stars.