roblox-analytics-mcp
Related Servers
Alternatives to roblox-analytics-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA local MCP server that lets AI agents manage Roblox developer products and game passes through the Open Cloud API.1228 npmMIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that enables AI agents to execute Lua code, inspect scripts, spy on remotes, and interact with running Roblox game clients, including support for mobile executors on Android and iOS.139 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that allows AI agents to execute code, inspect scripts, spy on remotes, and interact with a running Roblox game client.139 npm20MIT
- FlicenseAqualityCmaintenanceAn MCP server that bridges AI to Roblox Studio, enabling execution of Luau scripts, instance manipulation, play-testing control, and Open Cloud operations via natural language.21-
- AlicenseAqualityFmaintenanceUnofficial MCP server that lets AI agents query Aptabase analytics using cookie-authenticated dashboard endpoints, providing tools for metrics, events, and sessions.171MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI agents to interact with a running Roblox game client, including code execution, script inspection, remote spying, and GUI automation.139 npm7MIT
TDQS
Scored across 19 tools
The query-related tools (query_metric, query_metrics, get_metric_report, get_experience_overview, compare_periods, breakdown_metric_by_segments) all read analytics data, but each description carves a distinct usage: single series, batch, themed packs, health check, period comparison, exhaustive segment scan. A couple of metadata/auth tools (get_server_status vs whoami, get_universe_info vs get_public_game_stats) are adjacent but their descriptions separate them.
Names are consistently snake_case and mostly verb-first: list_*, get_*, query_*, compare_periods, analyze_funel, find_universes. Minor deviations: 'whoami' is an idiom rather than verb_noun, and 'breakdown_metric_by_segments' uses 'breakdown' as a verb-ish noun instead of 'break_down_metric_by_segments'.
At 19 tools this is above the ideal 3-15 range, but the server spans analytics querying, metric/dimension discovery, reporting wrappers, funnel analysis, universe/place lookup, and account/config diagnostics, so the count is defensible. A few convenience tools could theoretically be folded into query_metric, but none feel disposable.
Core analytics workflows are well covered: discover metrics/dimensions, query single/bulk metrics, break down, compare periods, analyze funnels, and retrieve async results. Minor gaps: no direct place-list endpoint (place IDs must be discovered via dimension values then resolved with get_place_info) and alias configuration can be set but not explicitly removed.