rtcStats

Query analyzed WebRTC sessions: observations, deductions, experience scores, and AI summaries.

CommunityOnlineAPI key requiredGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    An API key from the service settings is required

    Query analyzed WebRTC sessions: observations, deductions, experience scores, and AI summaries.

    How to connect

    How to connect rtcStats to Claude

    The server address to paste into Claude settings:

    https://api.rtcstats.com/v1.0/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect rtcStats to ChatGPT

    The server address to paste into ChatGPT settings:

    https://api.rtcstats.com/v1.0/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect rtcStats to Cursor

    The server address to paste into Cursor settings:

    https://api.rtcstats.com/v1.0/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (3)

    Raw names from tools/list. Only developers need these.

    get_quotaReturns the application token account: accountName, accountPlan (e.g. free, developer, trial_developer, enterprise), allowedCredits and remainingCredits (monthly plus purchased pool). Requires Authorization: Bearer <application JWT> on the MCP HTTP request.
    list_sessionsLists stored sessions for the application token account: rtcstatsId, createdAt, sessionStart, sessionEnd, title, rtcstatsUrl, embedUrl (Enterprise only), and abstract (denormalized session summary: browser/os, observation types+tags, severity counts, score band). Optional filters: name (title substring, any of), observationTypes (exact type names, any of), observationTags (any of), os, browser, browserVersion, userId, conferenceId, sessionId, hasCritical/hasHigh/hasMedium, hasLowScore/hasMediumScore/hasHighScore. Different filters are AND-combined; multiple values within one filter are OR-combined. Example queries: sessions about "zoom" on Safari + macOS, sessions with network observation tags, sessions having critical observations, sessions with a low experience score. Requires Authorization: Bearer <application JWT> on the MCP HTTP request.
    get_sessionReturns full session payload for one stored session (summary, observations, scores, etc.). Arguments: rtcstatsId (UUID). In data.observations[], each observation has type, severity, category, tags, firstSeenAt and a source object whose properties depend on the category: source.pid (peer connection id), source.sid (stream/datachannel report id), source.cpid (candidate-pair id), source.did (device entry id), source.rid (device row index), source.timestamp (device entry time), source.ssrcId (number, stream SSRC), source.labelId (device name). The top-level label is DEPRECATED and removed in the next schema version (overloaded legacy id; read source.ssrcId / source.sid / source.labelId instead). The full catalog of observation types (with possible severities and tags) is available from GET /v1.0/observations. Requires Authorization: Bearer <application JWT> on the MCP HTTP request.