What is the main functional difference between Convai Analytics and MCP Uptime Kuma?

Convai Analytics is categorized under Monitoring and uses a local stdio subprocess. MCP Uptime Kuma belongs to Monitoring and uses a local stdio subprocess. Pick Convai Analytics for monitoring work and MCP Uptime Kuma for monitoring.

How do I install Convai Analytics or MCP Uptime Kuma in Claude Desktop, Cursor, or Windsurf?

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.

Are Convai Analytics and MCP Uptime Kuma free to use, or do they require API keys?

Convai Analytics has no declared pricing — check the project's own site. MCP Uptime Kuma 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.

Can I run both Convai Analytics and MCP Uptime Kuma at the same time in my AI client?

Yes. MCP clients support multiple servers: add convai-analytics and mcp-uptime-kuma as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Convai Analytics has a quality signal of 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars. MCP Uptime Kuma has 60/100 (Good) with 1 views, 0 installs and 55 GitHub stars.

Convai Analytics vs MCP Uptime Kuma

Convai Analytics vs MCP Uptime Kuma | AllMCPs

Feature & specification comparison

Rows where the two servers differ are marked.

Spec	Convai Analytics	MCP Uptime Kuma
Category	Monitoring	Monitoring
Quality signal	56/100 · Good	60/100 · Good
Install command	Confirmed	Confirmed
Transport	Local subprocess (stdio)	Local subprocess (stdio)
Auth	Not declared	Not declared
Pricing	Not declared	Not declared
Required env vars	`CONVAI_API_KEY`	`UPTIME_KUMA_URLUPTIME_KUMA_USERNAMEUPTIME_KUMA_PASSWORDUPTIME_KUMA_2FA_TOKENUPTIME_KUMA_JWT_TOKENUPTIME_KUMA_HEADERS`
Verified owner	Community listing	Community listing
GitHub stars	0	55
Directory activity	1 views 0 installs 0 upvotes	1 views 0 installs 0 upvotes
Tools	44	26
Full listing	View Convai Analytics	View MCP Uptime Kuma

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_timeAnswer whether p95 end-to-end voice latency is getting better or worse over time.
+32 more on the listing page

MCP Uptime Kuma tools 26

getMonitorSummaryGet a quick overview of all monitors with their current status. Supports filtering.
listMonitorsGet the full list of all monitors with configurations. Supports filtering.
listMonitorTypesGet all available monitor types supported by Uptime Kuma.
getMonitorGet detailed configuration for a specific monitor by ID.
createMonitorCreate a new monitor (requires name and type at minimum).
updateMonitorUpdate an existing monitor's configuration.
deleteMonitorPermanently delete a monitor and all its heartbeat history.
pauseMonitorPause a monitor to stop performing checks.
resumeMonitorResume a paused monitor to restart checks.
listHeartbeatsGet status check history for all monitors.
getHeartbeatsGet status check history for a specific monitor.
listNotificationsList all configured notification channels (Slack, Discord, email, webhooks, etc.).
+14 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.