rybbit-super-mcp
Related Servers
Alternatives to rybbit-super-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables querying Rybbit Analytics data directly through MCP-compatible clients like Claude Code. It provides tools for monitoring website statistics, user sessions, error logs, funnels, and performance metrics via natural language.4342 npm4MIT
- AlicenseAqualityCmaintenanceEnables users to access and manage Savri analytics data, including visitor statistics, traffic sources, and conversion funnels, directly within Claude. It supports tracking custom event properties and creating multi-step conversion goals through natural language prompts.1517 npmMIT
- AlicenseAqualityDmaintenanceExposes Rybbit Analytics as MCP tools for querying site traffic, page views, visitor sessions, and live visitor counts through natural language.9270 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude Desktop to interact with Roistat analytics, orders, statistics, call tracking, and clients via 16 supported functions.1-
- FlicenseAqualityDmaintenanceConnects Claude to Google Analytics 4 for querying website analytics via natural language, enabling traffic summaries, top pages, traffic sources, and user engagement.4-
- AlicenseAqualityDmaintenanceFirst-party web analytics MCP server for AI agents, providing 42 tools to query traffic, events, funnels, conversions, sources, and performance data.4027 npmMIT
TDQS
Scored across 48 tools
Most tools are clearly distinct resource/action pairs, and the verbose descriptions help separate similarly named analytics queries. However, the large cluster of get_* metric, event-count, and timeseries tools could still cause misselection without careful reading.
All tools follow a consistent rybbit_<verb>_<noun> pattern with standard CRUD verbs and batch_create variants. There is no mixed casing or arbitrary verb usage, so an agent can reliably predict tool names.
48 tools is far above the 25+ threshold and creates a heavy selection surface for agents. The tools are logically grouped, but the count feels more like a full REST API dump than a curated MCP toolset.
The toolset provides strong coverage across sites, sessions, users, events, funnels, goals, performance, and configuration workflows, including CRUD where appropriate. Minor gaps exist: excluded IP/country lists are read-only, and there are no bulk update/delete operations for sites.