In-depth architectural comparison of the Linux MCP Server and Perfetto MCP Rs MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Linux MCP Server
Developer Tools · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
Perfetto MCP Rs
Developer Tools · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Linux MCP Server if you need specialized Developer Tools tools running via a local process. Choose Perfetto MCP Rs if your workspace requires Developer Tools integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
L
Choose Linux MCP Server when:
You need dedicated capabilities in the Developer Tools domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
MCP server for read-only Linux system administration, diagnostics, and troubleshooting
MCP server for Perfetto trace analysis. Runs PerfettoSQL queries on .perfetto-trace / .pftrace files via auto-downloaded traceprocessorshell, with dedicated Chrome tools for page loads, scroll jank, main-thread hotspots, and stdlib module discovery. Cross-client tested on Claude Code and Codex. Available via cargo install, Homebrew tap, and curl install script.
Linux MCP Server is categorized under Developer Tools and uses a local stdio subprocess. In contrast, Perfetto MCP Rs belongs to Developer Tools using local stdio subprocess. Select Linux MCP Server when you need capabilities focused on developer tools and Perfetto MCP Rs when you require tools for developer tools.
Open one trace with `path`, or several with `paths`; returns an opaque `trace_id` and lightweight routing summary for each file (type/profile, duration, platform, process/thread counts, capabilities, redaction policy, recommended next tools)
execute_sql
Run a PerfettoSQL query (max 5000 returned rows). Prefer the dedicated `chrome_*` / `list_*` tools for standard analyses; use this for custom joins or aggregations they don't expose. Output shaping: `head`/`limit`, `summary`, `columns_only`, `include_row_count`, `max_string_len`. Sensitive URL/head…
list_tables
List tables/views in the loaded trace, optional GLOB filter
list_table_structure
Show column names and types for a table
list_processes
List processes (pid, name, start/end timestamps)
list_threads_in_process
List threads under a process name (up to 2000)
slice_descendants_breakdown
Summarize child slices under a long slice id without hand-writing recursive CTEs
list_stdlib_modules
List PerfettoSQL stdlib modules, optional `domain` / `query` / `limit` filters (no trace needed)
chrome_scroll_jank_summary
Worst janky frames with cause, sub-cause, delay_since_last_frame
Compact URL-level resource/request summary for page-load windows, ranked by max overlap with normalized origin, navigation/renderer relatedness, and attribution-scope evidence
chrome_page_load_resource_pipeline
One URL's lifecycle/request spans joined with background parse, script evaluation, and style/layout signals, plus an evidence boundary for DNS/TLS/TTFB/cache/download hypotheses