perfetto-mcp-rs
Related Servers
Alternatives to perfetto-mcp-rs
- FlicenseAqualityCmaintenanceA FastMCP server that provides LLMs with structured access to Scalene's CPU, GPU, and memory profiling for Python applications. It enables automated performance analysis, bottleneck identification, and optimization suggestions through natural language interactions in supported IDEs.71-
Related Servers
- FlicenseNot gradedqualityDmaintenanceA lightweight MCP memory server built on SQLite + FTS5, providing cross-session long-term memory for Claude Code.-
- FlicenseAqualityDmaintenanceMCP server that exposes llm-tldr code analysis tools (tree, structure, context, search, impact, etc.) to MCP clients like Claude Code for project understanding and debugging.18-
- AlicenseNot gradedqualityBmaintenanceMCP server for analyzing Android APK, DEX, or JAR files via a headless jadx engine, enabling LLM agents to query decompiled code, symbols, call graphs, and more.2GPL 3.0
- AlicenseAqualityBmaintenanceCode intelligence MCP server for Claude Code providing multi-project code graph, semantic search, session history, knowledge base, and web search.153MIT
- AlicenseAqualityAmaintenanceLocal-first MCP server that watches your coding sessions and injects a compact summary at the start of each new session. 85.6% token reduction, SQLite storage, no cloud. Works with Claude Code, Cursor, Cline, and Windsurf.1321 npm8MIT
- AlicenseAqualityCmaintenanceSemantic vector DB as an MCP server for Claude Code — SQLite + FTS5 + local ONNX embeddings. Gives Claude persistent, searchable project knowledge across conversations.12MIT
TDQS
Scored across 17 tools
Most tools have distinct purposes (page-load summaries, resource hotspots, main-thread hotspots, scroll jank, startup, interactions). However, `chrome_page_load_resource_summary`, `chrome_page_load_resource_hotspots`, and `chrome_page_load_resource_pipeline` all deal with resource URL analysis and could be confused, though their descriptions clarify the intended sequence (summary → hotspots → pipeline). The generic `execute_sql` and `list_*` tools are clearly separate.
All tools follow a consistent snake_case pattern with a clear domain prefix: `chrome_*` for Chrome-specific analysis, `list_*` for exploration, `execute_sql`, `load_trace`, `slice_descendants_breakdown`. Verbs are uniform (list, load, execute, chrome_page_load_*, chrome_main_thread_*) and the naming clearly indicates the tool's function.
17 tools is on the higher side but justified for a comprehensive Perfetto trace analysis server covering Chrome performance domains (page loads, resources, main thread, jank, startup, interactions) plus general SQL and schema exploration. Each tool serves a distinct purpose, and the count reflects the breadth of the domain without being bloated.
The tool set covers major Chrome performance analysis workflows (page loads, resources, main-thread tasks, scroll jank, startup, web interactions) plus generic trace exploration (processes, threads, tables, SQL). Minor gaps exist: no dedicated tool for memory or CPU profile analysis, and the resource pipeline depends on the summary/hotspots sequence, but `execute_sql` covers custom needs.