What is the main functional difference between NotWorking and Convai Analytics?

NotWorking is categorized under Monitoring and uses an install path we have not confirmed yet. Convai Analytics belongs to Monitoring and uses a local stdio subprocess. Pick NotWorking for monitoring work and Convai Analytics for monitoring.

How do I install NotWorking or Convai Analytics 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. NotWorking has no confirmed install command yet — follow its own setup instructions.

Are NotWorking and Convai Analytics free to use, or do they require API keys?

NotWorking is listed as free. Auth: no auth required. 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.

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

Yes. MCP clients support multiple servers: add notworking and convai-analytics 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, NotWorking has a quality signal of 53/100 (Good) with 0 views, 0 installs and 2 GitHub stars. Convai Analytics has 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars.

NotWorking vs Convai Analytics — MCP Server Comparison

NotWorking vs Convai Analytics — MCP Server Comparison | AllMCPs

Feature & specification comparison

Rows where the two servers differ are marked.

Spec	N NotWorking	Convai Analytics
Category	Monitoring	Monitoring
Quality signal	53/100 · Good	56/100 · Good
Install command	Not confirmed yet	Confirmed
Transport	—	Local subprocess (stdio)
Auth	No auth required	Not declared
Pricing	Free	Not declared
Required env vars	None listed	`CONVAI_API_KEY`
Verified owner	Community listing	Community listing
GitHub stars	2	0
Directory activity	0 views 0 installs 0 upvotes	1 views 0 installs 0 upvotes
Tools	2	44
Full listing	View NotWorking	View Convai Analytics

Tools & capabilities

NotWorking tools 2

check_statusIs it down or blocking agents for everyone, or just you? Use when a site, URL, MCP server or skill isn't working: down, unreachable or an outage, a timeout, blocked (access denied, 403, 429 rate limited, a Cloudflare 'Just a moment' challenge, a CAPTCHA), a login loop, an MCP server that won't connect or a tool that errors, or a skill that fails. Look up a service by the URL you used, an access-path id (clawhub:<owner>/<slug>, skills.sh:<owner>/<repo>/<skill>, an MCP Registry name like io.github.<owner>/<server>) or a service name. Returns a one-sentence summary, the service, every listed access path with a description and failure reports from the last hour (and the last 24 hours as context), the what_failed values and how to report. Unlisted targets return their own counts and status, with listed: false.
reportReport that an access path failed for you. Use the access-path id from check_status, or the URL you used. Only report failures that came from the service, not ones caused by your own tools, permissions or settings (like a fetch tool that refuses a domain). Anonymous. Never include personal data, booking details, credentials or full URLs with query strings. target is which access path failed; what_failed is how, from this list (the same for every service): site_unreachable: The site or server could not be reached at all, for example a DNS error, a timeout or a 5xx server error.; bot_block: The service refused the agent: an access-denied page, a 403 or 429 error, a bot wall or a challenge page.; captcha: A CAPTCHA or 'are you human?' check stopped the agent.; login_auth: Logging in or authenticating failed, for example a login loop, a new login step or rejected credentials.; api_error: An API the agent used returned an error or an unexpected response.; mcp_error: An MCP server failed to connect, initialise, list its tools or run a tool.; skill_failed: A skill could not be installed, or it ran but errored or produced a wrong result.; payment: A payment or checkout step failed or was blocked.; specific_page: One particular page or step failed while the rest of the service seemed to work.; other: Something else went wrong.

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.

NotWorking

No confirmed install command for NotWorking yet — follow the setup steps linked from its listing page rather than a guessed package name.

Convai Analytics

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "convai-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@convai/analytics-mcp@latest"
      ],
      "env": {
        "CONVAI_API_KEY": "YOUR_CONVAI_API_KEY_HERE"
      }
    }
  }
}

NotWorking vs Convai Analytics

Which MCP server should you choose?

N
Choose NotWorking when

Choose Convai Analytics when

Feature & specification comparison

Tools & capabilities

NotWorking tools 2

Convai Analytics tools 44

Ready-to-paste client configs

NotWorking

Convai Analytics

Frequently asked questions

NChoose NotWorking when

Choose Convai Analytics when

NotWorking tools 2

Convai Analytics tools 44

NotWorking

Convai Analytics

Frequently asked questions

What is the main functional difference between NotWorking and Convai Analytics?

How do I install NotWorking or Convai Analytics in Claude Desktop, Cursor, or Windsurf?

Are NotWorking and Convai Analytics free to use, or do they require API keys?

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

Which MCP server has higher directory engagement and quality ratings?

Popular comparisons with NotWorking

Popular comparisons with Convai Analytics

N
Choose NotWorking when