Model Context Protocol (MCP) server for WebRTC stats
rtcStats exposes a Model Context Protocol server, so an MCP client like Claude Code or Cursor can read your analyzed WebRTC sessions right in your IDE. MCP here means Anthropic's Model Context Protocol, the standard for connecting AI agents to tools, not a telecom media control plane. It is available on the Developer plan.
What the rtcStats MCP server does
Point an MCP-compatible agent at rtcStats and it can pull analyzed session data through natural language: list the sessions that failed, open one, and read the observations, deductions, experience score, and AI summary, without leaving the editor. On the Free plan you do the same thing by uploading the dump in the browser; the MCP-in-IDE path is available on the Developer plan and up.
Tools
- •
get_quota- Returns the application token account: plan, allowed credits, and remaining credits (monthly plus purchased pool). - •
list_sessions- Lists analyzed sessions with rich filters (browser, OS, experience score band, observation types and tags, user/conference/session IDs). - •
get_session- Returns the full analysis for one session: summary, observations, deductions, experience score, and the plain-English AI summary.
Connect your agent
The server speaks Streamable HTTP at https://api.rtcstats.com/v1.0/mcp. Send your application token as Authorization: Bearer on the request. Create a token under Settings > Applications (Developer plan).
Claude Desktop / Claude Code
{
"mcpServers": {
"rtcstats": {
"type": "http",
"url": "https://api.rtcstats.com/v1.0/mcp",
"headers": {
"Authorization": "Bearer YOUR_APPLICATION_TOKEN"
}
}
}
}Related
Want MCP access?
MCP is available on the Developer plan. Start free to analyze dumps in the browser today, then upgrade to Developer to query them straight from your IDE.
